Outnound Route Not Working

[mc6650]

Hello
The gateway is registered (voip.ms) and my inbound route is working, however I can't make outbound calls. I have a route setup to use the registered gateway and "North America" as a dial pattern. Is this an issue with ACL and if so then should I have the voip.ms IP address of the gateway proxy set in CDIR of the ACL, or is there another setting I'm missing?
Thank you in advance for any help that can be provided.

 

[falk]

Hi if the inbound is working its not ACL -
could be 1000 option - try to make call and check the sip info with sngrep

 

[hfoster]

There's a few useful places to look here:

1. The CDR detail, there's a section which shows what the call is doing. You should hope it gets bridged to voip.ms.

2. The Freeswitch logs, you should be able to see the call matching against the dial plan rules to eventually hit one and get bridged out to voip.ms

 

[Architect]

Are you able to post a screen shot of the Outbound Route you have created?

 

[mc6650]

Hello
Thanks for the help. It's weird, but when I look at the CDR info it looks like I'm trying to make an inbound call! I've attached screens shots and the log files. Where am I going wrong?

 

[hfoster]

2021-06-17 07:22:38.622315 [DEBUG] sofia.c:10456 verifying acl "domains" for ip/port 192.168.2.52:0.
2021-06-17 07:22:38.622315 [DEBUG] sofia.c:10485 IP 192.168.2.52 Approved by acl "domains[]". Access Granted.

I've got a feeling you've put User Agent subnets in your domain ACL. As per the ACL Documentation:

• Do not put your public ip or phone IP addresses in the domains access control list.
• The main purpose is for your carriers ip addresses. Add the carrier IP addresses to the CIDR.

Only your SIP provider's IP addresses should be in there.

 

[mc6650]

Thanks for pointing that out. I've now amended the ACL, however I still can't make outgoing calls.

 

[hfoster]

The default still seems to be set to allow, which will match everything, so everything will be treated as part of the public context.

 

[mc6650]

Okay
Here's the change I've made to the ACL. Unfortunately my gateway will now not register. Don't know if this is because of the ACL changes or what?

 

[hfoster]

Only thing I can imagine is if you're not using montreal9.voip.ms to register. That's definitely the correct set up. Have you done the usual things like flush cache and reloaded the ACL from SIP Status?

 

[mc6650]

For some reason the gateway isn't authenticating!

 

[mc6650]

Okay. Got the gateway to register, have the ACL as in my previous post (except have updated the proxy address), can make an internal call - extension to extension, however I now cannot make inbound or outbound calls. It seems like every-time I try and make a change to the system, something else fails. Is FusionPBX this fragile? I'm trying to move over from FreePBX where I've got the VoIP.ms trunk working in inbound and outbound calls. It took me about 15 minutes and one youtube video to do it. Sorry to dump on the forum, but this is very, very frustrating and I don't understand why it should be. Rant over!

 

[mc6650]

Update. The gateway is now registered and I can receive calls, however outbout still is working. When I look at the WireShark entry for a call I see an authentication error. This I don't understand if the gateway is registered. Please see the attached screen shots.

 

[mc6650]

Hello
Would someone be able to comment on the above post? I've also included the log files from the latest attempt to make an outgoing call. Thanks in advance for any help that can be provided.

 

[hfoster]

Is it possible voip.ms are rejecting it due to the lack of outbound caller ID?

 

[Adrian Fretwell]

The SIP error is a 503 which is a very general "Service Unavailable" error. You would normally expect to see this sort of error when a providers server was down for maintenance or similar. If the issue is caller ID I would have expected the provider to give you a more meaningful error.

If you get a packet capture you may see some more useful text/description associated with the 503 message.

 

[mc6650]

Hello
Thanks for the suggestions. Is the issue with the CLID? I see a reference to it in the attached screen shot. If it is, then where would insert the caller line ID?

 

[mc6650]

Outbound Route.

 

[hfoster]

You would stick that on the extension you are calling from Extensions -> Outbound Caller ID Number. It's a wild suggestion, so I can't say for definite why voip.ms rejected the call. It's just I've seen 503 errors used as a place holder error for a lot of misconfiguration over a couple of SIP providers. I think Wireshark doesn't understand what Remote-Party-ID for some reason.

Failing that, it might be worth seeing if it's possible to get voip.ms to let you know what the calls are rejected with packet captures.

 

[mc6650]

BingGo! Putting the DID number into the Extensions > Outbound Caller ID Number worked. All of the documentation I've read regarding VoIP.ms suggests the PBX is to supply the ClID, however none of it suggests putting the ID into the extension number. Is there a global setting for CLID within FusionPBX and the domain I'm working with (as opposed to each extension)? Thanks to all of the contributors their help and patients.