[asterisk-bugs] [JIRA] (ASTERISK-21203) res_xmpp socket error: takes upto 19 minutes to restore xmpp socket connection to google

Wed Mar 13 01:48:01 CDT 2013

    [ https://issues.asterisk.org/jira/browse/ASTERISK-21203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204154#comment-204154 ] 

Chirag Chhatriwala commented on ASTERISK-21203:
-----------------------------------------------

Matt Jordan:

You misunderstood the point. I'm not concerned about the IP Address being changed in the middle of the call. 
The log file indicates that "MY" IP address changed. In other words, the box which runs asterisk had its IP address changed as a result of PPPoE based renewal. When that happened the call and the connection to google via xmpp was lost. 

What I want to know is, what can be done to minimize the time spent in limbo by the asterisk server figuring out whether it is still connected or not. Obviously it takes about 18-20 minutes EACH time the IP address changes for the connection to be revived. All the buddies see the connection as offline for this time and when it re-connects (after 18-20 minutes), the buddies now see the connection as active. All calls then originating and terminating to the google voice number are properly established (only after the 18-20 minutes spent in limbo).

The fact that the call dropped is inherent because every 6 or so hours my internet renews to a different IP address and all calls during that period will be terminated for obvious reason (something I already know about).
I want to have the connection to google "re-activated or refreshed" as soon as possible (and not have to wait 20 minutes). That is what I'm trying to draw attention to.

Thanks,
Chirag

> res_xmpp socket error: takes upto 19 minutes to restore xmpp socket connection to google
> ----------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21203
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21203
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_xmpp
>    Affects Versions: 11.3.0
>         Environment: Linux OpenWrt 3.7.5 #2 Wed Feb 6 20:40:48 EST 2013 mips GNU/Linux
>            Reporter: Chirag Chhatriwala
>         Attachments: messages
>
>
> 11.3.0-rc1 addresses a problem in which if a res_xmpp connection becomes stale (network interruption/IP address change), the res_xmpp performs a reconnect and the filters are also refreshed to make sure it responds to jingle/chan_motif signalling.
> Now, it takes about 18-20 minutes to recover from a network outage. I.e. IP Address change. There doesn't seem to be any way to minimize the time before the following message:
> [2013-03-02 09:18:13] WARNING[15652][C-00000026] res_rtp_asterisk.c: RTP Transmission error of packet to 74.125.135.127:19305: Network is unreachable
> [2013-03-02 09:18:13] WARNING[15652][C-00000026] res_rtp_asterisk.c: RTP Transmission error of packet to 74.125.135.127:19305: Network is unreachable
> [2013-03-02 09:18:13] WARNING[15652][C-00000026] res_rtp_asterisk.c: RTP Transmission error of packet to 74.125.135.127:19305: Network is unreachable
> [2013-03-02 09:36:29] WARNING[2872] res_xmpp.c: JABBER: socket read error
> I have a log file which is about 21.6MB in size so I'm not uploading it here just as yet.
> I have a smaller log file which does show this time difference of 18+ minutes as well. The file shows that a google voice call gets interrupted (as a result of IP renewal resulting in a changed IP) and then the jabber socket read error appears around 18+ minutes later.
> This is indicative of all IP Address renewals.
> In the above, the time between 09:18:13 and 09:36:29, any outbound calls [through google voice] do not work and any inbound calls [through google voice] do not terminate on my SIP phone. After, 09:36:29, everything works as it should. I'm trying to minimize this window where the connection is in limbo.
> Please help.
> Thanks,
> Chirag

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira