the P-Asserted-Identity must be checked: to validate that the SM interprets the origin of the call and the data received in a normal manner, the input from the SBC to the SM is manipulated in the SBCe and the data sent by the carrier in the P-Asserted-Identity is eliminated:
INVITE sip:xxxxxxxxxx@xxxxxxxxxxx;user=phone SIP/2.0
Via: SIP/2.0/TLS xx.xxx.xxx.xxx.ORT;branch=z9hG4bKcrn4872030ssh0ag6vb0.1 │
Call-ID: of2nmbo2ofbwpnlfu3lnwul4oggqq4gl@B.5.109.ims.enlacetpe.com │
From: "xxxxxxxxxxx"<sip:xxxxxxxxxx2@xxx.xxx.xxx.xxORT;noa=international;srvattri=national;cpc=ordinary>;tag=sm5ex6xc │
To: <sip:5xxxxxxxx@xxx.xxx.xxx.xx.POrt:xxxxx> │
CSeq: 1 INVITE │
Accept-Language: en │
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,PRACK,PUBLISH,UPDATE │
P-Charging-Vector: icid-value=pu0q5046ghb23ss6e9c43so5h9ee48t9eqn8l51cuc801;orig-ioi=ims.enlacetpe.com;term-ioi=ims.enlacetpe.com │
│Max-Forwards: 49 │
Supported: timer,histinfo,join,replaces,100rel │
User-Agent: Avaya J139 IP Phone 4.1.5.0.6 c81feaf2ab71 AVAYA-SM-8.1.3.8.813807 Avaya CM/R018x.01.0.890.0 AVAYA-SM-8.1.3.8.813807 │
│Session-Expires: 1800 │
Min-SE: 600 │
P-Asserted-Identity: "xxxxxxxxxxx"<sip:xxxxxxxxxx@ims.enlacetpe.com> │
P-Asserted-Identity: "xxxxxxxxxxx"<tel:xxxxxxxxx>
On the SBC
Signaling Manipulation
within session "INVITE"
{
act on request where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
remove(%HEADERS["P-Asserted-Identity"][1]);
remove(%HEADERS["P-Asserted-Identity"][1]);
}
}
INVITE sip:xxxxxxxxxx@xxxxxxxxxxx;user=phone SIP/2.0
Via: SIP/2.0/TLS xx.xxx.xxx.xxx.ORT;branch=z9hG4bKcrn4872030ssh0ag6vb0.1 │
Call-ID: of2nmbo2ofbwpnlfu3lnwul4oggqq4gl@B.5.109.ims.enlacetpe.com │
From: "xxxxxxxxxxx"<sip:xxxxxxxxxx2@xxx.xxx.xxx.xxORT;noa=international;srvattri=national;cpc=ordinary>;tag=sm5ex6xc │
To: <sip:5xxxxxxxx@xxx.xxx.xxx.xx.POrt:xxxxx> │
CSeq: 1 INVITE │
Accept-Language: en │
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,INFO,PRACK,PUBLISH,UPDATE │
P-Charging-Vector: icid-value=pu0q5046ghb23ss6e9c43so5h9ee48t9eqn8l51cuc801;orig-ioi=ims.enlacetpe.com;term-ioi=ims.enlacetpe.com │
│Max-Forwards: 49 │
Supported: timer,histinfo,join,replaces,100rel │
User-Agent: Avaya J139 IP Phone 4.1.5.0.6 c81feaf2ab71 AVAYA-SM-8.1.3.8.813807 Avaya CM/R018x.01.0.890.0 AVAYA-SM-8.1.3.8.813807 │
│Session-Expires: 1800 │
Min-SE: 600 │
P-Asserted-Identity: "xxxxxxxxxxx"<sip:xxxxxxxxxx@ims.enlacetpe.com> │
P-Asserted-Identity: "xxxxxxxxxxx"<tel:xxxxxxxxx>
On the SBC
Signaling Manipulation
within session "INVITE"
{
act on request where %DIRECTION="OUTBOUND" and %ENTRY_POINT="POST_ROUTING"
{
remove(%HEADERS["P-Asserted-Identity"][1]);
remove(%HEADERS["P-Asserted-Identity"][1]);
}
}