3CX V18: Connecting Teams & Customers - Faster, Better, More Efficiently

[N_G]

@liss @jaywagener It should not be that way. Our integrations script covers most teams configurations but sometimes it needs adjustment. Please contact support or post more details so we can see what is wrong in the configuration.

@Frederick Marcoux I dont know who "they" is but I am not against anything that helps 3CX The right time for teams integration was now. Dont forget there was skype, lync, office communication server etc etc and luckily we did not waste time on integration with those products. Now teams is a more standard product and direction is clearer. I believe that Microsoft will not focus on the phone system part of things and that for all companies that require more than basic in and out calling, 3CX will be needed (i.e. if you need IVR< call queues, live chat etc)

 

[StefanW]

Microsoft is sending a 603 DECLINE

603 I would drill down to two common cases. The ssl cert does not validate or the extension number is not matching. But also keep
In mind that the setup can take up to hours once you run the command

 

[StefanW]

Existing webmeeting links which have been sent out to customers take you to v16 webmeeting, yet if you join the meeting from within the v18 desktop app or webclient, you end up in a v18 meeting without any other participants
- Webmeeting links open a browser window even if the desktop app is installed

both are intended to work like this. The desktop app in the back also “only” opens an inline browser. Reg. The links, this we documented a while ago. They are also only valid for 30 days and then exp. on the
Old platform post upgrade.

https://www.3cx.com/blog/news/v18-video-conferencing/

 

[jaywagener]

@liss @jaywagener It should not be that way. Our integrations script covers most teams configurations but sometimes it needs adjustment. Please contact support or post more details so we can see what is wrong in the configuration.

@Frederick Marcoux I dont know who "they" is but I am not against anything that helps 3CX The right time for teams integration was now. Dont forget there was skype, lync, office communication server etc etc and luckily we did not waste time on integration with those products. Now teams is a more standard product and direction is clearer. I believe that Microsoft will not focus on the phone system part of things and that for all companies that require more than basic in and out calling, 3CX will be needed (i.e. if you need IVR< call queues, live chat etc)

Hello Nick, thanks for the response. I have an open case with support and was told that unfortunately, this is normal behavior. The extension is "known" and correct, as the Activity log provides me the error that the endpoint has no forwarding rule on reason "Forbidden":

08/16/2021 11:30:05 AM - L:63.2[Extn:1001]: destroying InvADS.ADS(295748)

08/16/2021 11:30:05 AM - [Flow] Endpoint Extn:1001 has no forwarding rule on reason 'Forbidden'

08/16/2021 11:30:05 AM - L:63.1[Line:10000<<(number removed)] failed to reach Extn:1001, reason Forbidden

08/16/2021 11:30:05 AM - Leg L:63.2[Extn:1001] is terminated: Cause: 603 Decline/INVITE from 52.114.132.46:5061

08/16/2021 11:30:05 AM - Call(C:63), Extn:1001 on entry: DlgInfo(63-1665/Terminated / R)

08/16/2021 11:30:05 AM - Notify dialog-info: Extn:1001: sip:+1(number removed)5;ext=[email protected], Call(C:63)

 

[Evolute IT]

Hello Nick, thanks for the response. I have an open case with support and was told that unfortunately, this is normal behavior. The extension is "known" and correct, as the Activity log provides me the error that the endpoint has no forwarding rule on reason "Forbidden":

08/16/2021 11:30:05 AM - L:63.2[Extn:1001]: destroying InvADS.ADS(295748)

08/16/2021 11:30:05 AM - [Flow] Endpoint Extn:1001 has no forwarding rule on reason 'Forbidden'

08/16/2021 11:30:05 AM - L:63.1[Line:10000<<(number removed)] failed to reach Extn:1001, reason Forbidden

08/16/2021 11:30:05 AM - Leg L:63.2[Extn:1001] is terminated: Cause: 603 Decline/INVITE from 52.114.132.46:5061

08/16/2021 11:30:05 AM - Call(C:63), Extn:1001 on entry: DlgInfo(63-1665/Terminated / R)

08/16/2021 11:30:05 AM - Notify dialog-info: Extn:1001: sip:+1(number removed)5;ext=[email protected], Call(C:63)

Could the extension have an exception for some calls or even on the phones themselves? Like a blacklist.

 

[jaywagener]

Could the extension have an exception for some calls or even on the phones themselves? Like a blacklist.

I don't see any exceptions or blacklisted numbers. It's a brand new build and I haven't programmed any exceptions or blacklists either. Just very curious behavior. I can answer it normally if using a 3CX softphone and rejections/direct to VM route as they should, to the user's VM box. It just seems to be the rejection from Teams. They send a 603 back to the 3CX and the system just drops the call after that.

 

