SIP - Call Centric - Watchguard

[penn73]

Hey guys,

Well, I have gotten the system upgraded to essential with no issues but now for the last part of this upgrade is to setup a couple of sip trunks. I have successfully setup call centric for other customers but cannot get this one to register. Any ideas on what I can do to get this going? I'm pretty sure the problem lies within the watchguard and right now I have ports 5060-5080 forwarded to my IPO. Anyone use or using a watchguard?


Thanks, Joe

 

[hairlessupportmonkey]

I ONLY use watchguard.

Are you using a SIP ALG Proxy or just SNAT?

ACSS - SME
General Geek

 

[penn73]

The only thing that has been done so far is setup a SNAT to the IPO. (Ports 5060-5080) I don't have access to the watchguard so I have kind of been passing on information to the company that supports there network. After reviewing the system status I noticed it wasn't resolving the callcentric domain which led me realize I forgot to enter a dns server. Not sure if this will fix the problem or not but I'm sure it is a issue.

Thanks

 

[penn73]

Well DNS servers have been put in but I still can't get the sip trunk to register. Should I be using a STUN server? Any other suggestions?


Thanks, Joe

 

[penn73]

According to Call Centric (and my monitor) the IPO is sending registration request but not receiving packets from Call Centric.

 

[hairlessupportmonkey]

can you post me the config of the watchguard?

ACSS - SME
General Geek

 

[hairlessupportmonkey]

Also you need to look in the watchguard logs and see if traffic coming back is being denied.

ACSS - SME
General Geek

 

[penn73]

Thank you sir, I have requested the information from the company that supports the network. I'm not used to not having full control of network access which adds another layer of complexity to this project... As soon as I get this information I will post it up.


Thanks, Joe

 

[penn73]

Copy of the config attached,

Thanks!

 

[hairlessupportmonkey]

Any reason why you are using a VLAN for the SIP trunk? Why not just create another trusted network on another interface (Optional) and plumb that into LAN 2(WAN) on the IPO.



ACSS - SME
General Geek

 

[penn73]

Ignorance I guess... So I could just plumb the IPO Wan (LAN 2) interface out to any data switchport correct? Then just create a IP Route on the IPO with the correct DG and route it to LAN 2?

Thanks for the assistance!

 

[hairlessupportmonkey]

No, plumb the IPO directly into an Optional port on the WG and configure it up as the second network, like the VLAN one is set up but without any VLAN tagging.

ACSS - SME
General Geek

 

[penn73]

Ok, I'll work with the vendor and attempt get the optional port setup. Did you see anything else with regards to why the traffic would not be getting back the IPO with its current config. I have done plenty of research over the last week and have made no progress. I've read where the Watchguard may need a reboot for the policy to take but when I passed that on to the supporting vendor they pretty much shot that theory down.

 

[hairlessupportmonkey]

Sometimes the WG does need a reboot. In my experience and I have configured over 100 of them, it doesnt hurt and its only a little XTM 25 and its back up in running in under 60 seconds.

ACSS - SME
General Geek

 

[penn73]

First off, thanks again for your assistance. Think I'm finally over the firewall issue as it is now registered and looking good. Now I"m having an issue with outbound routing. Try to dial out (8+1+area code+#) and get the incorrect number dialed error and I don't see anything going on in Monitor.

Current setup:
Lines>Sip trunk 17

SIP-URI tab = outgoing group 17

Shortcode-
8XXXXXXXXXXX
Dial
N
Line Group ID = 17

Any suggestions are greatly appreciated.

Joe

 

[AndrePa]

I haven't been on callcentric in a while because of problems with their incoming caller ID, I would get "alphabet soup" as the incoming caller ID Name on some calls.
You want dial out using (8+1+area code+#)
Your short code is close, but You need an ARS route too!


Try this,

Shortcode 8N
Feature Dial
Telephone N
Line Group ID 50:Main

Add this to You ARS ( ie. under 50:Main )

Code xxxxxxxxxxx
Feauture Dial
Telephone Number n"@callcentric.com"
Line Group Id 17


That should work

 

[penn73]

Thank you! I will get this change made and follow up.

Joe

 

[penn73]

Changes made but have the same results, any other suggestions?

Thanks

 

[AndrePa]

Penn73, the above short code, and ARS should work for callcentric. Make sure Use Tel URI is un-checked, and that You have callcentric.com as the ISTP Domain Name.

If Users are not dialing a 1 in front of the area code, You can add this to you ARS, this will add a 1 in front of the area code, and seven digit number. Callcentric will only complete an outgoing call with 11 digit numbers.

Code xxxxxxxxxx
Feauture Dial
Telephone Number 1n"@callcentric.com"
Line Group Id 17


Andre

 

[penn73]

I thought so as well, I'm guessing I have something else going on...

I'm assuming it's not a firewall issue since I'm now registered, would this be a correct assumption?