Setting up new SIP trunk service and can't make calls

[nixnewbie]

Concise back story: Currently running sip service provided by Integra from a Metaswitch configured on LAN2 directly connected to Provider. Switching to new SIP provider who also uses Metaswitch. Integra is set up as Line 17 and works fine. We are setting up the new service as Line 18 via LAN1 routed and NAT'd through a Juniper Firewall with ALG disabled. Sip Registration all looks good via monitor.

I'm working with a partner and we are all stumped. When attempting to make an outbound call via the new service, here is what we get:

2016-10-13T00:12:46 3452073mS CMARS: Case 1 - dial_delay_time: 3000 has expired - Resolve what we might have - Called Number: 1xxxxxxxxxx Addr: f1789b00
2016-10-13T00:12:46 3452073mS CMARS: FORM: LightSpeed - Received Number: 1xxxxxxxxxx
2016-10-13T00:12:46 3452073mS CMARS: FOUND A SHORT CODE - short_code: XN; - Tel: N - Called_Party: 1xxxxxxxxxx - Line Group Id: 98
2016-10-13T00:12:46 3452073mS CMARS: SetCurrentTarget: Short_Code: XN; - Line_Group_ID: 98
2016-10-13T00:12:46 3452073mS CMARS: FindActiveARSByGroupID GroupID=98 - Not Found
2016-10-13T00:12:46 3452073mS CMLRQ: FindActiveLRQByGroupID GroupID=98 - Not Found
2016-10-13T00:12:46 3452073mS Sip: SIPTrunks: Make Target voip, line group id is 98 and ip 67.137.xxx.xxx
2016-10-13T00:12:46 3452074mS Sip: SIP Line (17) cannot find a suitable SIP URI to dial out
2016-10-13T00:12:46 3452074mS Sip: SIPTrunks: Make Target voip, line group id is 98 and ip 208.93.xxx.xxx
2016-10-13T00:12:46 3452074mS Sip: SIP Line (18) chosen channel not registered
2016-10-13T00:12:46 3452074mS CMARS: LINE with group ID: 98 HAS NO CHANNEL: 34 - ATTEMPT OTHER TARGETS
2016-10-13T00:12:46 3452074mS CMARS: ModifyCMARSTarget: Short_Code: XN; - Line_Group_ID: 98 set line status to CMARS_OUTOFSERVICE

It seems to me that the key failure is
2016-10-13T00:12:46 3452074mS Sip: SIP Line (18) chosen channel not registered

On Line 17 with Integra, I get
2016-10-12T23:43:29 1694088mS Sip: SIP Line (17): License, Valid 1, Available 24, Consumed 0

Thoughts?

Stephen

 

[IPGuru]

Metaswitch configured on LAN2 directly connected to Provider

Please tell me that does not mean what i think it does

Do you have a direct internet connection to Lan2 on your IPO (programmed with public IP Address or all ports forwarded)


Do things on the cheap & it will cost you dear

 

[Okkie26]

Well,

It's handy.


just put the public IP Address and login credentials here, and we are able to help you...

 

[nixnewbie]

Unfortunately, it did mean what you thought it meant IPGuru. Lets just say we don't use the vendor that set up that configuration for our IPO services any more. It isn't configured that way any more however. We were never able to get NAT to work through the Juniper. We moved the new carrier to LAN2 and put their public IP on that port. With that configuration, it works as expected. Just so you know, the carrier has us fully firewalled and LAN 2 is not publicly accessible through their network.

Stephen

 

[janni78]

NAT through Juniper shouldn't be an issue, I've used it many times both on Netscreen and SRX.
Just make sure to disable SIP ALG since IPO deosn't need it so it most probably just breaks things.

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

 

[Pepp77]

IPO might need SIP ALG depending on the setup

For example if you are in the UK and using IP authenticated SIP trunks and Oak call recording then you need to use SIP ALG on the router as you cannot use Network Topology to change the local IP to the public IP in the headers of the SIP packets as it breaks the recording!

| ACSS SME |

 

[nixnewbie]

janni78, we tried with and without SIP ALG and could not get it to work. It is an SRX240. Either way, it is irrelevant now.

Stephen

 

[janni78]

Didn't think anyone used Oak anymore for IP Office.

Port forwarding on SRX240s shouldn't be any problems, I've used both SRX100s and 240s several times.

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