SIP Trunk Issue

donald.janke · ‎08-05-2011

I have a Junction Networks SIP trunk, which has no problems anytime making outbound calls. (for international) I have an inbound toll free number and one DID, every once in while I can not receive incoming calls on this trunk. As soon as I reboot the UC320, inbounds calls work again. Does anyone have any ideas on this? I was considering converting my 3 pots lines to a SIP trunk from Broadview networks but this issue of failing inbound calls on the SIP portion of this unit has me weary.

Christopher Edgeworth · ‎08-05-2011

Hi Donald,

Do you have another router siting WAN side of the UC320W? If so, does it have a SIP ALG?

One thing you can try is to enable NAT keepalive on the SIP / BRI page. You can enable sending SIP keep alive messages without having to enter a NAT IP address. (You may have to check and then uncheck the checkbox above it to do this, depending upon what version of firmware you are running).

If the UC320W is indeed getting the SIP INVITE and then failing the call that is a different story and the SBSC engineer will need to look at the SIP logs. You can enable this by going to Status -> Support Tools -> Log then enabling SIP logs for your SIP trunk configuration.

Hope this helps.

Chris

donald.janke · ‎08-05-2011

Chris,

I do have a Sonicwall as my WAN router. I have just enabled NAT keepalive. Let's see if it keeps it alive untill I return on Monday.

Don

donald.janke · ‎08-08-2011

Chris,

This seems to have resovled my issue. I do have another question. If you have more than one SIP provider it seems in the SIP section the port numbers increase as they are added. What if all your provides require 5060 to be used?

donald.janke · ‎08-11-2011

Actually, it did not reslove the issue, incoming calls have failed again.

Christopher Edgeworth · ‎08-11-2011

Donald Janke wrote:

Actually, it did not reslove the issue, incoming calls have failed again.

Hi Donald,

Are you seeing the incoming SIP INVITE if you enable SIP logs on the UC320W. Status -> Support Tools -> Log? If not, then the WAN side device is blocking the INVITE. Assume you have checked for firmware updates on the WAN side device?

Chris

Christopher Edgeworth · ‎08-11-2011

Donald Janke wrote:

Chris,

This seems to have resovled my issue. I do have another question. If you have more than one SIP provider it seems in the SIP section the port numbers increase as they are added. What if all your provides require 5060 to be used?

I'm assuming that they are requiring that the UDP destination port be 5060 on packets going to the provider, but the provider doesn't care what the source port is. If all of your providers are not using SIP registration, then maybe I could see this causing some challenges. Most providers use SIP registration, so if you have two providers that you are using one with registration and one without. Provision the provider without registration first so it uses local port 5060.

Chris

donald.janke · ‎08-11-2011

Chris,

I have roughed my way thru this install, so not sure exctally what I should be looking for in the log.

The system is so easy even someone who never installed a phone system can.

donald.janke · ‎08-11-2011

Maybe it is a provider issue? Because I have not rebooted the system and incoming calls are coming in.

rbordner · ‎08-12-2011

Does the incoming call work after an outbound call to the SIP provider? As Chris requested the NAT keep alive be enabled to keep the SIP port open on the sonicwall. You might want to check if the firewall firmware version is up to date.

After outbound call does inbound call work?

Then keep trying inbound calls at different time durations up to the registration timer (could be 3600 seconds). It is possible the firewall is closing down the inbound sip message after some time.

Randy

donald.janke · ‎09-09-2011

Has anyone got this unit to work with more than one SIP trunk? As I mentioned before when you add SIP trunks it ups the port numbers, 5060 then 5061. I had to have my provider change it to 5061 and I still can only get one SIP to work.

rbordner · ‎09-09-2011

Donald,

Can you provide more information on the second SIP trunk? What is the second trunk status? Does it show as registered? Can you make an make an inbound or outbound call on the second trunk? If needed let's arrange a time to trouble shoot and debug the issue.

Thanks,

Randy

Dturner4777 · ‎09-12-2011

HI

I also have the same issue, since upgrading to 2.1 incomings calls get engaged tone and dont even reach the uc320w, it has been working fine for 6 weeks before.