SV8100 no calls out (busy on all trunks)

[TheDillweed]

Hello fine people of this board!

I've been lurking here the past few days trying to learn all I can about the SV8100 system (v9.50)that my company has. I just started in my position and one of the priorities set for me was to 'fix the phones'. Well turns out that the environment was a large flat network (Class B) and voip quality was terrible due to packet loss. So I just created a new Voice VLAN and have moved the PBX and a few phones over to it. So far, here is where I'm at.

Incoming calls work perfectly.
Outgoing calls get a busy signal (on all SIP trunks)
Internal paging works

I changed the IP of the IPL on 10-12-09 and changed the VOIP gateway address on 84-26 to new IPs in the new VLAN. This unit has an IPL-B card in it. Is there something I missed? Any insight or help would be welcomed.

If it helps, we also have a SonicWall NSA2400 (with all VOIP related settings turned off). Ports are being forwarded from WAN>PBX and there are no restrictions outgoing. I'm not a 'phone guy' (as the tech who works for the SIP provider so rudely informed me) but I am competent in IT and am committed to understanding this system. I think I'm close...just need a little push by an expert here to get this system working properly.

Thanks for your help!

-G

 

[belevedere]

Outbound SIP trunk issues are usually the fault of a wrong setting in MB 10-36. Look for a space that does not belong, or a wrong character/number. Also make sure you have the main number in MB 21-17 for all SIP trunks. You may need to reset the system to kick it in. SIP ALG in the router can sometimes mess it up. Try turning it off. Make sure your port forwarding is correct in the router. IP address in MB 10-12-09 set to (usually 6060), and the IP address in MB 84-26 to ports 10020-10083.

 

[belevedere]

One more item, make sure that each phone has either a trunk line appearance or a trunk loop key assigned. Possibly CAP keys so you have a path for the trunk to go.