SOLVED Problems with outbound routes

[matt]

Hello everybody,

On my FusionPBX outbound routes are not working.

Call ends with 404 - No route destination

I have set up a gateway and I made an outbound route - but the rule never appears in the log...

 

[Boris Kovalenko]

AFAIK context "public" is for inbound routes? What is the context of your phones / local extensions?

 

[DigitalDaz]

As Boris says, somehow you have managed to get your calls landing in the public context, have you changed any access control lists by and chance?

 

[matt]

yes... i changed them...

192.168.1.0/24 is the local network
172.30.82.0/24 is a network with registered extensions - connected via a lan-lan connection
192.168.1.115 is the domain of the pbx

 

[Boris Kovalenko]

See, your outbound route (\d{7}) is in the context 192.168.1.115 while call is placed in the context "public"

 

[Boris Kovalenko]

To not break the ideolody and not to twist your and our minds: the context "public" is for external calls only. Place there external gateways and inbound routes only. And place your registered extensions and outbound routes in the context of domain (192.168.115 in your case).

 

[matt]

I´m afraid the ACLs are not proper configured... i tried it till the calls from the ISDN Gateway worked - but now all calls are in public context...

 

[Boris Kovalenko]

Matt, ok, calls are. But routes aren't? On your second screenshot the route sipcall.7d is in context 192.168.1.115

 

[matt]

yes...

 

[matt]

after i changed the context of the route to public it worked - but that can´t be the proper way

 

[Boris Kovalenko]

The proper way is to place your registered extensions (61 in your case) in context 192.168.1.115 (see the field context on extension configuration page).

 

[matt]

they are in the context 192.168.1.115...

if i take out the allow 192.168.1.0/24 from ACL Domain and use just 192.168.1.116 (IP of the ISDN Gateway) i get:

2017-11-08 16:39:14.729221 [DEBUG] sofia.c:9873 sofia/internal/0676841032500@192.168.1.115 receiving invite from 192.168.1.116:5060 version: 1.6.19 -36-7a77e0b 64bit
2017-11-08 16:39:14.729221 [DEBUG] sofia.c:10044 IP 192.168.1.116 Rejected by acl "domains". Falling back to Digest auth.
2017-11-08 16:39:14.729221 [WARNING] sofia_reg.c:1792 SIP auth challenge (INVITE) on sofia profile 'internal' for [60@192.168.1.115] from ip 192.168.1.116
2017-11-08 16:39:14.729221 [DEBUG] switch_core_state_machine.c:603 (sofia/internal/0676841032500@192.168.1.115) State NEW
2017-11-08 16:39:14.729221 [DEBUG] sofia.c:2334 detaching session cabb2f05-4f4b-4589-9d6d-11677c0900dd
2017-11-08 16:39:14.749243 [DEBUG] sofia.c:2442 Re-attaching to session cabb2f05-4f4b-4589-9d6d-11677c0900dd
2017-11-08 16:39:14.749243 [DEBUG] sofia.c:9873 sofia/internal/0676841032500@192.168.1.115 receiving invite from 192.168.1.116:5060 version: 1.6.19 -36-7a77e0b 64bit
2017-11-08 16:39:14.749243 [DEBUG] sofia.c:10044 IP 192.168.1.116 Rejected by acl "domains". Falling back to Digest auth.
2017-11-08 16:39:14.769248 [DEBUG] freeswitch_lua.cpp:365 DBH handle 0x7fbdfc0479c0 Connected.
2017-11-08 16:39:14.769248 [DEBUG] freeswitch_lua.cpp:382 DBH handle 0x7fbdfc0479c0 released.
2017-11-08 16:39:14.769248 [WARNING] sofia_reg.c:2906 Can't find user [berofix@192.168.1.115] from 192.168.1.116
You must define a domain called '192.168.1.115' in your directory and add a user with the id="berofix" attribute
and you must configure your device to use the proper domain in it's authentication credentials.
2017-11-08 16:39:14.769248 [WARNING] sofia_reg.c:1737 SIP auth failure (INVITE) on sofia profile 'internal' for [60@192.168.1.115] from ip 192.168.1.116
2017-11-08 16:39:14.769248 [NOTICE] sofia.c:2332 Hangup sofia/internal/0676841032500@192.168.1.115 [CS_NEW] [CALL_REJECTED]

 

[matt]

SOLVED:

ACL Domains: CIDR 192.168.1.116/32 instead of 192.168.1.0/24

now everything is in the right context...

 

[Boris Kovalenko]

Right way is to use 192.168.1.116/32. Also have You invoked "reloadacl" command after ACL change?

 

[matt]

yes and "flush memchache" too...
THX for your help

 

[DigitalDaz]

The ONLY thing that you should add to the domains acl is carriers, nothing else.