[asterisk-bugs] [JIRA] (ASTERISK-23329) Realtime Peers behind NAT becomes unreachable after peer reload

Michael L. Young (JIRA) noreply at issues.asterisk.org
Wed Feb 19 11:04:03 CST 2014


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

Michael L. Young commented on ASTERISK-23329:
---------------------------------------------

One thing that is probably not correct is that you have "directmedia" set to "yes".  You are working with NAT and that should be turned off.  If you do have that off for this peer, then it would probably be due to a bug that has been fixed in recent versions of Asterisk.

The other thing I would request is that you update to a newer version of Asterisk.  1.8.25 is the latest version and there have been some fixes in regards to realtime peers and NAT.

When upgrading, make sure you update your DB schemas since the schemas in the contrib directory were not up to date in 1.8.20.  They have been updated in recent versions.  Also, make sure you read the Changelog.  Upon updating, some of the default global settings in chan_sip were not being overridden and they will now be overridden properly if a peer is defining a different value from the default global values.

Please try the above and report back if this is still an issue for you.

Thanks
                
> Realtime Peers behind NAT becomes unreachable after peer reload
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-23329
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23329
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.20.1
>            Reporter: Paul Mathews
>            Severity: Critical
>
> I have a realtime peer behind NAT. Things work perfectly. I then did an asterisk reload, which caused the peer cache to be cleared, I then attempted to reach the peer. The private IP address from the Reg. Contact was copied over to the IP address, which caused the peer to be unreachable.
> Here is the sip show peer 10116 before reload
> {noformat}
> ip-10-0-0-94*CLI> sip show peer 10116
> Name : 10116
> Realtime peer: Yes, cached
> Secret : <Set>
> MD5Secret : <Not set>
> Remote Secret: <Not set>
> Context : from-internal
> Subscr.Cont. : <Not set>
> Language :
> AMA flags : Unknown
> Transfer mode: open
> CallingPres : Presentation Allowed, Not Screened
> Callgroup :
> Pickupgroup :
> MOH Suggest :
> Mailbox :
> VM Extension : *97
> LastMsgsSent : 32767/65535
> Call limit : 0
> Max forwards : 0
> Dynamic : Yes
> Callerid : "" <>
> MaxCallBR : 384 kbps
> Expire : 191
> Insecure : no
> Force rport : Yes
> ACL : No
> DirectMedACL : No
> T.38 support : No
> T.38 EC mode : Unknown
> T.38 MaxDtgrm: -1
> DirectMedia : Yes
> PromiscRedir : No
> User=Phone : No
> Video Support: No
> Text Support : No
> Ign SDP ver : No
> Trust RPID : No
> Send RPID : No
> Subscriptions: Yes
> Overlap dial : Yes
> DTMFmode : rfc2833
> Timer T1 : 500
> Timer B : 32000
> ToHost :
> Addr->IP : 27.122.12.75:50427
> Defaddr->IP : (null)
> Prim.Transp. : TCP
> Allowed.Trsp : TCP,UDP
> Def. Username: 10116
> SIP Options : (none)
> Codecs : 0x50e (gsm|ulaw|alaw|g729|ilbc)
> Codec Order : (g729:20,ilbc:30,gsm:20,ulaw:20,alaw:20)
> Auto-Framing : No
> Status : OK (471 ms)
> Useragent : MicroSIP/3.3.31
> Reg. Contact : sip:10116 at 10.185.1.6:5060;transport=TCP;ob
> Qualify Freq : 60000 ms
> Sess-Timers : Accept
> Sess-Refresh : uas
> Sess-Expires : 1800 secs
> Min-Sess : 90 secs
> RTP Engine : asterisk
> Parkinglot :
> Use Reason : No
> Encryption : No
> {noformat}
> Here is the sip show peer after reload
> {noformat}
> ip-10-0-0-94*CLI> sip show peer 10116
> Name : 10116
> Realtime peer: Yes, cached
> Secret : <Set>
> MD5Secret : <Not set>
> Remote Secret: <Not set>
> Context : from-internal
> Subscr.Cont. : <Not set>
> Language :
> AMA flags : Unknown
> Transfer mode: open
> CallingPres : Presentation Allowed, Not Screened
> Callgroup :
> Pickupgroup :
> MOH Suggest :
> Mailbox :
> VM Extension : *97
> LastMsgsSent : 32767/65535
> Call limit : 0
> Max forwards : 0
> Dynamic : Yes
> Callerid : "" <>
> MaxCallBR : 384 kbps
> Expire : -1
> Insecure : no
> Force rport : Yes
> ACL : No
> DirectMedACL : No
> T.38 support : No
> T.38 EC mode : Unknown
> T.38 MaxDtgrm: -1
> DirectMedia : Yes
> PromiscRedir : No
> User=Phone : No
> Video Support: No
> Text Support : No
> Ign SDP ver : No
> Trust RPID : No
> Send RPID : No
> Subscriptions: Yes
> Overlap dial : Yes
> DTMFmode : rfc2833
> Timer T1 : 500
> Timer B : 32000
> ToHost :
> Addr->IP : 10.185.1.6:50427
> Defaddr->IP : (null)
> Prim.Transp. : TCP
> Allowed.Trsp : TCP,UDP
> Def. Username: 10116
> SIP Options : (none)
> Codecs : 0x50e (gsm|ulaw|alaw|g729|ilbc)
> Codec Order : (g729:20,ilbc:30,gsm:20,ulaw:20,alaw:20)
> Auto-Framing : No
> Status : UNREACHABLE
> Useragent : MicroSIP/3.3.31
> Reg. Contact : sip:10116 at 10.185.1.6:5060;transport=TCP;ob
> Qualify Freq : 60000 ms
> Sess-Timers : Accept
> Sess-Refresh : uas
> Sess-Expires : 1800 secs
> Min-Sess : 90 secs
> RTP Engine : asterisk
> Parkinglot :
> Use Reason : No
> Encryption : No
> {noformat}

--
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



More information about the asterisk-bugs mailing list