Avaya Support Forums  

Go Back   Avaya Support Forums > Avaya Aura & Unified Communications

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 09-25-2014, 12:40 AM
kkanaganti kkanaganti is offline
Aspiring Member
.
 
Join Date: Sep 2014
Posts: 1
kkanaganti has 10 reputation points
Default We would like to understand when and why CM sent 687 response to EP

Below is the sample sip trace. content highlighted in RED color we would like to understand.

@2014-06-26 13:02:39,427||FINEST|Tele|8513|FileName=sip/UAInterface.cpp,LineNumber=476|cUAInterface::SendT oNetwork: To 138.83.199.57:5060[71:0] <^INVITE sip:69007678035@138.83.200.29 SIP/2.0^M <- EP initiated outbound call by sending INVITE
From: <sip:5209185500@verizon.com;user=phone>;tag=f8bc5d 57c1fbe31a7dc00538ad6c4^M
To: sip:69007678035@138.83.200.29^M
Call-ID: 6be5d57c1fbe31a8dc00538ad6c4^M
CSeq: 1 INVITE^M
Max-Forwards: 70^M
Via: SIP/2.0/TCP 138.83.196.214;branch=z9hG4bK7ed75d57c1fbe31a9dc00 538ad6c4^M
User-Agent: Avaya-VoicePortal/6.0.2.0.0528^M
Supported: 100rel, timer, replaces, join, histinfo^M
Allow: INVITE, CANCEL, BYE, ACK, PRACK, SUBSCRIBE, NOTIFY, REFER, OPTIONS, INFO, PUBLISH^M
Contact: <sip:138.83.196.214;transport=tcp>^M
Session-Expires: 1800;refresher=uac^M
Min-SE: 1800^M
Content-Type: application/sdp^M
Call-Info: <kvpairs:VPUCID~4CF2013A-1017EA60-0001-SC*DN~7670501_AVVD*BTN~5706608665*ACCN~>;purpose=v erizon-ivr-data^M
User-to-User: 04C82534434632303133412D31303137454136302D30303031 2D5343303030303030303030303030;encoding=hex^M
Content-Length: 73^M
^M
v=0^M
o=- 1 1 IN IP4 138.83.196.214^M
s=-^M
c=IN IP4 138.83.196.214^M
t=0 0^M

@2014-06-26 13:02:39,551||FINEST|Tele|8513|FileName=sip/SIPTCP.cpp,LineNumber=408|SIPTCP::ProcessRead: <SIP/2.0 180 Ringing^M <- got 180 ringing from CM
From: <sip:5209185500@verizon.com;user=phone>;tag=f8bc5d 57c1fbe31a7dc00538ad6c4^M
To: <sip:69007678035@138.83.200.29>;tag=80feb179c4fee3 13d0535fcf300^M
Call-ID: 6be5d57c1fbe31a8dc00538ad6c4^M
CSeq: 1 INVITE^M
Via: SIP/2.0/TCP 138.83.196.214;branch=z9hG4bK7ed75d57c1fbe31a9dc00 538ad6c4^M
Supported: 100rel, histinfo, join, replaces, sdp-anat, timer^M
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, SUBSCRIBE, NOTIFY, REFER, INFO, PRACK, PUBLISH, UPDATE^M
Contact: "ERP EVRC Con SIP 035" <sip:8008374966@138.83.116.144:5080;transport=tcp> ^M
History-Info: <sip:8008374966@verizon.com>;index=1^M
History-Info: "ERP EVRC Con SIP 035" <sip:8008374966@verizon.com>;index=1.1^M
P-Asserted-Identity: "ERP EVRC Con SIP 035" <sip:8008374966@verizon.com>^M
Record-Route: <sip:138.83.116.144:5080;transport=tcp;lr>^M
Record-Route: <sip:rw-78241384@138.83.199.57:5080;lr;transport=TCP>^M
Record-Route: <sip:138.83.199.11:15060;transport=tcp;lr;sap=-1614820648*1*016asm-callprocessing.sar180834954~1403802159426~-288196069~1>^M
Record-Route: <sip:rw-78241384@138.83.199.57;lr;transport=TCP>^M
Require: 100rel^M
RSeq: 1^M
Server: Avaya CM/R016x.03.0.124.0 AVAYA-SM-6.2.2.0.622007^M
Content-Type: application/sdp^M
Content-Length: 92^M
P-Location: SM;origlocname="SC-MPP";origsiglocname="SC-MPP";termlocname="Tampa ACD4";termsiglocname="Tampa ACD4"^M
^M
v=0^M
o=- 1403802159 2 IN IP4 138.83.116.144^M
s=-^M
c=IN IP4 255.255.255.255^M
b=AS:64^M
t=0 0^M

