Search results

I see same behaviour of phones behind NAT when the RPORT is turned off. If your phone is behind the NAT please check RPORT is on and also check your router's SIP ALG is off.

Hello! I need help in very strange problem.... There is "bind_digit_action" extension in "dialplan manager" which activates feature codes and escpecially for attended transfer. So we have 2 caller. A is outside of FusionPBX, B is registered with FusionPBX. 1) A calls B. B wants to transfer a...

That was a bug in latest master branch. mcrane fixed it already

Hello! I'm wondering what I did wrong. But now my "Alternate destination" in "Time condition app" has duplicate entries. Screenshot: https://snag.gy/2WJFsE.jpg How may I fix this? Regards, Boris

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

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, ok, calls are. But routes aren't? On your second screenshot the route sipcall.7d is in context 192.168.1.115

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).

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

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

Hello! I need to run ring_ready application on each inbound call in the public context. Yes, I may add this line of code to each inbound route, but my idea is other. There are "extensions" in the inbound routes called "caller-details" and "not-found". So I want to create my own "ring_ready...