I have callmanager version 9.1.2 and on-prem Webex Meeting Server (188.8.131.523A). The "callme" function works but webex tags on a +1 to any number it calls. I can strip off the +1 with a translation pattern which works for Cisco phones but am not sure how to handle numbers that need to go to PSTN. Do I need transformation pattern to strip +1 and add 9? Can this be done at the sip trunk level?
I am assuming webex uses the numbers that it finds through AD. The question is, how does your webex server route a call to PSTN, if it connects to CUCM using a SIP trunk, you can put the sip trunk in its own CSS that has a translation pattern that strips the +1 and prefixes a 9.
============================= Please remember to rate useful posts, by clicking on the stars below.
Please remember to rate useful posts, by clicking on the stars below.
My dilema is that stripping the +1 will work for all internal phones registered to our callmanager cluster. The example is that 605123XXXX is a callmanager registered phone, but 605234XXXX is a local call to the pstn while 605345XXXX is long distance still within the same state. We also have 40+ locations spread across several other states. I'm looking for an efficient way to manage calls to pstn without having a specific translation pattern for every scenario.
Re: Callmanager handling +1 inbound calls from Webex
First of all, for internal calls CWMS should not prefix + and a country code. There's an option on the call me - something like call internal number. If a user dials a number using this option it will ring internal extension without requiring any digit manipulation. Otherwise, for PSTN calls you select the country flag for the destination you are calling and it adds + and the respective country code.
You can simply setup a translation pattern stripping + and prefixing an access code 9 or 0 or whatever and your existing call routing will take care of rest.
I had done a CWMS implementation few months back and it worked fine for me. Not remember exactly if I used TP or RP but I didn't had any issue.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...