@2014-06-26 13:02:39,564||FINEST|Tele|8513|FileName=sip/UAInterface.cpp,LineNumber=476|cUAInterface::SendT oNetwork: To 138.83.199.57:5060[71:0] <^REFER sip:5209185500@138.83.200.29:5060;transport=tcp SIP/2.0^M <- EP sent REFER to original party to replace the INVITE call.
From: sip:69017678035@138.83.199.57;tag=5a5f6557c1fbe31a 3dc00538ad6c4^M
To: sip:5209185500@138.83.200.29;tag=2CBEC864-0^M
Call-ID: 82EB42E4-FC8A11E3-8FACA602-BB3DCA5C@138.83.200.29^M
CSeq: 1 REFER^M
Max-Forwards: 70^M
Route: <sip:78241384@138.83.199.57;transport=tcp;lr>^M
Route: <sip:138.83.199.11:15060;lr;sap=-1614820648*1*016asm-callprocessing.sar180834954~1403802158430~-288196155~1;transport=tcp>^M
Route: <sip:78241384@138.83.199.57;transport=tcp;lr>^M
Route: <sip:78241384@138.83.199.57;transport=tcp;lr>^M
Route: <sip:138.83.199.11:15060;lr;sap=-1614820648*1*016asm-callprocessing.sar180834954~1403802158346~-288196161~1;transport=tcp>^M
Route: <sip:78241384@138.83.199.57;transport=tcp;lr>^M
Via: SIP/2.0/TCP 138.83.196.214;branch=z9hG4bK30ca7257c1fbe31abdc00 538ad6c4^M
User-Agent: Avaya-VoicePortal/6.0.2.0.0528^M
Contact: <sip:7678035@138.83.196.214;transport=tcp>^M
Refer-To: <sip:69007678035@138.83.200.29?Expires=120&User-to-User=04C82534434632303133412D31303137454136302D303 030312D5343303030303030303030303030%3Bencoding%3Dh ex&Replaces=6be5d57c1fbe31a8dc00538ad6c4%3Bfrom-tag%3Df8bc5d57c1fbe31a7dc00538ad6c4%3Bto-tag%3D80feb179c4fee313d0535fcf300>^M
Content-Length: 0^M

@2014-06-26 13:02:39,582||FINEST|Tele|8513|FileName=sip/SIPTCP.cpp,LineNumber=408|SIPTCP::ProcessRead: <SIP/2.0 202 Accepted^M
Via: SIP/2.0/TCP 138.83.196.214;branch=z9hG4bK30ca7257c1fbe31abdc00 538ad6c4^M
From: <sip:69017678035@138.83.199.57>;tag=5a5f6557c1fbe3 1a3dc00538ad6c4^M
To: <sip:5209185500@138.83.200.29>;tag=2CBEC864-0^M
Date: Thu, 26 Jun 2014 17:02:39 GMT^M
Call-ID: 82EB42E4-FC8A11E3-8FACA602-BB3DCA5C@138.83.200.29^M
CSeq: 1 REFER^M
Content-Length: 0^M
Contact: <sip:5209185500@138.83.200.29:5060;transport=tcp>^ M
P-Asserted-Identity: <sip:5209185500@verizon.com>^M
Server: AVAYA-SM-6.2.2.0.622007^M
^M
>|kksscp52####

2014-06-26 13:02:39,694||FINEST|Tele|8513|FileName=sip/SIPTCP.cpp,LineNumber=408|SIPTCP::ProcessRead: <SIP/2.0 687 Transaction Terminated^M <- got 687 from CM
From: <sip:5209185500@verizon.com;user=phone>;tag=f8bc5d 57c1fbe31a7dc00538ad6c4^M
To: <sip:69007678035@138.83.200.29>;tag=80feb179c4fee3 13d0535fcf300^M
Call-ID: 6be5d57c1fbe31a8dc00538ad6c4^M
CSeq: 1 INVITE^M
Via: SIP/2.0/TCP 138.83.196.214;branch=z9hG4bK7ed75d57c1fbe31a9dc00 538ad6c4^M
Server: Avaya CM/R016x.03.0.124.0 AVAYA-SM-6.2.2.0.622007^M
Content-Length: 0^M
^M
>|kksscp52####

