« previous next »
Pages: [1]   Go Down

Author Topic: Strange issue with intermittent disconnects on interflowed calls  (Read 1880 times)

Offline jherrmann

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
Strange issue with intermittent disconnects on interflowed calls
« on: August 06, 2017, 12:18:08 AM »
All, I'm not by any means a VOIP person, but I've recently taken over as the IT manager for a national healthcare business that previously outsourced all IT. We have a 3300 controller and use the full suite of contact center solutions as well as MBGs.

We recently started experiencing a very strange issue and our Mitel Partner along with Mitel Support Engineers have no clue what's going on and just say that it's not an issue on the Mitel system.

Our contact center accepts calls on around 500 different DIDs that route to different queues and each have different interflow settings, however in common they all sit in queue for 40 seconds and then interflow to our contracted overflow contact center who has their own DID for each queue.

Over the past few days, most calls that overflow connect and are serviced without issue, however some calls will connect to the IVR at our overflow facility and sit in queue there, but once it goes to connect them to an agent the call drops.

On the overflow centers side (who uses SIP) it shows as the call disconnected by the calling party (it even shows up as an abandoned call on their reporting). On our side (We are in PRIs) the call shows as the Disconnect request came from them with a "normal call clearing" code. We've tried getting the engineering teams for both sides on a call together but they just keep telling each other that it's not their side it's the other side.

We've checked with other customers at the overflow center and none of them are reporting this issue, which makes it seem, that there is either an issue on the Mitel side or something in the interaction of the two systems, but neither of them have any ideas and troubleshooting has come to a total standstill.

We have a million dollar ad campaign starting Monday and I'm at my wits end... Please if any of you have any ideas, please please get in touch or comment here and suggest, point, ask... I'll take it all. We have some examples that I can provide as needed of the PRI trace log from Mitel, SIP call logs from our overflow center's pbx, SS7 switch logs from our PRI provider, and some data from the Verizon provider from our overflow center. I'm just so lost and need to figure something out quickly.
Logged

Offline jherrmann

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Strange issue with intermittent disconnects on interflowed calls
« Reply #1 on: August 06, 2017, 01:12:55 AM »
==MITEL PRI Trace==

Code: [Select]
2017-08-05  18:02:54  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 65 NS 81 INFO Dest PD=0x8 CR=0x10b2  ALERTING(0x1)

2017-08-05  18:02:55  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 65 NS 82 INFO Dest PD=0x8 CR=0x10b2  CONNECT(0x7)

2017-08-05  18:02:55  Link 1  - To Mitel   - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 83 NS 65 INFO Orig PD=0x8 CR=0x10b2  CONNECT_ACK(0xf)

2017-08-05  18:02:59  Link 1  - To Mitel   - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 83 NS 66 INFO Dest PD=0x8 CR=0x707  CONNECT(0x7)

2017-08-05  18:02:59  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 67 NS 83 INFO Orig PD=0x8 CR=0x707  CONNECT_ACK(0xf)

2017-08-05  18:03:02  Link 1  - From Mitel - HLen 4, ILen 43, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 67 NS 84 INFO Orig PD=0x8 CR=0x708  SETUP(0x5)
1   00000100 Information Element: Bearer Capability:
2   IE Length                   : 3  octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---00000 Info. trans. cap.  : Speech
4   1------- Extension bit      : Not Continued
    -00----- Transfer Mode      : Circuit Mode
    ---10000 Info. trans. rate  : 64 kbits/s
5   1------- Extension bit      : Not Continued
    -01----- Layer identifier   : 1
    ---00010 Layer 1 protocol   : Rec. G.711 u-law
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----1--- Preferred/Exclusive: exclusive
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0010001 Channel Number     : 17
1   01101100 Information Element: Calling Party Number:
2   IE Length                   : 12 octets
3   0------- Extension bit      : Continued
    -010---- Type of number     : National number
    ----0001 Numbering plan     : ISDN/telephony numbering - Rec. E.164
3a  1------- Extension bit      : Not Continued
    -00----- Presentation       : Allowed
    ---000-- Spare
    ------00 Screening          : User provided, not screened
