Solved Can't call outside

[leonardorebelo]

Hi i setup the 3cx teams integration:

but i can't call outside , it says " the person you're trying to reach isn't available.

Can somebody help me?

 

[NickD_3CX]

Hi!

OK, before starting external calls, let's take a step back:

• What happens when you dial *777 ?
• What happens if you dial another 3CX Extension Number that you have configured on your 3CX Mobile App?
• What happens when another Extension tries to dial the 3CX Extensions that you have synced with Teams

You can set 3CX to Verbose Logging from the Activity Log settings, then make another call attempt and check the Activity Log for clues what the error is saying.

Btw, did you switch the certificate you were using which was a wildcard one?

 

[leonardorebelo]

hi!

yes i got a new ssl (not a wildcard this time )

If i call *777 i got this:

if i call a other extension than it works perfectly

 

[NickD_3CX]

*777 is the Echo Test extension of 3CX and is available in all installations. If you dial it from another extension it should work, so first make sure this is OK.

If it works from another extension, check the Dial Plan in your Teams Admin portal and check the Normalization rules and see if there is an entry for *777.

 

[leonardorebelo]

ok i found the error, another question if i call my DID from my sip , i receive the call on the 3xc app but not on teams.

can i make it possible to receive on the teams too?

i use now a ring group 8000

 

[NickD_3CX]

• What happens when another Extension tries to dial the 3CX Extensions that you have synced with Teams

Again, first try the simple scenario, what happens in this case?

 

[leonardorebelo]

Hi NickD_3cx , in that scenario everything works.

 

[NickD_3CX]

Hi NickD_3cx , in that scenario everything works.

OK, so this means that outbound and inbound calls from/to your Teams Client are OK and most likely the Teams integration is setup correctly, otherwise this wouldn't be possible.

You say currently the Inbound Rule sends call to an Extension. Change it temporarily to go directly to the Extension you have done the Teams integration with. Also on the same extension register your 3CX Mobile App.
When you call this DID, does it ring both client?

 

[leonardorebelo]

Hi Nick!

If i change it to a extension with the teams integration, than it works, i got the call on teams

 

[NickD_3CX]

Great!
So calls from Teams work, calls to Teams work, is everything OK now?

 

[leonardorebelo]

hI ! Internal calls yes but not to external.

 

[NickD_3CX]

Did you change your Inbound rule to point directly to your Teams Extension, you called this DID and the Teams Client didn't ring?

 

[leonardorebelo]

yes i mean i can't call outside from teams app but it works from 3cx

 

[NickD_3CX]

Now you need to check the Activity Log to see why Outbound Calls are failing.
If I had to guess, all External Numbers dialed by Teams are in e164 format (starting with a '+' symbol).

Adjust your Outbound Rule(s) so that they also match this case.

 

[leonardorebelo]

yes true they are using +32 . can you help me what i have to change ?

 

[NickD_3CX]

View attachment 27243 yes true they are using +32 . can you help me what i have to change ?

So the matching of the Outbound Rule will be OK as you have selected Extension Groups. The question is, does your provider support dialing a number in format +32xxxxxxxx?

Do me a favor, from a 3CX client, not Teams, dial a Belgium number in this format +32xxxxxxx. Does it work?
How to you usually dial a local and international number from your 3CX Client?

 

[leonardorebelo]

Hi if i call +32 from 3cx it works perfectly, normally for a local number we use 0 so 0345455...
But its not a big deal if we will use +32 . but i just don't know how to set it up .

here is the log from teams call to external :

01/19/2022 8:52:11 AM - [CM503020]: Call(C:41): Normal call termination. Call originator: Extn:1005. Reason: Not found
01/19/2022 8:52:11 AM - [CM503016]: Call(C:41): Attempt to reach <sip:[email protected]:5062> from Extn:1005 has failed. Reason: Not Found
01/19/2022 8:52:11 AM - [CM503014]: Call(C:41): No known route from Extn:1005 to target: <sip:[email protected]:5062/UDP>
01/19/2022 8:52:11 AM - Call(C:41): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.
01/19/2022 8:52:11 AM - [Flow] Target endpoint for +32475623866 can not be built!






