We're running CUCM 8.6.2 and CUPS 8.5.4 and our users are running version 8.5.5 of the CUPC client.
When they make an outbound call from their phone to a PSTN number, they are using a 0 for an outside line. On the gateway, we remove the 0 and normalize the called number to be a E.164 number as our provider is requireing this from us.
So as an example, if a user dials 0021234567 (Belgian number), we translate this on the gateway to 3221234567 and send it on to the provider.
If I check my call history on the phone, the called numbers are there exactly as dialed (in our example 0021234567). Wen I check the call history on the CUPC client, the called numbers are there the way they were translated on the gateway (in our example 3221234567). When I call back from the phone, it works, but when I call back from the CUPC client, the call fails because it cannot match any router pattern.
Is there any way we can have the call history in the CUPC client the same as on the phone?
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...