@2014-06-26 13:02:44,428||FINEST|Tele|8513|FileName=sip/SIPTCP.cpp,LineNumber=408|SIPTCP::ProcessRead: <NOTIFY sip:7678035@138.83.196.214:5060;transport=tcp SIP/2.0^M
Via: SIP/2.0/TCP 138.83.199.57;branch=z9hG4bK8A53C70BFFFFFFFF94A091 6B0-1027845696-AP;ft=6682078^M
Via: SIP/2.0/TCP 138.83.199.11:15070;branch=z9hG4bK8A53C70BFFFFFFFF 94A0916B0-1027845696^M
Via: SIP/2.0/TCP 138.83.199.57;branch=z9hG4bK8A53C70BFFFFFFFF94A091 6B0-1027845698-AP-AP;ft=5766^M
Via: SIP/2.0/TCP 138.83.199.57;branch=z9hG4bK8A53C70BFFFFFFFF94A091 6B0-1027845698-AP;ft=6682078^M
Via: SIP/2.0/TCP 138.83.199.11:15070;branch=z9hG4bK8A53C70BFFFFFFFF 94A0916B0-1027845698^M
Via: SIP/2.0/TCP 138.83.199.57;branch=z9hG4bK1516F63DA9-AP;ft=11468019^M
Via: SIP/2.0/TCP 138.83.200.29:5060;branch=z9hG4bK1516F63DA9^M
From: sip:5209185500@138.83.200.29;tag=2CBEC864-0^M
To: sip:69017678035@138.83.199.57;tag=5a5f6557c1fbe31a 3dc00538ad6c4^M
Call-ID: 82EB42E4-FC8A11E3-8FACA602-BB3DCA5C@138.83.200.29^M
CSeq: 104 NOTIFY^M
Date: Thu, 26 Jun 2014 17:02:44 GMT^M
User-Agent: Cisco-SIPGateway/IOS-12.x AVAYA-SM-6.2.2.0.622007^M
Event: refer^M
Subscription-State: terminated;reason=noresource^M
Contact: <sip:5209185500@138.83.200.29:5060;transport=tcp>^ M
Content-Type: message/sipfrag^M
Content-Length: 18^M
Max-Forwards: 64^M
^M
SIP/2.0 200 OK^M
^M

@2014-06-26 13:03:09,875||FINE|SessMgr|4797||CSession::Run() - Exiting Session 78845 - kksscp52-2014177170238-50279|kksscp52####
@2014-06-26 13:03:09,875||FINEST|SessMgr|4797||******** Leaving Session.cpp:5262:Run|kksscp52####
@2014-06-26 13:03:09,875||FINE|SessMgr|4797||CSessionMgr:est roySession - Destroying Session[slot -1] 78845 - kksscp52-2014177170238-50279|kksscp52####
@2014-06-26 13:03:09,875||FINER|SessMgr|4797||CSessionMgr:es troySession - Session 78845, kksscp52-2014177170238-50279 is being removed from SessionMgr control|kksscp52####
@2014-06-26 13:03:09,875||FINER|SessMgr|4797||CSessionMgr:es troySession - Current Active Sessions = 0, Current ASR ports = 0, Current TTS ports = 0|kksscp52####
@2014-06-26 13:03:09,876||FINE|SessMgr|4797||CSessionMgr:est roySession - Session Destroyed 78845 - kksscp52-2014177170238-50279|kksscp52####
@2014-06-26 13:03:09,876||FINE|SessMgr|4797||CSessionThread::R un - Terminated session [slot -1] object kksscp52-2014177170238-50279 has a remaining reference count 1, end points = 0, tel calls = 0|kksscp52####
Reply With Quote
  #2  
Old 09-25-2014, 02:57 AM
richa164 richa164 is offline
Guru
 
Join Date: Oct 2013
Posts: 131
richa164 has 23 reputation pointsricha164 has 23 reputation points
Default

Without knowing all your topology it is hard to say exactly but see the below link ,

http://tools.ietf.org/html/draft-ietf-sip-replaces-02
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:36 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.