[asterisk-bugs] [JIRA] (ASTERISK-26491) pjsip: PJSIP is confused by erroneous Contact header. chan_sip handles it fine.
Daniel Heckl (JIRA)
noreply at issues.asterisk.org
Tue Nov 1 05:55:10 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=233215#comment-233215 ]
Daniel Heckl commented on ASTERISK-26491:
-----------------------------------------
Thanks for the heads-up. I think there are more effected users than thought. All users which want to migrate to pjsip and have no static public ip.
They cannot set external_signaling_address and external_media_address (because of only external_signaling_address supports domains), so they use there private ip and asterisk goes crazy if there are two contact-headers with the same URI.
I am in contact with our provider. I think that does not help. The SIP messages and SDP messages uses private IPs, which is unusual.
I hope the problem is fixed as soon as possible. PJSIP is great and I want to use it for all our phone numbers.
> pjsip: PJSIP is confused by erroneous Contact header. chan_sip handles it fine.
> -------------------------------------------------------------------------------
>
> Key: ASTERISK-26491
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26491
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip
> Affects Versions: 13.11.2
> Reporter: Daniel Heckl
> Assignee: Unassigned
> Severity: Minor
> Attachments: log.txt, pjsip-debug-log2.txt
>
>
> Our Asterisk is behind an NAT and has an public ip. Sometimes our public ip address changes. Asterisk sends an REGISTER all 480 seconds.
> If our public ip address changes and Asterisk sends an re-REGISTER, our provider sends an OK. But asterisk does not realize it. Instead asterisk sends multiple times a new REGISTER and gets always an OK. After some time it logs "res_pjsip_outbound_registration.c:761 schedule_retry: No response received". Why!? Asterisk received multiple times an OK!
> After some wait time it retries again, gets an 403 Forbidden from our provider and permanently stops outbound registration.
> Chan_sip handle properly this situation.
> Attached a log from the communication between asterisk and tel.t-online.de.
> I think the problem is that the OK from the provider contains following lines:
> Contact: <sip:0123456789 at 192.168.0.10:45060>;expires=480
> Contact: <sip:0123456789 at 192.168.0.10:45060>;expires=10
> Asterisk see the 10 seconds expiring Contact and schedules a new registration. But in reality the first Contact is "the new" one, this one is expiring in 480 seconds.
> Asterisk re-REGISTER till the second Contact is expired.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list