Under normal conditions, calls arrive from the PSTN via the H323 gateway to CUCM. CUCM uses Calling Number Transformation patterns on the gateway device pool to transform the calling number into E164 format e.g. 296662600 gets translated to +61296662600
When calling a Cisco IP Phone in SRST mode, the calling numbers are translated using the "translation-profile outgoing toPhone"
e.g. 296662600 gets translated to +61296662600
When calling the hunt pilot number 95555000 when the router is in SRST mode (call-manager-fallback), The calling number displayed on the hunt group member phone is "296662600 From: +61296662600"
The calling history (Missed, Received calls etc) of that phone shows the pre-translated number e.g. 296662600
The "Details" of the Missed/Received call shows the post-translation of "+61296662600"
Is there a away to show E164 format numbers/post-translated numbers for the Missed/Received calls to the hunt group members, while keeping the calling number presented to CUCM the under normal conditions the same??
The dialpeer created for the hunt pilot is dialpeer 2147483647. However, I could not find a way to modify it.
voice translation-rule 2
rule 1 /\(........\)/ /+61\1/ type national national
rule 2 /([2-9].......\)/ /+618\1/ type subscriber subscriber
rule 3 /\(.*\)/ /+\1/ type international international
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...
[toc:faq]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 discusse...