Summary:	ASTERISK-21043: Motif/XMPP/Google Voice based calls keep ringing after re-establishing XMPP connection after socket error
Reporter:	Chirag Chhatriwala (cchhat01)	Labels:
Date Opened:	2013-02-06 18:27:52.000-0600	Date Closed:	2013-02-06 18:31:36.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Channels/chan_motif Resources/res_xmpp
Versions:	11.1.0 11.1.2 11.2.1	Frequency of Occurrence	Constant
Related Issues:	duplicates ASTERISK-20916 GoogleVoice calls don't connect, but continue ringing despite call having been answered
Environment:	Linux OpenWrt 3.7.5 #1 Sun Feb 3 17:34:28 EST 2013 mips GNU/Linux (mips based)	Attachments:	( 0) asterisk.conf ( 1) extensions.conf ( 2) jingle.conf ( 3) logger.conf ( 4) messages ( 5) rtp.conf ( 6) sip.conf ( 7) xmpp.conf
Description:	Chan motif works great for the most part, as long as the connectivity to gtalk/google servers is maintained throughout. However, if the connection is interrupted (i.e. dhcp release/renew, event), the XMPP connectivity to google servers is renegiated. However, any calls placed routed via google voice (chan_motif) will not terminate properly. The called party will be called correctly, they will even pick up. However to the caller continues to hear "ringing" tone. Incoming calls that terminate through chan_motif (after the renegotiated xmpp connection) DO NOT RING on the SIP phones (where originally they did). Also, SIP based calling works absolutely fine. Dialplan/extension and configuration files available as well. Thanks, Chirag
Comments:	By: Joshua C. Colp (jcolp) 2013-02-06 18:31:36.195-0600 This issue has already been fixed in SVN.