I am used to configuring VoIP extensions with FreePBX but now I have a strange case where I need to receive a call from an Akuvox device that I can’t reconfigure in the best way for FreePBX, so I can cater to other requirements (and because the UI offers limited options for what I need).
The device doesn’t register a SIP account, and always calls the same way.
On the device side, this is what it claims it’s doing:
I think you can do it by defining it as a trunk, but setting the context to “from-internal”. You might also find a solution which defines it as a trunk, with the default context, and uses the number it dials as the DID.
It is also possible that the restriction that extensions much be incoming registration and incoming authentication has been removed since FreePBX 13, for which online documentation is available.
David, thank you for your answer. I am in a support case with Akuvox trying to get a better solution, but I don’t think it’s going anywhere and I hope to try your suggestions next week. Thanks.
Situations like that in FreePBX can be confusing, especially when a device shows up making calls but isn’t clearly listed in the endpoint configuration. I’ve seen cases where it turned out to be an old extension still registered or a SIP device using cached credentials. Checking the active registrations and call logs usually helps track down which endpoint is actually placing the call.
Just to provide some feedback here, eventually with the help of Akuvox Support I was able to configure things in the device, in a way that avoids this problem.
The trick was to upgrade the firmware, which I had previously tried to do but it wouldn’t work. Their support gave me an intermediate version (mine was really old) and I was finally able to complete the firmware upgrade in two separate steps, up to the latest.
With the new firmware, I can specify normal full SIP addresses, and get the device to call to 2 different servers (FreePBX+online SIP account for mobile) correctly.
