Call Deflection Session Initiation Protocol (SIP) Tracing
Dernière rubrique modifiée : 2009-07-08
The following Session Initiation Protocol (SIP) packets illustrate the pertinent data between an Office Communications Server 2007 R2 pool Front End Server and a Communicator Web Access (2007 R2 release) server for the call deflection scenario. The Communicator Web Access (2007 R2 release) user deflects the incoming call to voice mail.
All incoming calls to Communicator Web Access (2007 R2 release) sessions meet this scenario. An audio call is forked to all valid endpoints. Regardless of the source of the call, if the incoming call is directed at the Communicator Web Access (2007 R2 release) session, the deflection scenario is valid.
Call Deflection SIP Tracing Scenario
In this scenario, a Communicator Web Access (2007 R2 release) session exists. User1 is on Communicator Web Access (2007 R2 release) and User2 is on Office Communicator 2007 R2. User2 on Office Communicator 2007 R2 initiates an audio call to a phone number. An invitation from Office Communicator 2007 R2 is sent to the pool Front End Server.
TL_INFO(TF_PROTOffice Communicator 2007 R2 OL) [1]0A2C.0A9C::06/22/2009-17:58:48.922.0009935d (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
Instance-Id: 0018A2F9
Direction: incoming
Peer: 192.0.2.143:1331
Message-Type: request
Start-Line: INVITE sip:+12065550101@litwareinc.com;user=phone SIP/2.0
From: <sip:User2@litwareinc.com>;tag=ea1b3cab6b;epid=213be0ea4a
To: <sip:+12065550101@litwareinc.com;user=phone>
CSeq: 1 INVITE
Call-ID: a9c2eb61a37944979e6ba90adbf869ce
Via: SIP/2.0/TLS 192.0.2.143:1331
Max-Forwards: 70
Contact: <sip:User2@litwareinc.com;opaque=user:epid:Ub31lldjtFyGH5-ijiRSAgAA;gruu>
User-Agent: UCCAPI/3.5.6907.9 Office Communicator 2007 R2 /3.5.6907.34 (Microsoft Office Communicator 2007 R2)
Ms-Conversation-ID: AcnzYxWcvyhU/nzkQQK09Es13ht5ug==
Supported: timer
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-sender
Supported: ms-early-media
Supported: Replaces
Supported: 100rel
ms-keep-alive: UAC;hop-hop=yes
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REfront end R, NOTIFY, BENOTIFY, OPTIONS
P-Preferred-Identity: <sip:User2@litwareinc.com>, <tel:+14255550190>
Supported: ms-conf-invite
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="24C84179", targetname="sip/ocs.litwareinc.com", crand="2137c1d9", cnum="73", response="602306092a864886f71201020201011100ffffffff1e132d0f694dca1062759f1ba2b2538c"
Content-Type: multipart/alternative;boundary="----=_NextPart_000_0A41_01C9F328.696A8600"
Content-Length: 4786
Message-Body: ------=_NextPart_000_0A41_01C9F328.696A8600
Content-Type: application/sdp
$$end_record
The pool server determines that the phone number is a contact, and that the only registered endpoint is Communicator Web Access (2007 R2 release). The pool Front End Server sends the invitation to Communicator Web Access (2007 R2 release). In a situation where there is more than one registered endpoint, the Front End Server forks the call to all valid endpoints. In this case, Communicator Web Access (2007 R2 release) is the only endpoint.
TL_INFO(TF_PROTOffice Communicator 2007 R2 OL) [1]0A2C.0A9C::06/22/2009-17:58:48.953.0009939f (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
Instance-Id: 0018A302
Direction: outgoing
Peer: cwa.litwareinc.com:5061
Message-Type: request
Start-Line: INVITE sip:cwa.litwareinc.com:5061;transport=Tls;ms-opaque=303a446bf296e5e2 SIP/2.0
From: "User2"<sip:User2@litwareinc.com>;tag=ea1b3cab6b;epid=213be0ea4a
To: <sip:+12065550101@litwareinc.com;user=phone>;epid=454BF77D78
CSeq: 1 INVITE
Call-ID: a9c2eb61a37944979e6ba90adbf869ce
ms-user-data: ms-publiccloud=true;ms-federation=true
Record-Route: <sip:ocs.litwareinc.com:5061;transport=tls;opaque=state:T:F;lr>;tag=04E32C63BB6B7CF14891AD3423F629A0
Via: SIP/2.0/TLS 192.168.5.28:2507;branch=z9hG4bK41780D13.6D1B53BD01D5FDC8;branched=TRUE
Max-Forwards: 69
ms-application-via: backend_token;ms-server=ocs.litwareinc.com;ms-pool=ocs.litwareinc.com;ms-application=AB072FF0-C918-424c-AC12-7C100E91front end 3E
Content-Length: 4786
Via: SIP/2.0/TLS 192.0.2.143:1331;ms-received-port=1331;ms-received-cid=58200
P-Asserted-Identity: "User2"<sip:User2@litwareinc.com>,<tel:+14255550190>
Contact: <sip:User2@litwareinc.com;opaque=user:epid:Ub31lldjtFyGH5-ijiRSAgAA;gruu>
User-Agent: UCCAPI/3.5.6907.9 Office Communicator 2007 R2 /3.5.6907.34 (Microsoft Office Communicator 2007 R2)
Ms-Conversation-ID: AcnzYxWcvyhU/nzkQQK09Es13ht5ug==
Supported: timer
Supported: histinfo
Supported: ms-safe-transfer
Supported: ms-sender
Supported: ms-early-media
Supported: Replaces
Supported: 100rel
ms-keep-alive: UAC;hop-hop=yes
Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REfront end R, NOTIFY, BENOTIFY, OPTIONS
Supported: ms-conf-invite
Content-Type: multipart/alternative;boundary="----=_NextPart_000_0A41_01C9F328.696A8600"
History-Info: <sip:User1@litwareinc.com>;index=1
Message-Body: ------=_NextPart_000_0A41_01C9F328.696A8600
Content-Type: application/sdp
$$end_record
The Front End Server sends 101 Progress Report to the caller (that is, on Office Communicator 2007 R2).
TL_INFO(TF_PROTOffice Communicator 2007 R2 OL) [0]0A2C.0E7C::06/22/2009-17:58:48.953.000993fb (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
Instance-Id: 0018A306
Direction: outgoing;source="local"
Peer: 192.0.2.143:1331
Message-Type: response
Start-Line: SIP/2.0 101 Progress Report
From: "User2"<sip:User2@litwareinc.com>;tag=ea1b3cab6b;epid=213be0ea4a
To: <sip:+12065550101@litwareinc.com;user=phone>
CSeq: 1 INVITE
Call-ID: a9c2eb61a37944979e6ba90adbf869ce
Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF356BB0D9D7DF7A14FB5F5B03B945C688", srand="ED8D8237", snum="118", opaque="24C84179", qop="auth", targetname="sip/ocs.litwareinc.com", realm="SIP Communications Service"
Content-Length: 0
Via: SIP/2.0/TLS 192.0.2.143:1331;ms-received-port=1331;ms-received-cid=58200
ms-diagnostics: 13004;reason="Request was proxied to one or more registered endpoints";source="ocs.litwareinc.com";appName="InboundRouting"
Server: InboundRouting/3.5.0.0
Message-Body: –
$$end_record
The Front End Server receives 303 Proxy Should Redirect message from the Communicator Web Access (2007 R2 release) server. This is the result of the Communicator Web Access (2007 R2 release) user selecting the redirect to voice mail option in the system alert.
TL_INFO(TF_PROTOffice Communicator 2007 R2 OL) [1]0A2C.059C::06/22/2009-17:59:01.766.0009a336 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
Instance-Id: 0018A485
Direction: incoming
Peer: cwa.litwareinc.com:5061
Message-Type: response
Start-Line: SIP/2.0 303 Proxy Should Redirect
From: "User2"<sip:User2@litwareinc.com>;tag=ea1b3cab6b;epid=213be0ea4a
To: "User1"<sip:+12065550101@litwareinc.com;user=phone>;tag=ba51cb6d68;epid=454BF77D78
CSeq: 1 INVITE
Call-ID: a9c2eb61a37944979e6ba90adbf869ce
VIA: SIP/2.0/TLS 192.168.5.28:2507;branch=z9hG4bK41780D13.6D1B53BD01D5FDC8;branched=TRUE,SIP/2.0/TLS 192.0.2.143:1331;ms-received-port=1331;ms-received-cid=58200
CONTACT: <sip:User1@litwareinc.com;opaque=app:voicemail>
CONTENT-LENGTH: 0
SERVER: RTCC/3.5.0.0 CWA/3.5.0.0
Message-Body: –
$$end_record
The Front End Server sends ACK for the 303 message to Communicator Web Access (2007 R2 release) to notify the Communicator Web Access (2007 R2 release) user that the call was actually redirected to voice mail by the Front End Server.
TL_INFO(TF_PROTOffice Communicator 2007 R2 OL) [1]0A2C.059C::06/22/2009-17:59:01.766.0009a34d (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
Instance-Id: 0018A486
Direction: outgoing;source="local"
Peer: cwa.litwareinc.com:5061
Message-Type: request
Start-Line: ACK sip:cwa.litwareinc.com:5061;transport=Tls;ms-opaque=303a446bf296e5e2 SIP/2.0
From: "User2"<sip:User2@litwareinc.com>;tag=ea1b3cab6b;epid=213be0ea4a
To: "User1"<sip:+12065550101@litwareinc.com;user=phone>;tag=ba51cb6d68;epid=454BF77D78
CSeq: 1 ACK
Call-ID: a9c2eb61a37944979e6ba90adbf869ce
Via: SIP/2.0/TLS 192.168.5.28:2507;branch=z9hG4bK41780D13.6D1B53BD01D5FDC8;branched=FALSE
Max-Forwards: 70
Content-Length: 0
Message-Body: –
$$end_record