1/19/2022 8:53:28 AM - [CM503020]: Call(C:42): Normal call termination. Call originator: Extn:1005. Reason: Not found
01/19/2022 8:53:28 AM - [CM503016]: Call(C:42): Attempt to reach <sip:[email protected]:5062> from Extn:1005 has failed. Reason: Not Found
01/19/2022 8:53:28 AM - [CM503014]: Call(C:42): No known route from Extn:1005 to target: <sip:[email protected]:5062/UDP>
01/19/2022 8:53:28 AM - Call(C:42): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.
01/19/2022 8:53:28 AM - [Flow] Target endpoint for +32475623866 can not be built!
01/19/2022 8:53:28 AM - Looking for outbound rule: dialed = [+32475623866], processed: [475623866]; from-ext:
01/19/2022 8:53:28 AM - [Flow] Building target endpoint to +32475623866 from "Leonardo Rebelo" <sip:[email protected]:5061>
01/19/2022 8:53:28 AM - [CM503010]: Call(C:42): Making route(s) from Extn:1005 to <sip:[email protected]:5062/UDP>




01/19/2022 8:56:05 AM - [CM503016]: Call(C:44): Attempt to reach <sip:[email protected]:5062> from Extn:1005 has failed. Reason: Not Found
01/19/2022 8:56:05 AM - [CM503014]: Call(C:44): No known route from Extn:1005 to target: <sip:[email protected]:5062/UDP>
01/19/2022 8:56:05 AM - Call(C:44): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.

 

[NickD_3CX]

Hi if i call +32 from 3cx it works perfectly, normally for a local number we use 0 so 0345455...
But its not a big deal if we will use +32 . but i just don't know how to set it up .

here is the log from teams call to external :

01/19/2022 8:52:11 AM - [CM503020]: Call(C:41): Normal call termination. Call originator: Extn:1005. Reason: Not found
01/19/2022 8:52:11 AM - [CM503016]: Call(C:41): Attempt to reach <sip:[email protected]:5062> from Extn:1005 has failed. Reason: Not Found
01/19/2022 8:52:11 AM - [CM503014]: Call(C:41): No known route from Extn:1005 to target: <sip:[email protected]:5062/UDP>
01/19/2022 8:52:11 AM - Call(C:41): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.
01/19/2022 8:52:11 AM - [Flow] Target endpoint for +32475623866 can not be built!






1/19/2022 8:53:28 AM - [CM503020]: Call(C:42): Normal call termination. Call originator: Extn:1005. Reason: Not found
01/19/2022 8:53:28 AM - [CM503016]: Call(C:42): Attempt to reach <sip:[email protected]:5062> from Extn:1005 has failed. Reason: Not Found
01/19/2022 8:53:28 AM - [CM503014]: Call(C:42): No known route from Extn:1005 to target: <sip:[email protected]:5062/UDP>
01/19/2022 8:53:28 AM - Call(C:42): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.
01/19/2022 8:53:28 AM - [Flow] Target endpoint for +32475623866 can not be built!
01/19/2022 8:53:28 AM - Looking for outbound rule: dialed = [+32475623866], processed: [475623866]; from-ext:
01/19/2022 8:53:28 AM - [Flow] Building target endpoint to +32475623866 from "Leonardo Rebelo" <sip:[email protected]:5061>
01/19/2022 8:53:28 AM - [CM503010]: Call(C:42): Making route(s) from Extn:1005 to <sip:[email protected]:5062/UDP>




01/19/2022 8:56:05 AM - [CM503016]: Call(C:44): Attempt to reach <sip:[email protected]:5062> from Extn:1005 has failed. Reason: Not Found
01/19/2022 8:56:05 AM - [CM503014]: Call(C:44): No known route from Extn:1005 to target: <sip:[email protected]:5062/UDP>
01/19/2022 8:56:05 AM - Call(C:44): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.

Your answer is in this line:

01/19/2022 8:56:05 AM - Call(C:44): from Extn:1005 to +32475623866 doesn't match any outbound rule. No outbound rule could be selected.

So there is something with the matching of the Rule. Remove the Extension Groups from the Outbound Rule and as a test, in the prefix put 0-9,+.

 

[leonardorebelo]

Worked perfectyl! thank you a lot Nick

 

[NickD_3CX]

Worked perfectyl! thank you a lot Nick

Good news!