Direct URI / Direct SIP - what's possible, what's not possible

[Ed_S]

Hi there,

Loving the system, migrated a small home setup to 3CX in about 30 minutes - rather than the days it took with FreePBX initially. Everything with the siptrunk, physical phones, voicemail etc, is all functioning. However, I have a couple of questions that I'm struggling to find the answers to with regards to direct sip calls.

I followed the below, set everything up, SRV records (which were already in place) modified for the new 3CX setup.

https://www.3cx.com/blog/voip-howto/direct-sip/

1. Should I be able to use the 3CX user webclient, to dial a direct URI/SIP? The web client rings my desk phone, I pick it up, but then it hangs up. I see something similar to the below in the logs, so presumably this is not possible?

04/23/2018 4:54:46 PM - [Flow] Target endpoint for sipthetestcallsip2sipinfo can not be built!

2. Is it possible to map an extension, say 123, to dial a remote direct sip/URI call such as [email protected] or [email protected]? My desk phone does not have the option to dial URIs, so I was thinking this might be a workaround (or the above, point 1, but I cant get that to work).

3. As far as I can tell 3CX should not require an additional outbound rule for direct sip/URI? At the moment I have just the one, for regular phone calls, via the SIP trunk.

Many thanks for any pointers you can give me,

Ed

 

[Ed_S]

Ah ha, found the verbose logging:

04/23/2018 6:02:36 PM - Call(C:22): from Extn:511 to testtimesip5060net doesn't match any outbound rule. No outbound rule could be selected.
04/23/2018 6:02:36 PM - [Flow] Target endpoint for testtimesip5060net can not be built!

So, looks like I can answer my 3rd question, which may resolve question 1, I need to determine the correct outbound rule.

 

[leejor]

I don't think you will be able to direct dial a URL directly from a phone (extension) connected to 3CX. What you may be able to do, if you call certain URLs on a regular basis, is to create each as a separate trunk group. Set them to NOT register. You'd have to create outbound rules that sent the direct dial number, out on the new trunk group, which might require a prefix, to distinguish from internal calls, if only using 3 digits.

I have not tried this myself.

 

[Ed_S]

Thanks for the reply - so direct URI is ingress to 3CX (which it translates to an extension), as opposed to egress/bi-directional?

 

[leejor]

What are you trying to achieve? I assumed it was the ability to dial a user at a URL. Are you trying to allow Direct SIP incoming (which should be much easier) as well?

 

[Ed_S]

What are you trying to achieve? I assumed it was the ability to dial a user at a URL.

Spot on, so I can call my ISP support over SIP - [email protected] - the various UI options I see such as 'SIP ID' on the Extension, does this relate to ingress calls only i.e mapping to an extension rather than from?

Are you trying to allow Direct SIP incoming (which should be much easier) as well?

I believe this is all configured, I followed the guide, setup/tested the SRV records, have the required ports open etc.

 

[leejor]

the various UI options I see such as 'SIP ID' on the Extension, does this relate to ingress calls only i.e mapping to an extension rather than from?

Yes, the SIP ID is for calls to the extension, from both outside, and inside. You can dial the SIP ID from another extension even if it is not the same as the extension number.