SIP TRUNK ISSUES VIA SONICWALL

[sedwardf]

Hi,

I have an IPO (v9.0.5). I have set up a SIP trunk via a sonicwall. The issue I have is frequent loss of registration that isn't being seen by Network. The sonicwall is keeping the connection live from wan side to network. However the internal connection to IPO is losing registration often. I can make calls but any SIP updates being sent aren't reaching the IPO. I can make and receive calls but suffer cut offs on all calls at various durations. Multiple calls cut off at the same time. I have seen in SysStatus that this is due to the loss of registration. Has anyone had similar issues using sonicwall? I have been assured that SIP ALG is turned off.

 

[DavidCT]

I have lots of Sonicwalls with SIP on IP Office. It does work.

1) You need to have a gen4 or newer Sonicwall running 5.8 or better enhanced firmware.

2) I always enable SIP transformations on the Sonicwall.

3) I open port 5060 from the ITSP to the IP Office.

4) Turn STUN on IP office off.

 

[sedwardf]

Thanks David,

I'll try these. I hadn't turned STUN on because our provider doesn't require it. But I'm prepared to try anything.

 

[AvantiWade]

How do you have the IP Office setup network wise? I had all sorts of trouble getting SIP working and ended up setting interface X6 to a dmz zone on my NSA220 and putting the IP Office in there with its public IP to get rid of NAT. I pass through the port ranges for SIP, RTP, and assorted one-x stuff, works fine. I have SIP Transformations disabled with this and it runs fine.

 

[pmcook]

Also be sure that H323 transformations is disabled on the SonicWall.

 

[sedwardf]

Thanks Guys. running STUN hasn't worked. The Trunk registers but the lines are OOS. Going to get the transformations checked on the sonic...

 

[DavidCT]

You do not want STUN. Turn it off.

You do want SIP Transformations enabled.
You also want to disable OOS on the SIP Line, unless your ITSP explicitly says they support it.

 

[janni78]

I never use SIP ALG, unless doing SIP on Aura.

It's only needed if you want the firewall to rewrite the SIP headers, but the IPO already puts the right IPs in the SIP headers.
Also doing SIP ALG limits the amount of calls you can have through the firewall.

You should do a monitor trace when it happens, if it has to do with registration you should see what reply you get from the service provider that might give a clue what's causing this.

"Trying is the first step to failure..." - Homer