-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug]: ENUM trunks only work with chan_sip #495
Comments
Hi @JoseGoncalves , Can you make the dialplan change on your systemV17 system and let us know its working with PJSIP or not? Change details
To make this change on your system, just copy the below dialplan in to extensions_override_freepbx.conf file.
Run dialplan reload in asterisk cli and then test the calls with ENUM trunk. |
It does not work, but now it gives me a different error:
|
HI @JoseGoncalves Is it possible for you to test the call from the PJSIP extension? |
Not now... I'm not on my office, and remotely I can only use IAX2 to make calls... later on the day I will try it when I reach my office. |
Hi @ramarajan222. It works from a PJSIP extension. Here is the relevant log:
So, the only issue remaining is when I make a call from an IAX2 extension. |
Thank you for the update @JoseGoncalves, Need to modify the dial command to fix it with IAX2 extension. |
FreePBX Version
FreePBX 17
Issue Description
I had a FreePBX 15 system were I used an ENUM trunk to connect to a remote institute. After migrated that system to FreePBX 17 with Asterisk 20 and
chan_sip
disabled, I was unable to communicate with that trunk!Looking at Asterisk logs I see this when I try to make a call on that trunk:
Only after enabling
chan_sip
I was able to restore the calls with it.So it seems ENUM trunks need to be updated to support
chan_pjsip
, or else, they are useless with Asterisk 21 or 22, werechan_sip
is unavailable.Operating Environment
Debian 12
Asterisk 20.9.3
Relevant log output
The text was updated successfully, but these errors were encountered: