Solved Problem call extension via SIP ID - since v16 update!

[lohh]

Hi!

We have some extensions with a configuired SIP ID. The SID ID is used for a speed dial list to have easier numbers for specific extensions.
This worked fine in the last 4 years with all 3cx versions. Now, since the update to v16, the SIP ID numbers can not be dialed.

• We have two digit extensions
• The SIP ID ist unique per extension
• No changes to the config, except the update to v16
• google search without results!

In my understanding the 3cx should handle this calls as internal calls an no matching outbound rule is needed.

Example (extension 19 calling SIP ID 27 (extension 17)):

09/27/2019 11:14:07 PM - [CM50**]: Call(C:148): No known route from Extn:19 to target: <sip:27@...30:5060>

09/27/2019 11:14:07 PM - Call(C:148): from Extn:19 to 27 doesn't match any known extension number.

09/27/2019 11:14:07 PM - [Flow] Target endpoint for 27 can not be built!

09/27/2019 11:14:07 PM - [CM50**]: Call(C:148): Making route(s) from Extn:19 to <sip:27@...30:5060>

The internal 3cx phonebook does not know the connection between SIP ID 27 an extension 17.
Any ideas? Any knows changes in v16?

 

[leejor]

Did you allow direct SIP calls? That must now be done to enable SIP ID dialling.
See... https://www.3cx.com/community/threads/dial-0-for-reception-using-sip-id.64008/

 

[JohnS_3CX]

Hi @lohh

Check your Settings > Network > FQDN > Settings for Direct SIP Calls

and also take a look at this article for more general information on the subject https://www.3cx.com/docs/direct-sip/

 

[lohh]

Thank you! Thats the solution!

We use the alternative SIP ID function only for internal calls and I was thinking too, that "external" means external callers.

You can see the configuration (v15.5) before the v16 update in the screenshot. The checkbox is unchecked and that worked for the last 3 years.

Maybe you can add this adjustment to the changelog or give a special hint at the documention and the checkbox description?

Thanks a lot!

 

[Mark Phillips]

You can see the configuration (v15.5) before the v16 update in the screenshot. The checkbox is unchecked and that worked for the last 3 years.

Yes, this caught me out too when I upgraded to v16.

 

[JohnS_3CX]

Glad to hear it was resolved!