SOLVED No Route

[kristiam garcia]

good morning

A clean install of fusionpbx was done, 2 extensions were configured and they are called between them without problems, then a gateway was set up against an asterisk for outgoing calls, it was tried and it worked correctly, after a restart of the server I stopped making calls That I can see is:

before
[INFO] mod_dialplan_xml.c: 637 Processing 3401 <3401> -> 3400 in context 192.168.230.3

After
[INFO] mod_dialplan_xml.c: 637 Processing 3401 <3401> -> 3400 in context public

The serious question because it changes the context and how it is solved, I hope they can help me since I want to put this into production.

 

[Ricky]

Hello Kristiam,

If your are using Freepbx you may want to ensure that the firewall settings on the device is allowing your Fusionpbx IP as a trusted subnet.

 

[kristiam garcia]

I am running pure asterisk for the gateway with the pstn

 

[DigitalDaz]

good morning

A clean install of fusionpbx was done, 2 extensions were configured and they are called between them without problems, then a gateway was set up against an asterisk for outgoing calls, it was tried and it worked correctly, after a restart of the server I stopped making calls That I can see is:

before
[INFO] mod_dialplan_xml.c: 637 Processing 3401 <3401> -> 3400 in context 192.168.230.3

After
[INFO] mod_dialplan_xml.c: 637 Processing 3401 <3401> -> 3400 in context public

The serious question because it changes the context and how it is solved, I hope they can help me since I want to put this into production.

This would imply that a change has been made to an ACL, that would cause it to go into the public context.

 

[kristiam garcia]

This would imply that a change has been made to an ACL, that would cause it to go into the public context.

friend these are my acl



Just change the one that comes by default from:


a:


What would be the mistake and excuse my ingnorance

 

[kristiam garcia]

I had reason friend, an acl so wide was the reason of my problem.

I solved it by placing more specific acl's such as:
192.168.230.2/32
192.168.203.10/32

Thanks for the help

 

[DigitalDaz]

ACL are for putting carriers in, not yourself but even carriers do not need to go in acl if they can send to port 5080.

Why did you add those to the ACL? Remove them if they are not your carriers

 

[kristiam garcia]

ACL are for putting carriers in, not yourself but even carriers do not need to go in acl if they can send to port 5080.

Why did you add those to the ACL? Remove them if they are not your carriers

Ok understood, I already know what the acl is, thank you, I will continue to consult this forum to get the system in production thank again