modify alphanumeric called party numbers with sip-profiles
I'm trying to modify the notify message for a sip-call alerted to a non-numerical destination in a UBE. Sounds freaky, but this is what sipgate.com is doing. The following example shows the INVITE with the TO: address, which I like to "clean" from the non-numeric characters. It would be enough to use just the leading digits to identify the called party. Then I could use a standard dial-peer to send the call into UCM. I went through the configuration examples for sip-profiles and read the other posts, but seems I'm overlooking something here.
I used lower case "x" in this example to mask my phone numbers. It is the sip:firstname.lastname@example.org:5060 which I have the problem with. A debug voip dialpeer shows that the incoming dial-peer is matched if I use "incoming 5276466", but the sip-profile is not triggered incoming only outgoing. An outgoing dial-peer cannot be triggered because even with a destination-pattern like "527T" is not recognized if there are illegal characters in the called party information. What am I overlooking here to get rid of these extra characters, or how can a UBE digest this kind of called party information??
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...