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:[email protected]: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??
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 18.104.22.168:5060;branch=z9hG4bK61c1.cf79bce7.0
Via: SIP/2.0/UDP 172.30.20.1;branch=z9hG4bK61c1.cf79bce7.0
Via: SIP/2.0/UDP 22.214.171.124:5060;received=126.96.36.199;branch=z9hG4bK4e189a7e
Via: SIP/2.0/UDP 188.8.131.52:5060;branch=z9hG4bK4e189a7e;rport=5060
From: "415xxxxxx" <sip:[email protected]>;tag=as5a0dad6a
To: <sip:[email protected]>
Contact: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 103 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
X-ORIGSIPCALLID: [email protected]