Summary:ASTERISK-03682: MGCP *69 does not call back correct number
Reporter:duanecox (duanecox)Labels:
Date Opened:2005-03-14 21:45:21.000-0600Date Closed:2011-06-07 14:05:16
Versions:Frequency of
Environment:Attachments:( 0) debug_trace.txt
( 1) snip_of_mgcp_conf.txt
Description:MGCP *69 does not properly call back number.  Testing here shows that if call 12172026046 terminates on the MGCP endpoint, *69 at the endpoint will dial 172026046, leaving out the "21" from the area code.
Comments:By: Clod Patry (junky) 2005-03-14 21:46:37.000-0600

Could you attach any infos for debug?

By: Brian West (bkw918) 2005-03-14 23:03:28.000-0600

This could have all been filed under the same bug because chances are the problem is identical.


By: duanecox (duanecox) 2005-03-18 15:26:01.000-0600

This may be more of a feature request than a bug.
After looking at the source, I do not see where mgcp will actually dial the number.  Currently all it is coded to do is read back the lastcallerid.
I believe that normal operation of *69 is to call the number back...

} else if (p->callreturn && !strcmp(exten, "*69")) {
    res = 0;
    if (strlen(p->lastcallerid)) {
         res = ast_say_digit_str(chan, p->lastcallerid, "", chan->language);
    if (!res)
         /*res = tone_zone_play_tone(p->subs[index].zfd,ZT_TONE_DIALRECALL);*/
         transmit_notify_request(sub, "L/sl");

By: duanecox (duanecox) 2005-03-18 15:28:00.000-0600

bkw, identical to what?  *70?  No, that is a different problem entirely, but I see that it was closed for some reason, what bug is ASTERISK-3681 duplicate of?

By: Mark Spencer (markster) 2005-03-26 01:53:54.000-0600

The *69 feature on Asterisk simply reads back the last number called and plays stutter dialtone -- it does not call it.  This is not a bug.