JohnsonOps
Technical User
When i get an incoming call on a SIP trunk the outgoing twinning call isn't passing the CID corectly. I get a garbled CID, now it works ok on an incoming analog call.
When looking at monitor traces I think the problem lies in the fact that the IP address is appended to the phone number so when it passes the CID with that full string it just uses garbage for the CID on the cell phone.
xxx.xxx.xxx.xxx and yyy.yyy.yyy.yyy added for incoming ip and outgoing ip respectively to protect the innocent
Anyone know of how to massage the incoming CID on SIP so that it will be formated like a regular 10 digit phone number?
When looking at monitor traces I think the problem lies in the fact that the IP address is appended to the phone number so when it passes the CID with that full string it just uses garbage for the CID on the cell phone.
Code:
64704872mS SIP Rx: UDP yyy.yyy.yyy.yyy:5060 -> xxx.xxx.xxx.xxx:5060
BYE sip:PatrickJohnson@xxx.xxx.xxx.xxx:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP yyy.yyy.yyy.yyy:5060;branch=z9hG4bK25768079;rport
From: <sip:18479912233@yyy.yyy.yyy.yyy>;tag=as01754069
To: PatrickJohnson <sip:PatrickJohnson@xxx.xxx.xxx.xxx>;tag=9219c8493193287b
Call-ID: 0f664eae1ebd105362fdef007a1527b8@yyy.yyy.yyy.yyy
CSeq: 103 BYE
User-Agent: LES.NET.VoIP
Max-Forwards: 70
Content-Length: 0
64704886mS CMLineRx: v=0
CMReleaseComp
Line: type=IPLine 10 Call: lid=0 id=1151 in=2
IE CMIERespondingPartyName (228) Palatine,IL
IE CMIERespondingPartyNumber (230)(P:0 S:100 T:0 N:100 R:4) number=18479912233@yyy.yyy.yyy.yyy
IE CMIEDeviceDetail (231) LOCALE=enu HW=8 VER=4 class=CMDeviceSIPTrunk type=0 number=10 channel=0 gain=32
64704886mS CMCallEvt: 0.1151.2 38 SIPTrunk Endpoint: StateChange: END=A CMCSConnected->CMCSCompleted
Anyone know of how to massage the incoming CID on SIP so that it will be formated like a regular 10 digit phone number?