[FridayIT]

Hello Nick, thanks for the response. I have an open case with support and was told that unfortunately, this is normal behavior. The extension is "known" and correct, as the Activity log provides me the error that the endpoint has no forwarding rule on reason "Forbidden":

Check to make sure you have an outbound rule that supports this, if memory serves when forwarding is done by the system, a rule without a group needs to be set. I ran into this same issue a while back

 

[jaywagener]

Check to make sure you have an outbound rule that supports this, if memory serves when forwarding is done by the system, a rule without a group needs to be set. I ran into this same issue a while back

Thanks for the suggestion. These users are all in the AzureAD group so I added it to the default Outbound rule. Unfortunately, when the call is manually rejected in Teams, we get the same result, the call drops.

Originally, the Outbound rule had no group assigned to it.

 

[N_G]

@jaywagener @liss - let me have your support case numbers by PM and we will look into your teams configuration......

 

[StefanW]

Is anyone else seeing this in the teams integration. Inbound call gets declined from the teams side and the call drops with the remote party hearing a call can not be completed or another error message (depending on carrier)?

I strangely hat this one morning after it had worked well for weeks. Once I started the desktop app, the issue stopped however when I only used the mobile app, all calls failed. MS Support to clear some cache in the app which did not resolve my issue while not using the desktop app in tandem. I removed on my iOS device the app and reinstalled it and 10m later all was back to normal. Would this fit your situation? Do you still have any other SBC configuration in your teams tenant?

 

[StefanW]

when the call is manually rejected in Teams

This might be a flow that is currently not covered. We also noticed that the SIP decline messages are vastly different, for whatever reason, if you do this from the Desktop, Android or iOS app... Lync...

 

[PhilK]

I see your use case, for my company it's a godsend to send to voicemail. We force all calls into different teams for every member on the team. Business cards etc have that queue number instead. When a caller calls, if the person they are looking for is busy the caller gets offered to be sent to the team members voicemailbox or take a message. Many people who call will happily say, send me to there voicemail box. But I see your point on adding a system parameter or a flag to disable that option.

I see your case as well but I think there is a little missunderstanding here. As you describe your case, I think you mean for example forwarding rules and above all you have enabled all the mailboxes. What I'm talking about is the forwarding when I have someone on my phone. Sorry for my english, maybe it is better called the transfering of a call.
This is what I'm talking about.

And in our case, we have disabled all mailboxes in the extensions, and when we transfer the call and I look for a name or the extension of a colleague, there is his extension and the extensions mailbox listed, where I can forward to. Some colleagues have problems with this and they don't see the difference and transfer the call to the mailbox, where it says the caller, that the extensions mailbox is disabled.
So the question is not why the mailbox is listed here generally, the question is, why is it listed for extensions where the mailbox is disabled.

 

[Digital221]

Is there an ETA for Windows v18 release?

 

[NickD_3CX]

Is there an ETA for Windows v18 release?

It will probably be at least a few more weeks before we release V18 for Windows, but we are certainly planning on doing so.

 

[fgc92210]

Any update on the ticketing system which was supposed to be part of V18?

 

[NickD_3CX]

Any update on the ticketing system which was supposed to be part of V18?

No, currently it's planned for a future update within the lifetime of V18. No ETA though.

 

[jaywagener]

@jaywagener @liss - let me have your support case numbers by PM and we will look into your teams configuration......

It doesn't allow me to PM you. You may need to initiate the conversation.

 

[grp_cyr]

Chrome Extension V18
|
Hi team!
Can anybody tell me if there will be a browser extension on V18 for Chrome and or Edge?

The V18 app took place of extensions.

 

[fabs]

Hello
is there already an approximate release date for the ios app v18?

Regards
fabs

 

[jaywagener]

I strangely hat this one morning after it had worked well for weeks. Once I started the desktop app, the issue stopped however when I only used the mobile app, all calls failed. MS Support to clear some cache in the app which did not resolve my issue while not using the desktop app in tandem. I removed on my iOS device the app and reinstalled it and 10m later all was back to normal. Would this fit your situation? Do you still have any other SBC configuration in your teams tenant?

@StefanW Thanks for the idea. I tried uninstalling both my desktop and mobile Teams app to no avail.

We do have multiple Voice Routing configs setup in our tenant but no actual SBCs except for the 3CX SBC. We are only using the 3CX provided routes, usage, calling policies and dial plans for this testing. Our next step (to rule out MS) would be to create a new tenant and start fresh. I am not optimistic about this plan though as we use direct routing with another PBX vendor and the 603 DECLINE messages get sent to the user's PBX VM as expected. This setup is in the same tenant as well. See support ticket 788254 for more details.