Solved No Voicemail if call is manually declined in Teams client.

[Nico.ipn]

Hello !

We are testing Teams integration and Direct Routing.
Inbound and Outbound call from and to TEAMS (with Voice System activated) are working perfectly fine.

We are using : 18.0.1880 (Enterprise)
The case is :
UserA - External
UserB - TEAMS User direct routed via 3CX.

• UserA calls UserB
• Call is correctly delivered, popup is shown in UserB Teams interface.
• UserB decline manually the incoming call (by clicking on the red button in the teams interface)
• UserA has an announcement from his ISP : "Number called is not affected..."

There is no voicemail, so.

In the log :

09/15/2021 10:03:48 AM - [CM503003]: Call(C:27): Call to <sip:+33xxxxxxxx;[email protected]:0> has failed; Cause: 603 Decline/INVITE from 52.114.76.76:5061
09/15/2021 10:03:48 AM - Call to T:Extn:104@[Dev:sip:+33xxxxxxxx;[email protected]] from L:27.1[Line:10000<<+339xxxxxxxx] failed, cause: Cause: 603 Decline/INVITE from 52.114.76.76:5061

Do you have any clue on how to solve this issue, please ?

 

[NickD_3CX]

Hello !

We are testing Teams integration and Direct Routing.
Inbound and Outbound call from and to TEAMS (with Voice System activated) are working perfectly fine.

We are using : 18.0.1880 (Enterprise)
The case is :
UserA - External
UserB - TEAMS User direct routed via 3CX.

• UserA calls UserB
• Call is correctly delivered, popup is shown in UserB Teams interface.
• UserB decline manually the incoming call (by clicking on the red button in the teams interface)
• UserA has an announcement from his ISP : "Number called is not affected..."

There is no voicemail, so.

In the log :

09/15/2021 10:03:48 AM - [CM503003]: Call(C:27): Call to <sip:+33xxxxxxxx;[email protected]:0> has failed; Cause: 603 Decline/INVITE from 52.114.76.76:5061
09/15/2021 10:03:48 AM - Call to T:Extn:104@[Dev:sip:+33xxxxxxxx;[email protected]] from L:27.1[Line:10000<<+339xxxxxxxx] failed, cause: Cause: 603 Decline/INVITE from 52.114.76.76:5061

Do you have any clue on how to solve this issue, please ?

Hi!

Yes, we are aware of this and plan on addressing it in V18 Update 1.

Specifically what we will do is when Teams responds with a 603 message, the Forwarding Rules of the 3CX Extension will be triggered.
This way, you can control what happens when the call is rejected from your Teams client, exactly like if it was rejected from your IP Phone of softclient (End Call, send to VMail, etc...).

We don't currently have a release date for U1, but it should not be too far away.

 

[Nico.ipn]

Thank to you !
We will wait for the V18U1.