4   ******** Phone number       : [425###1205]
1   01110000 Information Element: Called Party Number:
2   IE Length                   : 12 octets
3   1------- Extension bit      : Not Continued
    -000---- Type of number     : Unknown
    ----0000 Numbering plan     : Unknown
4   ******** Phone number       : [1330###4357]

2017-08-05  18:03:02  Link 1  - To Mitel   - HLen 4, ILen 10, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 85 NS 67 INFO Dest PD=0x8 CR=0x708  CALL PROCEEDING(0x2)
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----1--- Preferred/Exclusive: exclusive
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0010001 Channel Number     : 17

2017-08-05  18:03:03  Link 1  - From Mitel - HLen 4, ILen 43, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 68 NS 85 INFO Orig PD=0x8 CR=0x709  SETUP(0x5)
1   00000100 Information Element: Bearer Capability:
2   IE Length                   : 3  octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---00000 Info. trans. cap.  : Speech
4   1------- Extension bit      : Not Continued
    -00----- Transfer Mode      : Circuit Mode
    ---10000 Info. trans. rate  : 64 kbits/s
5   1------- Extension bit      : Not Continued
    -01----- Layer identifier   : 1
    ---00010 Layer 1 protocol   : Rec. G.711 u-law
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----1--- Preferred/Exclusive: exclusive
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0010000 Channel Number     : 16
1   01101100 Information Element: Calling Party Number:
2   IE Length                   : 12 octets
3   0------- Extension bit      : Continued
    -010---- Type of number     : National number
    ----0001 Numbering plan     : ISDN/telephony numbering - Rec. E.164
3a  1------- Extension bit      : Not Continued
    -00----- Presentation       : Allowed
    ---000-- Spare
    ------00 Screening          : User provided, not screened
4   ******** Phone number       : [248###2570]
1   01110000 Information Element: Called Party Number:
2   IE Length                   : 12 octets
3   1------- Extension bit      : Not Continued
    -000---- Type of number     : Unknown
    ----0000 Numbering plan     : Unknown
4   ******** Phone number       : [1855###1039]

2017-08-05  18:03:03  Link 1  - To Mitel   - HLen 4, ILen 10, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 86 NS 68 INFO Dest PD=0x8 CR=0x709  CALL PROCEEDING(0x2)
1   00011000 Information Element: Channel Identification:
2   IE Length                   : 3 octets
3   1------- Extension bit      : Not Continued
    -0------ Interface ident.   : implicitly identified
    --1----- Interface type     : primary rate
    ---0---- Spare
    ----1--- Preferred/Exclusive: exclusive
    -----0-- D-channel indicator: not the D channel
    ------01 Info. chan. sel.   : as indicated in the following octets
3.2 1------- Extension bit      : Not Continued
    -00----- Coding Std         : CCITT Std
    ---0---- Channel indicated  : by following octets
    ----0011 Chan/Map type      : B-chan units
3.3 1------- Extension bit      : Not Continued - Single channel
    -0010000 Channel Number     : 16

2017-08-05  18:03:06  Link 1  - To Mitel   - HLen 4, ILen 13, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 86 NS 69 INFO Dest PD=0x8 CR=0x708  PROGRESS(0x3)
1   00001000 Information Element: Cause: 
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- spare 
    ----0010 Location           : Public network serving the local user
4   1------- Extension bit      : Not Continued
    -1111111 Cause code         : Interworking, unspecified                     
1   00011110 Information Element: Progress Indicator:
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- Spare              : Spare
    ----0010 Location           : Public network serving the local user
4   1------- Extension bit      : Not Continued
    -0000001 Description        : Call is not end-to-end ISDN

2017-08-05  18:03:06  Link 1  - To Mitel   - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 86 NS 70 INFO Dest PD=0x8 CR=0x708  CONNECT(0x7)

2017-08-05  18:03:06  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 71 NS 86 INFO Orig PD=0x8 CR=0x708  CONNECT_ACK(0xf)

2017-08-05  18:03:06  Link 1  - To Mitel   - HLen 4, ILen 9, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 86 NS 71 INFO Dest PD=0x8 CR=0x709  PROGRESS(0x3)
1   00011110 Information Element: Progress Indicator:
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- Spare              : Spare
    ----0010 Location           : Public network serving the local user
4   1------- Extension bit      : Not Continued
    -0001000 Description        : In-band information now available

2017-08-05  18:03:06  Link 1  - To Mitel   - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 87 NS 72 INFO Dest PD=0x8 CR=0x709  CONNECT(0x7)

2017-08-05  18:03:06  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 73 NS 87 INFO Orig PD=0x8 CR=0x709  CONNECT_ACK(0xf)

2017-08-05  18:03:14  Link 1  - To Mitel   - HLen 4, ILen 9, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 88 NS 73 INFO Orig PD=0x8 CR=0xcae  DISCONNECT(0x45)
1   00001000 Information Element: Cause: 
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- spare 
    ----0000 Location           : User
4   1------- Extension bit      : Not Continued
    -0010000 Cause code         : normal call clearing                         

2017-08-05  18:03:14  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 74 NS 88 INFO Dest PD=0x8 CR=0xcae  RELEASE(0x4d)

2017-08-05  18:03:14  Link 1  - From Mitel - HLen 4, ILen 9, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 74 NS 89 INFO Orig PD=0x8 CR=0x6ffe  DISCONNECT(0x45)
1   00001000 Information Element: Cause: 
2   IE Length                   : 2 octets
3   1------- Extension bit      : Not Continued
    -00----- Coding Standard    : CCITT
    ---0---- spare 
    ----0000 Location           : User
4   1------- Extension bit      : Not Continued
    -0010000 Cause code         : normal call clearing                         

2017-08-05  18:03:14  Link 1  - To Mitel   - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 90 NS 74 INFO Orig PD=0x8 CR=0xcae  RELEASE COM(0x5a)

2017-08-05  18:03:14  Link 1  - To Mitel   - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 1 P/F 0 NR 90 NS 75 INFO Dest PD=0x8 CR=0x6ffe  RELEASE(0x4d)

2017-08-05  18:03:14  Link 1  - From Mitel - HLen 4, ILen 5, IType 5
SAPI 0 TEI 0 C/R 0 P/F 0 NR 76 NS 90 INFO Orig PD=0x8 CR=0x6ffe  RELEASE COM(0x5a)
Logged

Offline jherrmann

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Strange issue with intermittent disconnects on interflowed calls
« Reply #2 on: August 06, 2017, 01:16:34 AM »
==SIP Logs - From Overflow Center's PBX==

Code: [Select]
8/4/17 17:43:54
ANI 8005116880
740-855-5251  DNIS 1008171
Snippet from C:\Users\Tomu-admin\Desktop\080417_SIP\SIPEngine.ininlog
Message Timestamp (UTC-04:00) Topic Thread
SIPHandlerIO::submit_recvd_message : *?INV$(P#266415) - udp recv 10.###.46.102:5060 <- 10.21.4.125:5060 (retried-request) msg=
INVITE sip:1008171@10.21.46.102;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.21.4.125:5060;branch=z9hG4bKb3725ac4b6877f55dc8292388, SIP/2.0/UDP 172.31.154.77:5085;branch=z9hG4bKrjpn7a108gsg4rtvffg0.1
To: <sip:1008171@garfield.infocisionprod.globalipcom.com>
Content-Type: application/sdp
Allow: INVITE, ACK, BYE, OPTIONS, CANCEL, SUBSCRIBE, REFER
Accept: application/sdp
Call-ID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
From: <sip:8005116880@74.80.226.163>;tag=e181103b
Date: Fri, 04 Aug 2017 21:43:55 GMT
Contact: <sip:8005116880@172.31.154.77:5085;sipappsessionid=app-1tym8ppll31n9;transport=udp>
Ncp-Prcd: ICT
Allow-Events: refer
Supported: replaces, timer
Accept-Encoding:
Accept-Language: en
Privacy: none
Max-Forwards: 68
Session-Expires: 1800;refresher=uac
CSeq: 1 INVITE
Content-Length: 221
P-Asserted-Identity: UNAVAILABLE <sip:+18005116880@65.211.120.237>
Record-Route: <sip:10.21.4.125:5060;lr;transport=udp>

v=0
o=MediaServer 3710871835 3710871836 IN IP4 172.31.154.196
s=-
i=Media Server version 2,0,0,238
c=IN IP4 172.31.154.196
t=0 0
m=audio 20300 RTP/AVP 0
c=IN IP4 172.31.154.196
a=sendrecv
a=rtpmap:0 PCMU/8000/1 17:43:54.8691133_0001 SIPEngine.Packets 0x27bc
SIPRequestInstance::SIPRequestInstance : inbound-leg: SIPCallLeg {
to/remote: <sip:8005116880@74.80.226.163>;tag=e181103b
from/local: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
callID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36}
17:43:54.8716133_0004 SIPEngine.Processing 0x18cc
SIPSession::updateDestination : callID=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, old destination=10.21.4.125:5060
new destination=SIPViaUrl { host: "10.21.4.125" port: "5060" ttl: "" maddr: "" received: "" rport: "" branch: "z9hG4bKb3725ac4b6877f55dc8292388" transport: "udp" hidden: "false" generic-param { } } 17:43:54.8716133_0017 SIPEngine.Processing 0x1998
SIPSession::recordRoute : callID=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, total route entries=2, route=SIPRouteUrl { displayName: "" generic-param { } SIPUrl { phone: 0 scheme: "sip" user: "8005116880" passwd: "" host: "172.31.154.77" port: "5085" transport: "udp" userparam: "ip" method: "INVITE" maddr: "" other-param { sipappsessionid: "app-1tym8ppll31n9" } headers { } original: "sip:8005116880@172.31.154.77:5085;sipappsessionid=app-1tym8ppll31n9;transport=udp" } }, SIPRouteUrl { displayName: "" generic-param { } SIPUrl { phone: 0 scheme: "sip" user: "" passwd: "" host: "10.21.4.125" port: "5060" transport: "udp" userparam: "ip" method: "INVITE" maddr: "" other-param { } headers { } original: "sip:10.21.4.125:5060;lr;transport=udp" } } 17:43:54.8716133_0034 SIPEngine.Processing 0x1998
SIPUDPHandlerIO::issue_msg_write : S#145407: (P#266417)*100->INV$(P#266415) - udp xmit 10.21.46.102:5060 -> 10.21.4.125:5060 [410] msg=
SIP/2.0 100 Trying
To: <sip:1008171@garfield.infocisionprod.globalipcom.com>
From: <sip:8005116880@74.80.226.163>;tag=e181103b
Via: SIP/2.0/UDP 10.21.4.125:5060;branch=z9hG4bKb3725ac4b6877f55dc8292388, SIP/2.0/UDP 172.31.154.77:5085;branch=z9hG4bKrjpn7a108gsg4rtvffg0.1
CSeq: 1 INVITE
Call-ID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
User-Agent: ININ-TsServer/4.0006.0017.364
Content-Length: 0



.?AVSIPResponseEntry@@ 17:43:54.8716133_0038 SIPEngine.Packets 0x1998
SIPSession::GetCustomHeaders : Found custom header=Call-ID, value=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
17:43:54.8741133_0018 SIPEngine.Processing 0x1998
SIPInboundIndication::SIPInboundIndication : Before
.?AVSIPInboundIndication@@ lrn=355812584 crn=0 user=0x000237ff
custom=[Call-ID/wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36,From/<sip:8005116880@74.80.226.163>;tag=e181103b,P-Asserted-Identity/UNAVAILABLE <sip:+18005116880@65.211.120.237>]
rUri=sip:1008171@10.21.46.102:5060 contact=sip:8005116880@172.31.154.77:5085 agent=
to=[]/[sip:1008171@garfield.infocisionprod.globalipcom.com:5060]
from=[]/[sip:8005116880@74.80.226.163:5060]
asserted identity=[UNAVAILABLE]/[sip:+18005116880@65.211.120.237]
referred-by=[]/[sip:]
events=[refer]
allow="ACK", "BYE", "CANCEL", "INVITE", "OPTIONS", "REFER", "SUBSCRIBE"
route_list="sip:8005116880@172.31.154.77:5085;sipappsessionid=app-1tym8ppll31n9", "sip:10.21.4.125:5060;lr"
dialog={call-id=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, to-tag=ch4cnjq, from-tag=e181103b}
media list=[Media Type=0, Address=172.31.154.196, Port=20300, Port Count=1
Payload=[0/G.711 mu-law]
direction=0, Attributes=[rtpmap=[0 PCMU/8000/1]], Fax Attributes=[]]
full body=true 17:43:54.8741133_0029 SIPEngine.Processing 0x19c4
SIPEngineWorkerThread::dispatch : assigning crn=2402653098 to callID=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
17:43:54.8791133_0081 SIPEngine.Processing 0x19d0
SIPUDPHandlerIO::issue_msg_write : S#145407: (P#26641b)*200$->INV$(P#266415) - udp xmit 10.21.46.102:5060 -> 10.21.4.125:5060 [739] msg=
SIP/2.0 200 OK
To: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
From: <sip:8005116880@74.80.226.163>;tag=e181103b
Via: SIP/2.0/UDP 10.21.4.125:5060;branch=z9hG4bKb3725ac4b6877f55dc8292388, SIP/2.0/UDP 172.31.154.77:5085;branch=z9hG4bKrjpn7a108gsg4rtvffg0.1
CSeq: 1 INVITE
Call-ID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
Record-Route: <sip:10.21.4.125:5060;lr;transport=udp>
Contact: <sip:1008171@10.21.46.102:5060>
User-Agent: ININ-TsServer/4.0006.0017.364
x-inin-crn: 2402653098;loc=GFH;ms=SVRGFHMED05
Content-Type: application/sdp
Content-Length: 144

v=0
o=ININ 30287897 30287899 IN IP4 10.21.46.102
s=Interaction
c=IN IP4 199.76.37.170
t=0 0
m=audio 26566 RTP/AVP 0
a=rtpmap:0 PCMU/8000


.?AVSIPRetriedResponseEntry@@ 17:43:54.9341133_0133 SIPEngine.Packets 0x1998
SIPHandlerIO::submit_recvd_message : *?ACK(P#26641c) - udp recv 10.21.46.102:5060 <- 10.21.4.125:5060 (retried-request) msg=
ACK sip:1008171@10.21.46.102:5060 SIP/2.0
Via: SIP/2.0/UDP 10.21.4.125:5060;branch=z9hG4bK31f954e2f9a30e9b707b49824, SIP/2.0/UDP 172.31.154.77:5085;branch=z9hG4bK0c746930cob51cro7lr0.1
To: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
CSeq: 1 ACK
Content-Length: 0
Call-ID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
Max-Forwards: 68
From: <sip:8005116880@74.80.226.163>;tag=e181103b
Record-Route: <sip:10.21.4.125:5060;lr;transport=udp> 17:43:55.1366133_0005 SIPEngine.Packets 0x27bc
SIPRequestInstance::SIPRequestInstance : inbound-leg: SIPCallLeg {
to/remote: <sip:8005116880@74.80.226.163>;tag=e181103b
from/local: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
callID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36}
17:43:55.1366133_0023 SIPEngine.Processing 0x18cc
SIPSession::updateDestination : callID=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, old destination=10.21.4.125:5060
new destination=SIPViaUrl { host: "10.21.4.125" port: "5060" ttl: "" maddr: "" received: "" rport: "" branch: "z9hG4bK31f954e2f9a30e9b707b49824" transport: "udp" hidden: "false" generic-param { } } 17:43:55.1366133_0036 SIPEngine.Processing 0x1998
SIPSession::GetCustomHeaders : Found custom header=Call-ID, value=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
17:43:55.1366133_0041 SIPEngine.Processing 0x1998
SIPAnswerConfirmation::SIPAnswerConfirmation : Before
.?AVSIPAnswerConfirmation@@ lrn=355812584 crn=2402653098 user=0x00000000
error=eSipError=0 (No error)dialog={call-id=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, to-tag=e181103b, from-tag=ch4cnjq} 17:43:55.1366133_0047 SIPEngine.Processing 0x19d0
SIPHandlerIO::submit_recvd_message : ?BYE(P#266ce2) - udp recv 10.21.46.102:5060 <- 10.21.4.125:5060 (retried-request) msg=
BYE sip:1008171@10.21.46.102:5060 SIP/2.0
Via: SIP/2.0/UDP 10.21.4.125:5060;branch=z9hG4bK4f1cbaee50b8545b8ed9fd756, SIP/2.0/UDP 172.31.154.77:5085;branch=z9hG4bK0c746930cob51cro7lr0cd0000010.1
To: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
CSeq: 2 BYE
Content-Length: 0
Call-ID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
Max-Forwards: 68
From: <sip:8005116880@74.80.226.163>;tag=e181103b
Record-Route: <sip:10.21.4.125:5060;lr;transport=udp> 17:46:14.3541133_0103 SIPEngine.Packets 0x27bc
SIPRequestInstance::SIPRequestInstance : inbound-leg: SIPCallLeg {
to/remote: <sip:8005116880@74.80.226.163>;tag=e181103b
from/local: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
callID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36}
17:46:14.3541133_0193 SIPEngine.Processing 0x18cc
SIPSession::updateDestination : callID=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, old destination=10.21.4.125:5060
new destination=SIPViaUrl { host: "10.21.4.125" port: "5060" ttl: "" maddr: "" received: "" rport: "" branch: "z9hG4bK4f1cbaee50b8545b8ed9fd756" transport: "udp" hidden: "false" generic-param { } } 17:46:14.3566133_0024 SIPEngine.Processing 0x1998
SIPUDPHandlerIO::issue_msg_write : S#145407: (P#266ce4)200->BYE(P#266ce2) - udp xmit 10.21.46.102:5060 -> 10.21.4.125:5060 [545] msg=
SIP/2.0 200 OK
To: <sip:1008171@garfield.infocisionprod.globalipcom.com>;tag=ch4cnjq
From: <sip:8005116880@74.80.226.163>;tag=e181103b
Via: SIP/2.0/UDP 10.21.4.125:5060;branch=z9hG4bK4f1cbaee50b8545b8ed9fd756, SIP/2.0/UDP 172.31.154.77:5085;branch=z9hG4bK0c746930cob51cro7lr0cd0000010.1
CSeq: 2 BYE
Call-ID: wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36
Record-Route: <sip:10.21.4.125:5060;lr;transport=udp>
Contact: <sip:1008171@10.21.46.102:5060>
User-Agent: ININ-TsServer/4.0006.0017.364
x-inin-crn: 2402653098
Content-Length: 0



.?AVSIPResponseEntry@@ 17:46:14.3566133_0061 SIPEngine.Packets 0x1998
SIPEngineWorkerThread::dispatch : Before [
.?AVSIPDisconnectIndication@@ lrn=355812584 crn=2402653098 user=0x00000000 code=1 reason=BYE reasonHdr= [] uui=[] dialog={call-id=wlss-fcc72a0b-0ba58fac67af5f76@152.188.161.36, to-tag=, from-tag=}]
17:46:14.3566133_0073 SIPEngine.Processing 0x19d0
 
Logged

Offline Tech Electronics

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2984
  • Country: us
  • Karma: +89/-1
    • View Profile
Re: Strange issue with intermittent disconnects on interflowed calls
« Reply #3 on: August 08, 2017, 10:11:29 AM »
jherrmann,

The two sets of logs don't seem to correlate with one another; ie different calls at different times. Is there a time zone/date difference between the sites?

The only way anyone would be able to figure anything out is if the information is from the same call end-to-end.

Have you talked to the Carriers to have them look and see who is disconnecting first?

Thanks,

TE
Logged

Pages: [1]   Go Up
« previous next »
 

Sitemap 1 2 3 4 5 6 7 8 9 10