Has anyone encountered an issue where the PAP2T isn't honoring the registration timer in the contact header sent by an Acme Packet SD to the PAP2T? Any suggestions are appreciated.
What is the Acme trying to set the timer to, and how does that compare to the default registration interval in the Linksys? I think they can't be more than 50% apart (so if the Linksys is set to 3600, and the Acme suggests 30, that's too much of a difference and you'd need to lower the interval on the Linksys). There are also settings for min and max registration interval on the SIP settings page. -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Holloway Sent: Tuesday, January 31, 2012 6:06 PM To: VoiceOps Subject: [VoiceOps] Linksys PAP2T Has anyone encountered an issue where the PAP2T isn't honoring the registration timer in the contact header sent by an Acme Packet SD to the PAP2T? Any suggestions are appreciated. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
I haven't had a problem with setting the Linksys to 3600. However, my Acme SBC has a 3600 second timer as well, with a 120 second renew/30 second NAT renew timer. That being said, I did run into an issue not too long ago where I moved to a new platform and the Linksys ATAs started ignoring the renewal timers. Ryan Delgrosso of this list pointed me to the problem, which is that it was caused by a blank "organization" header in the SIP messaging from the softswitch, causing the Linksys to ignore any headers below the blank one. Populating that field in the softswitch (the Acme just reoriginates the original request) fixed it. You can do header manipulation to get it to work as well, but that's really just an unnecessary band-aid and doesn't fix the underlying issue. --- Brandon P. Buckner Switching Technician / VoIP Admin Iowa Network Services brandonb at netins.com -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Scott Berkman Sent: Tuesday, January 31, 2012 7:31 PM To: 'Mark Holloway'; 'VoiceOps' Subject: Re: [VoiceOps] Linksys PAP2T What is the Acme trying to set the timer to, and how does that compare to the default registration interval in the Linksys? I think they can't be more than 50% apart (so if the Linksys is set to 3600, and the Acme suggests 30, that's too much of a difference and you'd need to lower the interval on the Linksys). There are also settings for min and max registration interval on the SIP settings page. -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Holloway Sent: Tuesday, January 31, 2012 6:06 PM To: VoiceOps Subject: [VoiceOps] Linksys PAP2T Has anyone encountered an issue where the PAP2T isn't honoring the registration timer in the contact header sent by an Acme Packet SD to the PAP2T? Any suggestions are appreciated. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Thanks Brandon (and Ryan too). That confirms the defect. If the organizational header is blank the Linksys ignores the expiry timer. On Feb 1, 2012, at 11:01 AM, Brandon Buckner wrote:
I haven't had a problem with setting the Linksys to 3600. However, my Acme SBC has a 3600 second timer as well, with a 120 second renew/30 second NAT renew timer. That being said, I did run into an issue not too long ago where I moved to a new platform and the Linksys ATAs started ignoring the renewal timers. Ryan Delgrosso of this list pointed me to the problem, which is that it was caused by a blank "organization" header in the SIP messaging from the softswitch, causing the Linksys to ignore any headers below the blank one. Populating that field in the softswitch (the Acme just reoriginates the original request) fixed it. You can do header manipulation to get it to work as well, but that's really just an unnecessary band-aid and doesn't fix the underlying issue.
--- Brandon P. Buckner Switching Technician / VoIP Admin Iowa Network Services brandonb at netins.com
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Scott Berkman Sent: Tuesday, January 31, 2012 7:31 PM To: 'Mark Holloway'; 'VoiceOps' Subject: Re: [VoiceOps] Linksys PAP2T
What is the Acme trying to set the timer to, and how does that compare to the default registration interval in the Linksys? I think they can't be more than 50% apart (so if the Linksys is set to 3600, and the Acme suggests 30, that's too much of a difference and you'd need to lower the interval on the Linksys). There are also settings for min and max registration interval on the SIP settings page.
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark Holloway Sent: Tuesday, January 31, 2012 6:06 PM To: VoiceOps Subject: [VoiceOps] Linksys PAP2T
Has anyone encountered an issue where the PAP2T isn't honoring the registration timer in the contact header sent by an Acme Packet SD to the PAP2T? Any suggestions are appreciated. _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
participants (3)
-
BrandonB＠netins.com -
mh＠markholloway.com -
scott＠sberkman.net