Sip registration changes port?

Answered Question
Apr 15th, 2010
User Badges:
  • Bronze, 100 points or more

Hello,


I'm trying to resolve my problem with a UC560 that sometimes works and sometimes doesn't. In talking with my Sip provider they tell me that they see my registrations coming in on odd ports. I'm not so sure that this is really my problem, however all the boxes I have out there are registering oddly. I can't determine where the change is taking place. The deal is that my first attempt to register is going to be denied as it is a url address, then a second attempt is made to the actual ip and then it will register. This is default behavior of the Sip provider. My first attempts do always come through on 5060. The port changes on the second attempt to some off brand port. What I want to know is, is there a default config in the UC pro boxes that will change the port? I would sure appreciate any thoughts on what could be going on as it seems across the board UC540 and 560 my registrations aren't behaving ideally. I feel there is something else going on with the 560 as it is having troubles passing traffic to extensions once it does get past the Auto attendant, but eliminating this trouble would help all over.


Thank ya much

Steph

Correct Answer by stevekeller007 about 7 years 2 months ago

I had a similar behavior when using a voice gateway to register with SIP server and using Communications Manager 7.1


In the debugs we could see the socket in use change its port from 5060 to something like 65410 when talking to the SIP server.

there is a hidden IOS command we used to stop that from happening, and we registered just fine after that.

under sip-ua then "connection-reuse" . this forced the gateway to use port 5060. hope it works for you

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
stevekeller007 Tue, 05/25/2010 - 05:47
User Badges:

I had a similar behavior when using a voice gateway to register with SIP server and using Communications Manager 7.1


In the debugs we could see the socket in use change its port from 5060 to something like 65410 when talking to the SIP server.

there is a hidden IOS command we used to stop that from happening, and we registered just fine after that.

under sip-ua then "connection-reuse" . this forced the gateway to use port 5060. hope it works for you

SHeidemann Thu, 05/27/2010 - 07:48
User Badges:
  • Bronze, 100 points or more

Thank you so much you saved my tail end. We have a firewall that is locked down pretty tight, let me just say this information came right on time it was exactly what I needed. Registering and calls are going through consistantly now. Whew!


Thank you thank you

Stephanie

Actions

This Discussion