4.2.1.1 Step 3: INVITE Message Is Received by the UAC

  • Article

 A UAS proxy replaces the Request URI header with the phone-context parameter that is received from the gateway. However, the To header is not replaced and holds the SIP URI with the phone-context that was inserted by the gateway.

INVITE sip:10.56.66.167:1501;transport=tls;ms-opaque=56d3073f52;ms-received-cid=8000 SIP/2.0
Record-Route: <sip:server1.example.com:5061;transport=tls;ms-role-rs-from;lr;ms-identity=C8ybl0ausk5JrrJOeabpGevnl7YoohctFBsEB3Oy33pmWwR9xH_oTAlgAA;ms-route-sig=ea0m1vIX8ijETotqsV9nVQESDR_2qwR9xH_oTAlgAA>;tag=D78DE2B2FF72EB24FDA98B88DCC879B2
Via: SIP/2.0/TLS 10.56.64.202:5061;branch=z9hG4bKD262F853.B047DC47;branched=TRUE;ms-internal-info="daqI8a1fcNQkUHDJyMoUxdQudrDTCwR9xH7_OEdQAA"
Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF1125B31E1322F6E6A4E65212D8DEDCA4", srand="A8085D66", snum="58", opaque="C216B7E9", qop="auth", targetname="sip/server1.example.com", realm="SIP Communications Service"
Max-Forwards: 69
Content-Length: 1606
Via: SIP/2.0/TLS 10.56.64.207:2861;branch=z9hG4bK27555a4e;ms-received-port=2861;ms-received-cid=8900
From: <sip:+15555550103@server1.example.com;user=phone>;epid=571F84BB45;tag=ed77bad0f0
To: <sip:7275036;phone-context=normal-loc@server1.example.com;user=phone>;epid=782abb8f70
CSeq: 6 INVITE
Call-ID: 46bac89b-3f5f-4f1f-bb0b-e791706e2401
Contact: <sipserver1.example.com@server1.example.com;gruu;opaque=srvr:MediationServer:ANaNrdcy8EmB-dKmljqX-wAA;grid=9b192c6b829d4373adb88ea9ef4dff03>;isGateway
Supported: replaces
Supported: gruu-10
User-Agent: RTCC/3.0.0.0 MediationServer
Content-Type: application/sdp; charset=utf-8