<div dir="ltr">Hi,<div><br></div><div>We are running CUCM 8.6.2 and CUBE 15.2(2)T1. I collect SIP trace from an incoming call made between from ITSP to one of our number.</div><div><br></div><div>There are two things from SIP trace collected from CUBE that I don't quite understand. If anyone has seen similar things and able to explain what happens, that would be great.</div>
<div><br></div><div>[1] After the call is put on hold and a Resume button is pressed. CUCM seems to send an INVITE to CUBE, but addressing it to our local number. (ext 1111 registered to our CUCM at 2.2.2.2, but the CUCM send out INVITE to 1111@CUBE_IP)</div>
<div><br></div><div>The trace of the anomaly one. <br></div><div><br></div><div><div>Feb 3 13:11:31.062: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:</div><div>Received: </div><div><b><u>INVITE sip:1111@203.13.194.13:5060;transport=tcp SIP/2.0</u></b></div>
<div>Via: SIP/2.0/TCP 2.2.2.2:5060;branch=z9hG4bK224ce234d6995</div><div>From: <<a href="mailto:sip%3A1111@2.2.2.2">sip:1111@2.2.2.2</a>>;tag=1518352~5715354d-5e10-479a-bb99-fd13399246ab-42474051</div><div>To: "Foo Foo" <<a href="mailto:sip%3A00222222222@203.13.194.13">sip:00222222222@203.13.194.13</a>>;tag=BCC14C68-1155</div>
</div><div><br></div><div>All other Re-INVITEs in the trace contain the correct target URI.<br></div><div><br></div><div><div>Feb 3 13:11:28.086: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:</div><div>Received: </div><div>
<b><u>INVITE sip:00222222222@203.13.194.13:5060;transport=tcp SIP/2.0</u></b></div><div>Via: SIP/2.0/TCP 2.2.2.2:5060;branch=z9hG4bK224ca3fe1b3aa</div><div>From: <<a href="mailto:sip%3A1111@2.2.2.2">sip:1111@2.2.2.2</a>>;tag=1518352~5715354d-5e10-479a-bb99-fd13399246ab-42474051</div>
<div>To: "Foo Foo" <<a href="mailto:sip%3A00222222222@203.13.194.13">sip:00222222222@203.13.194.13</a>>;tag=BCC14C68-1155</div></div><div><br></div><div>Is this a known bug or by design?<br></div><div><br>
</div><div><br></div><div>[2] For Re-INVITE, CUBE seems to filter both "Remote-Party-ID" & "P-Asserted-Identify" before sending it out to our ITSP. Is this expected? CUBE seems to be very young and many aspect of its operation is fairly undocumented so I don't know whether this is a bug or by-design.</div>
<div><br></div><div><br></div><div>Here is the relevant configuration on CUBE</div><div><br></div><div>#show run | b voice service voip<br></div><div><div>voice service voip</div><div> ip address trusted list</div><div>....</div>
<div>...</div><div> address-hiding<br></div><div> mode border-element</div><div> allow-connections sip to sip</div><div> fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none</div><div> sip</div><div> bind control source-interface GigabitEthernet0/0</div>
<div> bind media source-interface GigabitEthernet0/0</div><div> session transport tcp</div><div> rel1xx disable</div><div> header-passing</div><div> error-passthru</div><div> midcall-signaling passthru</div><div> pass-thru content sdp</div>
</div><div>...</div><div>...</div><div><br></div><div>A full call trace in question is attached. </div><div><br></div><div>Regards,</div><div>--Somphol.</div><div><br></div><div><div><br></div></div></div>