CSCvq50611 - Webex Teams UC calling does not support Application dial rules like Cisco Jabber does

Matthew Miktus · ‎04-14-2020

has there been any progress on this?

between the move from Jabber to Teams and the newly released MSFTTeams integration, AppDialRules are now an issue as MSFTTeams doesn't sync IPPHONE but uses TelephoneNumber which we have set for the full 10-digit number.

Rao29 · ‎06-01-2020

Hi Matthew,
I have open a TAC - Partially, fix by creating a new CSS, Partition and Route Pattern and added that new CSS to the CSF device profile - I can now dial out from Webex Teams but, outbound calls fails in Desktop Control mode as the call is rejected by the desk phone which doesn't recognise this route pattern.

How are you coping with this issue - Do you have a workaround in place ?

Thanks,
Rao

Matthew Miktus · ‎06-01-2020

4-digit extension dialing works.

It was click-to-call where the full 10-digit number is pulled from a contact card where ours failed. I found when pulled from AD >> WebexCalling in MS Teams pulled the full "work number" and not the IPPHone. To work around this, I created called-party transformation patterns to catch our numbers with & without the prefix (we use an 8 to dial out) so

1) 81201XXX.XXXX - strip pre-dot

2) 1201XXX.XXXX - strip pre-dot

applied this to the partition we use for transforming CALLED numbers (xform-sip-cld-pt). This caught the number on the way in from the application and converted it to a 4-digit extension that would then match existing DN's in the database.

I created one for every combination of Area-Code/Number combinations. since we only have 4 ranges, it requires 8 patterns, but it's quick and fairly painless..

Rao29 · ‎06-02-2020

I'm only using webex Teams & Jabber - Internal calls (5 digit numbers) has always work for me - It's only outbound 10 Digit calling numbers that were failing when NO prefix was applied.

Worked with TAC again on this today - Made a few test calls today with 10-digit numbers - So, dialing out from Desktop/Mac Teams is working.
The Application Dial rules under CUCM > Call Routing > Dial Rules > Application Dial Rules is now working for Teams Desktop/Mac.
So, I just had to add a rule to prepend a "91" while dialing 10-digit numbers and that worked with my existing route pattern/CSS for Desktop/Mac Teams.

++ But, the same APP Dial Rules still doesn't work for IOS/Android cell phones - Workaround: Create a different route pattern, partition and CSS which strip pre-dot. Then, assigned that new CSS to the TCT/BOT device.

dashaffe · ‎08-03-2021

Good Morning:

I'm reading through this. I have a work around that does not involve adding dialing plans. I'm not sure how this will impact most of you. But in the directory synchronization program, you can set the IPPhone field to be the one that goes to the telephone number on the WebEx side. I'm not sure if this is a recent addition to the directory sync program in that we have only started to try WebEx App, or WebEx Teams whatever the current name is. I've successfully done this, and performed a full sync and in our case the six digit extension now shows in place of the standard 10 digit.

A couple of other things. First, I can't get any other numbers to even show up in WebEx. The directory sync is sending them because Cisco TAC can see those other numbers. But I can't look at a user for example and see that I have sent a mobile, or fax number to the cloud platform. But Cisco TAC can see that. I've been told that this visibility is being worked on. But I'll believe it when I see it.

Also, application dial rules on our premise Call Manager system do not work with WebEx Teams. This is disappointing and I think what lead initially to this thread.

I can't say I'm thrilled with what I've seen in WebEx App (Teams). It's just a rehash of Microsoft Teams. Too bad we can't integrate the Call Manager features with Microsoft Teams for a unified platform. Yes, I know there is a Jabber app on MS Teams, but it really isn't what I'm looking for either.

Dave