2010/9/13 Seshu Kumar <[email protected]>:
>
>
> Hi All,
>
>
>
>          When using Sipxecs (with Sipxbridge configured) for an external
> call scenario, we are getting few issues with PAI (P-Asserted-Identity) in
> the INVITE. The problem seems happening in sipXbridge.
>
>
>
>          The flow of the INVITE message can be seen as,
>
>
>
>          Our app --> SipxProxy à Sipxbridge à ITSP(sip trunk)
>
>
>
>          Now from the below message headers, we can see that PAI is
> propagated to sipxbridge with the value set in the app. But in the
> SipxBridge(in step3), it is stripped and set with the value configured on
> the GW page.
>
>
>
>          Could you please suggest us, how can we ensure that user specific
> PAI is transparently sent to the ITSP (which is required for billing
> purpose) – Thanks in advance.
>

That support does not exist. It can be easily added however.

Ranga

>
>
> Step 1: (our app -> SipxProxy)
>
>
>
> Call-ID: [email protected]
>
> CSeq: 1 INVITE
>
> From: "[email protected]"
> <sip:[email protected]>;tag=226112
>
> To: <sip:[email protected]>
>
> Max-Forwards: 70
>
> P-Asserted-Identity:
> <sip:[email protected];signature=4C8E3E52:b29599d95ac66b6ce2385a413c26b749>
>
> Contact: <sip:[email protected]:5560>
>
> X-Targetleg: 1
>
> Route: <sip:[email protected];lr>
>
> Content-Type: application/sdp
>
> Allow: INVITE, ACK, CANCEL, BYE, REFER, NOTIFY
>
> Expires: 180
>
> Via: SIP/2.0/UDP
> 10.48.62.111:5560;branch=z9hG4bK76b165877be1101d99ec59026390c4a2313939
>
> Content-Length: 176
>
>
>
> Step 2: (SipxProxy -> Sipxbridge)
>
>
>
> Route: <sip:10.48.62.111:5090;lr>
>
> Record-Route:
> <sip:10.48.62.111:5060;lr;sipXecs-CallDest=CUST;sipXecs-rs=%2Aauth%7E.%2Afrom%7EMjI2MTEy.700_fromalias%2Aa%7EPHNpcDowMTIyNTU4MDgxMEBlYzItNzktMTI1LTExNC0xNzQuZXUtd2VzdC0xLmNvbXB1dGUuYW1hem9uYXdzLmNvbT47dGFnPQ%60%60.700_fromalias%2Aao%7ENzM%60.700_fromalias%2Ac%7EIjgxMEBlYzItNzktMTI1LTExNC0xNzQuZXUtd2VzdC0xLmNvbXB1dGUuYW1hem9uYXdzLmNvbSIgPHNpcDo4MTBAZWMyLTc5LTEyNS0xMTQtMTc0LmV1LXdlc3QtMS5jb21wdXRlLmFtYXpvbmF3cy5jb20%27O3RhZz0%60.700_fromalias%2Aco%7EMTIy.900_ntap%2Aid%7EMzI3NjQtMg%60%60%2154e33a4343400ec9098fc93f72e6c5f3>
>
> Call-Id: [email protected]
>
> Cseq: 1 INVITE
>
> From:
> <sip:[email protected]>;tag=226112
>
> To: <sip:[email protected]>
>
> Max-Forwards: 18
>
> P-Asserted-Identity:
> <sip:[email protected];signature=4C8E3E52:b29599d95ac66b6ce2385a413c26b749>
>
> Contact: <sip:[email protected]:5560;x-sipX-nonat>
>
> X-Targetleg: 1
>
> Content-Type: application/sdp
>
> Allow: INVITE, ACK, CANCEL, BYE, REFER, NOTIFY
>
> Expires: 60
>
> Via: SIP/2.0/TCP 10.48.62.111;branch=z9hG4bK-XX-0027GVHuw3cjCcX2mXFZOgsw8g
>
> Via: SIP/2.0/UDP
> 10.48.62.111;branch=z9hG4bK-XX-0024i1wjOqrjAoVAmbSRFIxhUA~DUtTRp7HeHBZtmxZZVNHVA;id=32764-2
>
> Via: SIP/2.0/UDP
> 10.48.62.111:5560;branch=z9hG4bK76b165877be1101d99ec59026390c4a2313939
>
> Content-Length: 185
>
> Date: Mon, 13 Sep 2010 15:08:02 GMT
>
> X-Sipx-Handled: X10.48.62.111-79.125.114.174
>
>
>
>
>
> Step 3: (Sipxbridge à ITSP(Sip Trunk))
>
>
>
> Call-ID: [email protected]
>
> CSeq: 1 INVITE
>
> From: "sipxbridge" <sip:[email protected]>;tag=2102611743270162572
>
> To: <sip:[email protected];user=phone>
>
> Via: SIP/2.0/UDP
> 79.125.114.174:5080;branch=z9hG4bK7cf4f441478c244fc1656d0c76ba3577313938
>
> Max-Forwards: 70
>
> User-Agent: sipXecs/4.2.1 sipXecs/sipxbridge (Linux)
>
> P-Asserted-Identity: <sip:[email protected]>
>
> Contact: <sip:[email protected]:5080;transport=udp>
>
> Route: <sip:212.11.94.100:5060;transport=udp;lr>
>
> Session-Expires: 1800;refresher=uac
>
> References:
> [email protected];rel=chain;sipxecs-tag=request-invite-z9hg4bk-xx-0027gvhuw3cjccx2mxfzogsw8g
>
> Allow: INVITE,BYE,ACK,CANCEL,OPTIONS
>
> Supported: timer
>
> Content-Type: application/sdp
>
> Content-Length: 189
>
>
>
>
>
>
>
>
>
> Best Regards,
>
> Seshu Kumar.
>
>
>
> Seshu Kumar Velagapudi, Senior System Engineer
>
> OnRelay
>
> Elizabeth House │ 39 York Road, London SE1 7NQ, UK │ +44 (0) 207 902 8131 │
> [email protected] │ www.onrelay.com
>
> This electronic message transmission contains information from OnRelay,
> Ltd., that may be confidential or privileged. The information is intended
> solely for the recipient and use by any other party is not authorised. If
> you are not the intended recipient, be aware that any disclosure, copying,
> distribution or use of the contents of this information or any attachment,
> is prohibited. If you have received this electronic transmission in error,
> please notify us immediately by electronic mail ([email protected]) and
> delete this message, along with any attachments, from your computer.
> Registered in England No 04006093 ¦ Registered Office 1st Floor, 236 Gray's
> Inn Road, London WC1X 8HB.
>
>



-- 
M. Ranganathan
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to