[Home]

Summary:ASTERISK-25604: Dial application 'r' argument does not initiate ringing on a Motif channel
Reporter:Sean Darcy (seandarcy)Labels:
Date Opened:2015-12-02 10:48:36.000-0600Date Closed:2020-01-14 11:14:02.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Applications/app_dial Channels/chan_dahdi
Versions:11.20.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:fedora 22. x86_64Attachments:( 0) DebugLog2
( 1) myDebugLog
Description:No ringing using r option for dial. Everything else works, just silence until until the call is answered. There is a dial tone, and DTMF tones on dialing.

This option used to work (same dialplan) on 11.17 and earlier.

Surprising how really irritating this is.

extensions.conf :
{noformat}
exten => s,n(gv),Dial(motif/${MOTIF_DEFAULT}/+1${ARG1}@voice.google.com,,r)
{noformat}

cli:
{noformat}
Dial("DAHDI/1-1", "motif/XXX/+1<num>@voice.google.com,,r")
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2015-12-02 10:48:37.755-0600

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Rusty Newton (rnewton) 2015-12-04 17:07:29.388-0600

We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information


By: Rusty Newton (rnewton) 2015-12-04 17:08:09.872-0600

Sean, does this happen only with a Motif channel tech?

Please attach a debug log (as described above) along with correlating packet capture to demonstrate the issue.
By: Sean Darcy (seandarcy) 2015-12-05 10:25:09.887-0600

If I use a sip channel I get ringing _without_ the r option.

I didn't see anything related the the debug log.
By: Sean Darcy (seandarcy) 2015-12-07 08:47:54.405-0600

To be more clear, on a sip channel I get ringing with _or_  without the r option.
By: Rusty Newton (rnewton) 2015-12-09 21:15:26.127-0600

Hmm, can you verify that "xmpp set debug on" was enabled for the log. In addition can you provide a packet capture that correlates to the debug?

Have you gone back to 11.17 to verify the behavior regresses?
By: Sean Darcy (seandarcy) 2015-12-10 09:21:02.737-0600

OK, I'll enable xmpp set debug on,

I'll recheck 11.17.0.

By packet capture, to you mean wireshark between asterisk and gv ?

I'm pretty ignorant about all this, but it seems to me the connection between between xmpp and the gv server is working correctly .

From https://wiki.asterisk.org/wiki/display/AST/Calling+using+Google:

We use the Dial option "r" because Google doesn't provide ringing indications.

From that I'd assume that the Dial application was responsible for the ringing. Not xmpp or gv. In other words, the Dial app would cause a ringing on the Dahdi channel without any connection to xmpp (or motif).
By: Sean Darcy (seandarcy) 2015-12-10 10:32:54.159-0600

debug log with xmpp set debug on
By: Sean Darcy (seandarcy) 2015-12-16 10:24:58.111-0600

I rigged up a sip phone to the server.  Dialed with motif:

Dial("SIP/250-00000001", "motif/8447/+1<num>@voice.google.com") in new stack

No ringing without "r". BUT there is ringing with "r".

So it's some connection bewtween app_dial and dahdi.

Added chan_dahdi to components involved.
By: Rusty Newton (rnewton) 2015-12-30 09:15:22.846-0600

Ah, so it only happens with DAHDI <-> MOTIF then?

Can you attach new debug log that includes the DEBUG logger channel additionally? make sure verbose and debug are both turned up to 5. The instructions in the guide I linked should work.

Make sure to capture the entire call.
By: Sean Darcy (seandarcy) 2015-12-30 16:31:52.181-0600

Upgraded the server today to Fedora 23, gcc-5.3.1.

Was running 11.21.0-rc1 . "r" wasn't working.

After upgrade rebuilt 11.21.0-rc1  Everything the same. Same menuselect.

.But now "r" works.

Sunspots ???
By: Rusty Newton (rnewton) 2015-12-30 18:41:00.239-0600

Strange... maybe swamp gas or something got fixed along the way..

I'll leave the issue in Waiting On Feedback for a couple weeks. Let us know if it pops up again.
By: Asterisk Team (asteriskteam) 2016-01-14 12:00:21.484-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines