[SIPForum-discussion] P-Asserted-Identity and From Header

[Tomasz Zieleniewski]

Hi,

>From the trace, it looks like the AS is working in the Routing B2BUA mode.
This means that P-Asserted-Identity header is not changed but other headers
like From can change according to AS specific functionality. In the most
general case don't change it.
For more details check TS 24.229 section 5.7 Procedures at the Application
Server.

Kind regards,
- Tomasz Zieleniewski

ICT Backyard - http://ictbackyard.com
---------------------------------------------------------------------------------
"Tomorrow is today - nevertheless tomorrow" - S.Mrożek

2011/12/20 rawat he <himanshu.rawat at gmail.com>

> Hello,
>
> Below is the problem description :
>
> INCOMING INVITE to Application server has got P-Asserted-Identity header,
> What should be the value of FROM header in OUTGOING INVITE from the
> application server??
>
> Scenario :
>
> Incoming invite :
>
> INVITE sip:+661970000001 at ims.pea.co.th SIP/2.0^M
> Via: SIP/2.0/UDP 10.41.1.70:5090
> ;branch=z9hG4bK_IMSCA0720430.000_bdfc475e68282708e18c4eb8d1d05ba1;lskpmc=S27^M
> Via: SIP/2.0/UDP hq1rs01sip1.ims.pea.co.th:5060
> ;branch=z9hG4bKNSNSIP-460b290a-490b290a-2-0f7ec1f92a04bcbe93d700955d833400;received=10.41.11.19^M
> Max-Forwards: 61^M
> Route: <sip:10.41.13.88;lr;mode=terminating>^M
> Route: <sip:isc at scscf1-mw.ims.pea.co.th:5090
> ;lr;lskpmc=S27;bcos=1cb8d4844ddf7d70fb48c28d8001bf44>^M
> Record-Route: <sip:isc at scscf1-mw.ims.pea.co.th:5090
> ;lr;interface=isc;lskpmc=S27;routing_id=1cb8d4844ddf7d70fb48c28d8001bf44>^M
> To: <sip:+661970000001 at ims.pea.co.th:5090>^M
> From: <sip:70000002 at ims.pea.co.th
> ;user=phone>;tag=snl_0008345853_NSN_CLIENT^M
> Call-ID: NSNSIP-460b290a-490b290a-2-21-1321948234-921378-1322869612^M
> CSeq: 1235 INVITE^M
> Content-Length: 368^M
> Contact: <sip:70000002 at hq1rs01sip1.ims.pea.co.th;transport=udp>^M
> Supported: 100rel^M
> Supported: timer^M
> Accept-Language: en;q=0.0^M
> Allow: REGISTER,INVITE,ACK,BYE,CANCEL,NOTIFY,REFER,INFO,UPDATE,PRACK^M
> P-Asserted-Identity: <sip:+661970000002 at ims.pea.co.th;user=phone>^M
>
> Our application server Outgoing invite :
>
> INVITE sip:+661970000001 at ims.pea.co.th:5090;transport=udp;user=phone
> SIP/2.0^M
> Via: SIP/2.0/UDP 10.41.13.91:5060^M
> Route: <sip:isc at scscf1-mw.ims.pea.co.th:5090
> ;lr;lskpmc=S27;bcos=1cb8d4844ddf7d70fb48c28d8001bf44>^M
> To: <sip:+661970000001 at ims.pea.co.th:5090;transport=udp;user=phone>^M
> From: <sip:+661970000002 at 10.41.13.91
> ;user=phone>;tag=738fe46f-8cd3-4623-a542-467e957191cf^M
> Call-ID: 10.41.13.911261051318^M
> CSeq: 1 INVITE^M
> Content-Length: 368^M
> Content-Type: application/sdp^M
> Contact: <sip:10.41.13.91:5060;transport=udp>^M
> P-Charging-Vector: icid-value=692873354d69b59f922e51b210ba262e^M
> P-Asserted-Identity: <sip:+661970000002 at ims.pea.co.th;user=phone>^M
>
> We have replaced the FROM number with P-Asserted-Identity number.
>
> Is this correct behavior ?? If not, then what should be the idle
> behavior??
>
> Please tell me which RFC can give more details on this?? I have looked in
> RFC 3325 but not much information given for above scenario.
>
> Thanks,
> Rawat
>
>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20111221/b8e3e831/attachment-0002.html>