Skip to content
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]: SIP Alias - 'user.name' rejected because extension not found in context 'from-sip-external' #510

Open
iMiMx opened this issue Oct 18, 2024 · 1 comment
Labels
bug Something isn't working triage Triage

Comments

@iMiMx
Copy link

iMiMx commented Oct 18, 2024

FreePBX Version

FreePBX 17

Issue Description

Running FreePBX 17, all updates installed, with guest/anon SIP calls enabled.

New extension created, 511, I can successfully call [email protected] - the call is routed correctly.

I then added a SIP Alias to the extension 511 for user.name - then tried calling [email protected] but it results in:

NOTICE[478873] res_pjsip_session.c: anonymous: Call (UDP:xx.xx.xx.xx:31991) to extension 'user.name' rejected because extension not found in context 'from-sip-external'.

Forum post, confirmed bug by lgaetz:

https://community.freepbx.org/t/trying-to-call-sip-alias-results-in-rejected-because-extension-not-found-in-context-from-sip-external/101774/4

Operating Environment

FreePBX 17

Relevant log output

NOTICE[478873] res_pjsip_session.c: anonymous: Call (UDP:xx.xx.xx.xx:31991) to extension 'user.name' rejected because extension not found in context 'from-sip-external'.
@iMiMx
Copy link
Author

iMiMx commented Oct 18, 2024

Editing extensions.conf (/etc/asterisk), changing:

[from-sip-external]
exten => _X.,1,NoOp(Received incoming SIP connection from unknown peer to ${EXTEN})
exten => _X.,n,Set(DID=${IF($["${EXTEN:1:2}"=""]?s:${EXTEN})})
exten => _X.,n,Goto(s,1)

To:

[from-sip-external]
exten => _.,1,NoOp(Received incoming SIP connection from unknown peer to ${EXTEN})
exten => _.,n,Set(DID=${IF($["${EXTEN:1:2}"=""]?s:${EXTEN})})
exten => _.,n,Goto(s,1)

As suggested by lgaetz in the forum post, seems to resolve the issue - but obviously throws an 'altered file' warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage Triage
Projects
None yet
Development

No branches or pull requests

1 participant