Workaround: ARI get second invite SIP headers

Hello,

I understand that ARI able to get SIP header from only the first INVITE. Do you have any idea to get SIP header from the second INVITE?

Thanks,
Warawich

There isn’t a way in Asterisk to do so, and what do you mean by “second INVITE”? A re-INVITE?

Thanks for reply, sorry I’m not sure. I mean I would like to get an P-Asserted-Identity from SIP headers in the CSeq: 3 INVITE.

Thanks,

<--- SIP read from TCP:203.130.145.198:15300 --->
ACK sip:3825@35.213.180.255:5123;transport=tcp SIP/2.0
From: "AAEP12" <sip:71665@10.101.1.31:15300>;tag=0fc49a66edeb164b860622cfe00
To: <sip:3825@35.213.180.255:5123>;tag=as50ddc301
CSeq: 2 ACK
Call-ID: aa97d6658bfa2137d85e714a741db625
Record-Route: <sip:10.101.1.31:5123;ipcs-line=130045;lr;transport=tcp>
User-Agent: Avaya CM/R016x.00.1.510.1 AVAYA-SM-6.3.22.0.632205
Max-Forwards: 66
Via: SIP/2.0/TCP 10.101.1.31:5123;branch=z9hG4bK-s1632-000935605918-1--s1632-
P-Location: SM;origlocname="SCG-HQ";origsiglocname="SCG-HQ";origmedialocname="SCG-HQ";termlocname="SCG-HQ";termsiglocname="SCG-HQ";termmedialocname="SCG-HQ";smaccounting="true"
Av-Global-Session-ID: b43e6630-eebd-11eb-871f-000c299e3f90
Content-Length: 0

<------------->
[Jul 27 16:33:31] VERBOSE[7304] chan_sip.c: --- (12 headers 0 lines) ---
[Jul 27 16:33:31] VERBOSE[7304] chan_sip.c: 
<--- SIP read from TCP:203.130.145.198:15300 --->
INVITE sip:3825@35.213.180.255:5123;transport=tcp SIP/2.0
From: "AAEP12" <sip:71665@10.101.1.31:15300>;tag=0fc49a66edeb164b860622cfe00
To: <sip:3825@35.213.180.255:5123>;tag=as50ddc301
CSeq: 3 INVITE
Call-ID: aa97d6658bfa2137d85e714a741db625
Contact: <sip:0865158281@10.101.1.31:5123;transport=tcp;gsid=b43e6630-eebd-11eb-871f-000c299e3f90>
Record-Route: <sip:10.101.1.31:5123;ipcs-line=130045;lr;transport=tcp>
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY, REFER, INFO, PRACK, PUBLISH
Supported: 100rel, histinfo, join, replaces, timer
User-Agent: Avaya CM/R016x.00.1.510.1 AVAYA-SM-6.3.22.0.632205
Max-Forwards: 66
Via: SIP/2.0/TCP 10.101.1.31:5123;branch=z9hG4bK-s1632-001639202890-1--s1632-
Accept-Language: en
P-Asserted-Identity: <sip:0865158281@10.101.1.31:15300>
Session-Expires: 1200;refresher=uac
Min-SE: 1200
P-Location: SM;origlocname="SCG-HQ";origsiglocname="SCG-HQ";origmedialocname="SCG-HQ";termlocname="SCG-HQ";termsiglocname="SCG-HQ";termmedialocname="SCG-HQ";smaccounting="true"
Av-Global-Session-ID: b43e6630-eebd-11eb-871f-000c299e3f90
Content-Length: 0

Set trustrpid=yes for chan_sip or trust_id_inbound=yes for chan_psjip, then read Manipulating Party ID Information - Asterisk Project - Asterisk Project Wiki

Do not try to re-invent the wheel.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.