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

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-21203:
----------------------------------------

I did misunderstand the point - it's usually easy to point the finger at Google on these kinds of issues, since they're notorious for doing "interesting" things.

However, in this case, it's actually even easier to point out that this is not a bug. As David pointed out, changing a server IP address during operation is generally considered a "bad thing". If nothing else, it invalidates any information sent to any endpoint regarding Asterisk's location - any operation in progress is at risk of failing.

In general, if you make major system configuration changes - which changing the IP address of the server would amount to - you should, at a minimum, reload modules in Asterisk that communicate with other system - and more likely, restart Asterisk.

Anything that changed this behavior would be considered an improvement, and not a bug fix. I'm in complete agreement with David here - this is generally something that should not be done to any system that is providing services.
                
> 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