There is a serious problem with Caller ID spoofing that is being used for illegal purposes, including swatting (http://en.wikipedia.org/wiki/Swatting). A legislation has been introduced (Truth in Caller ID Act of 2009) that makes carriers liable for transporting Caller ID that is known false. By sending arbitrary 10 digit numbers in the From: field, you are basically spoofing Caller ID. This is the likely reason why they are stripping it out. As mentioned, you could try to use the Via header but any SBC or B2BUA in the call path could strip it out (under the guise of topology hiding). Maybe a parameter in the Request-URI has more chance of making it through...
Dan ____________________________________________________ Dan Mongrain, eng. Senior Systems Engineer, Public Safety FREQUENTIS USA Inc. 9017 Red Branch Road, Suite 102 Columbia Maryland 21045 Phone +1-301-657-8001 Mobile +1-819-744-0491 Fax +1-301-657-8002 Web www.frequentis.com/usa E-Mail [email protected] Incorporated in the State of Maryland EIN: 52-2178926 CAGE Code: 1XKR9 ____________________________________________________ Confidentiality Notice: This email message, including any attachments, is for the sole use of the intended recipient(s) and contains confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and associated attachments. -----Original Message----- From: Adelia Chetreanu [mailto:[email protected]] Sent: January-29-14 7:30 PM To: [email protected] Subject: Re: [Sip-implementors] Sending proprietary information in SIP INVITE Seems like my problem is with the FROM header. 518-09x-yyyy is not a valid NPA-NXX. Why would carries replace it with "Anonymous" if not valid? What kind of feature is this? Serious question, not sarcastic. Thx. A.C. From: Carlos Ruiz Díaz [mailto:[email protected]] Sent: Wednesday, January 29, 2014 2:09 PM To: Adelia Chetreanu Cc: [email protected] Subject: Re: [Sip-implementors] Sending proprietary information in SIP INVITE Add a parameter to your Via header? Via: SIP/2.0/UDP 10.10.10.2:5060;received=10.10.10.2;branch=z9hG4bK-d87543-603a7a3e7269fb4d-1--d87543-;rport=5060;xid=0123456789 On Wed, Jan 29, 2014 at 7:05 PM, Adelia Chetreanu <[email protected]<mailto:[email protected]>> wrote: Thank you, Paul, I have 2 tickets open - one with our carrier and one with the destination carrier. Our carrier confirmed that they don't change anything. Waiting for a reply from the destination carrier. The extra "P-Asserted-Identity" header is inserted in the network and I assume the NE inserting it is the culprit. >From P-Asserted-Identity: ><sip:[email protected]:5060<http://sip:[email protected]:5060>> > I determined that : - the inserted number owned by MCI (not our carrier, not the destination carrier) - the inserted IP is owned by the destination carrier. I'm with you and it's frustrating. Unfortunately I cannot count on the kindness of carriers, there must be something I can do to guarantee my unique ID delivery. A.C. -----Original Message----- From: Paul Kyzivat [mailto:[email protected]<mailto:[email protected]>] Sent: Wednesday, January 29, 2014 1:57 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Sip-implementors] Sending proprietary information in SIP INVITE Adelia, The problem is that carriers and other intermediaries have decided that they are free to change anything they want in sip signaling, regardless of SIP spec rules that they not do so. So you will have to take it up with them. It appears to me that the general attitude is: we will allow what we must to make the specific features we care about work - breaking any usage we don't explicitly embrace is a feature rather than a bug. Thanks, Paul On 1/29/14 4:48 PM, Adelia Chetreanu wrote: > I need to send a 10 digit unique ID over the network. > I've been doing it for years by replacing the INVITE FROM header with the 10 > digit value. > Looks like a phone number. > > Lately, I'm facing an on/off problem, the ANI gets replaced with Anonymous > every 70-80 calls or so. Randomly, no pattern. > I believe it to be related to a particular carrier we traverse and I have no > control over it. > It breaks one of our major features. > > This is an example: > > Sending: > INVITE > sip:[email protected]:5060<http://sip:[email protected]:5060 > > SIP/2.0 > Via: SIP/2.0/UDP > 10.10.10.2:5060;received=10.10.10.2;branch=z9hG4bK-d87543-603a7a3e7269 > fb4d-1--d87543-;rport=5060 > Max-Forwards: 69 > Contact: <sip:[email protected]:5060;transport=udp> > To: <sip:[email protected]:5060;transport=udp> > From: > <sip:[email protected]:5060;transport=udp;isup-oli=00>;tag=2b5d315 > 7 > Call-ID: MzQ3NzFjNGQ1NjY1MDBmNjMxMDAyOTA0NWVhNjVmNzc. > CSeq: 1 INVITE > Content-Type: application/sdp > Content-Length: 186 > > Receiving: > > > > > Request URI: > sip:[email protected]:5060<http://sip:[email protected]: > 5060> > From: "Anonymous" > <sip:[email protected];isup-oli=0>;tag=gK0a240fff > To: > <sip:[email protected]:5060<http://sip:[email protected] > 52:5060>> > Call-ID: > [email protected]<mailto:[email protected] > ><mailto:[email protected]<mailto:[email protected] > 3.234.114> > > > CSeq: 20798 INVITE > Contact: "Anonymous" > <sip:[email protected]:5060<http://sip:[email protected]:506 > 0>> > P-Asserted-Identity: > <sip:[email protected]:5060<http://sip:[email protected] > 14:5060>> > > > We extract 4153436545 instead of 5180943774 on the called party side, and our > feature bombs. > > While I follow up with our carrier, what other options do I have? > What could I use (header or parameter) to send my private info transparently > through the network? > Must be in INVITE. > > I have found post "Private Header" from 2009, that suggests: > - private header, add your own > - MIME data > - userinfo parameter in Request URI > > Each one has its challenges for my app - do I have other options? > Thank you! > A.C. > _______________________________________________ > Sip-implementors mailing list > [email protected]<mailto:[email protected] > s.columbia.edu> > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected]<mailto:[email protected]> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected]<mailto:[email protected]> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors -- Carlos http://caruizdiaz.com +595981146623 _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
