Home › Forums › HAast (High Availability for Asterisk) › General › Multiple PJSIP contacts for same extension after failover with IPR
Tagged: contact, contacts, default_expiration, max_contacts, pjsip
-
AuthorPosts
-
I am using the Immediate Phone Reachability (IPR) feature and it’s working well. However, I noticed that right after a failover, some of my phones show as being registered multiple times with PJSIP, and both registrations are “available” (i.e. qualified) on the same IP. How can there be multiple registrations to the same IP? For example, see extension 123 below
pbx-k*CLI> pjsip show contacts
Contact: <Aor/ContactUri…………………………> <Hash….> <Status> <RTT(ms)..>
==========================================================================================Contact: 123/sip:123@192.168.1.10:5060 c2bc4d82a3 Avail 357.751
Contact: 123/sip:123@192.168.1.10;user=123;transport=ud 48ce6598ea Avail 340.433Because of how IPR works it’s normal to see some extensions registered multiple times, to the same IP address / port / transport /etc. This is harmless (will have no affect on Asterisk operations), and they will expire after the phone’s next (regular) registration or expiration countdown. This normally takes 5-10 minutes but can take up to 60 minutes depending on the phone and PJSIP configuration.
If you want a more technical explanation, PJSIP tracks endpoints by the exact SIP contact header string. So even a small change in that string (e.g. changing the order of contact parameters), PJSIP will treat the latest contact (which is slightly different) as another registration. This is a known issue with PJSIP but is practically harmless.
If you wish to immediately remove old (unused) contact entries, set the max_contacts line in pjsip’s configuration to 1 (or however many phones actually register against this AOR). You can also experiment with the default_expiration and remove_unavailable settings; however, this can have other consequences so be sure you fully understand these settings before you change them.
-
AuthorPosts
- You must be logged in to reply to this topic.