<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Jay,<div><br></div><div>I agree with Alex in that my research on the issue showed that Caller-ID was most often taken from P-A-I followed by From, with some people still using the now-deprecated RPID. </div><div><br></div><div>For passing the billing identifier, some network operators, carriers and ITSPs are using another header, P-Charge-Info, which I've been in the process of documenting for several years:</div><div><br></div><div><a href="http://tools.ietf.org/html/draft-york-sipping-p-charge-info">http://tools.ietf.org/html/draft-york-sipping-p-charge-info</a></div><div><br></div><div>(and am hoping will move along further in the next few months). The operators (and my prior employer was one of them) are using P-Charge-Info to carry a billing identifier that is completely separate from the identifier used for Caller-ID. They do that only between themselves, i.e. the header is stripped before being sent on to others.</div><div><br></div><div>This is certainly not the only way to pass this kind of billing identifier, but it's one of the ones out there.</div><div><br></div><div>Regards,</div><div>Dan</div><div><br></div><div>P.S. I am NOT with Sonus Networks, even though the latest version of the document looks like I am. The next version will correct that.</div><div><br></div><div><br></div><div><div><div>On Jul 23, 2012, at 5:21 PM, Alex Balashov wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Almost all commercial softswitch and SBC equipment we've run into<br>prioritises CLID presentation thusly:<br><br>1. P-Asserted-Identity<br>2. Remote-Party-ID<br>3. From<br><br>However, this is not so ubiquitous that it can be counted on one hundred<br>percent. Some folks don't do it. Some only use RPID (even though it's<br>a long-expired draft supplanted by PAI). Some expect RPID or PAI to<br>play only a supplementary role, with their various screening and<br>presentation options, and thus deny calls where the CLID in the PAI or<br>RPID is inconsistent with the CLID in the From.<br><br>Most, however, look at PAI, then RPID, then From. I can't speak to<br>whether this is "correct" or is grounded in some sort of best-practical<br>recommendation somewhere. It's just what they do.<br><br>On 07/23/2012 05:08 PM, Jay Hennigan wrote:<br><br><blockquote type="cite">Question for the experts:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We have a scenario where a SIP user originates a call to the PSTN (not<br></blockquote><blockquote type="cite">9-1-1) with a SIP From: header containing one DID and<br></blockquote><blockquote type="cite">P-Asserted-Identity showing a different DID.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">We expect the carrier to use the P-Asserted-Identity for billing and<br></blockquote><blockquote type="cite">recordkeeping but send the SIP From: out as the CLID to be displayed to<br></blockquote><blockquote type="cite">the called party.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Typically this is done in a call center type scenario where an agent<br></blockquote><blockquote type="cite">wants the CLID to display the main number of the agent pool and not the<br></blockquote><blockquote type="cite">specific DID of the agent. Another scenario is a customer PRI-based PBX<br></blockquote><blockquote type="cite">that hairpins inbound calls back out to a traveling user and wants to<br></blockquote><blockquote type="cite">preserve the original caller's information.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">One of our terminating carriers uses the P-Asserted-Identity as the<br></blockquote><blockquote type="cite">displayed CLID and not the SIP From:. I feel that this is not correct.<br></blockquote><blockquote type="cite"> Opinions?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Numbers have been changed to protect the guilty...<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">TO: <<a href="sip:8055550123@www.xxx.yyy.zzz;user=phone">sip:8055550123@www.xxx.yyy.zzz;user=phone</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">FROM: "Fred<br></blockquote><blockquote type="cite">Flintstone"<<a href="sip:+18055550199@www.xxx.yyy.zzz;user=phone">sip:+18055550199@www.xxx.yyy.zzz;user=phone</a>>;tag=1689985881-1343063740200-<br></blockquote><blockquote type="cite">P-Asserted-Identity: "Fred<br></blockquote><blockquote type="cite">Flintstone"<<a href="sip:+18055550177@www.xxx.yyy.zzz;user=phone">sip:+18055550177@www.xxx.yyy.zzz;user=phone</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">TIME/DATE: Mon Jul 23 17:15:39 2012 (GMT)<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">RESULT: Called party (8055550123) is seeing 8055550177 as calling<br></blockquote><blockquote type="cite">party's caller ID instead of 8055550199<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br><br>-- <br>Alex Balashov - Principal<br>Evariste Systems LLC<br>235 E Ponce de Leon Ave<br>Suite 106<br>Decatur, GA 30030<br>Tel: +1-678-954-0670<br>Fax: +1-404-961-1892<br>Web: <a href="http://www.evaristesys.com/">http://www.evaristesys.com/</a>, <a href="http://www.alexbalashov.com/">http://www.alexbalashov.com/</a><br>_______________________________________________<br>VoiceOps mailing list<br><a href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a><br>https://puck.nether.net/mailman/listinfo/voiceops<br></div></blockquote></div><br><div apple-content-edited="true">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">-- <br>Dan York <a href="mailto:dyork@lodestar2.com">dyork@lodestar2.com</a></div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Phone: +1-802-735-1624 <a href="skype:danyork">skype:danyork</a><br><a href="http://www.danyork.com/">http://www.danyork.com/</a> <br><a href="http://twitter.com/danyork">http://twitter.com/danyork</a></div></div></div></span></div>
</div>
<br></div></body></html>