Thank you very much!
1) Thank you for the correction, I thought I referenced the correct file but
apparently not.
2) That makes a lot of sense, thank you!
3) Humm... I haven't bolted on a sound parser so it probably doesn't detect
RTP as you mentioned. Another thing to add to the list of todo items. Thank
you.
Robert Remsik
ACNS
Desk Phone: 970 491 7120
robert.rem...@colostate.edu
________________________________
From: sindelka <sinde...@ttc.cz>
Sent: Friday, March 10, 2017 10:45:05 AM
To: sipp-users@lists.sourceforge.net
Subject: Re: [Sipp-users] Suggestion for - IVR Scenario
Hi Robert,
1) the pcap you've attached does not match the error log, and neither of the
two illustrates your original issue (404 response to BYE).
2) the pcap shows that the embedded UAC scenario cannot cope with what your SER
(Freeswitch) send back to it. In the 200 OK, there are several Record-Route
headers, so the UAC scenario has to mirror them as Route headers in the ACK and
any subsequent requests it sends within that call, including the BYE - see the
purpose of the rrs attribute of recv and the [routes] keyword in the SIPp
manual. These are missing in the embedded UAC scenario, so the ACK doesn't make
it to the actual UAS and thus the latter keeps re-transmitting the 200 until
timeout; when the timeout expires, it attempts to actively terminate the dialog
by sending a BYE which the UAC scenario doesn't expect to receive - instead, it
intends to send its own one but later.
So if you want to move further, you have to dump the embedded UAC scenario into
a file, modify it the way suggested above, and try again.
3) from your original description, I'm quite sceptical regarding the "detect if
there is audio coming back" part. SIPp does not have an embedded detection of
RTP arrival, let alone a detector/analyzer of that RTP's contents, so you'd
have to glue one to it if you'd want to check that something else than silence
is coming from the IVR.
Pavel
Dne 10.3.2017 v 17:41 Remsik,Robert napsal(a):
Sure! Thank you for the help! :)
For some reason this didn't post the several errors to the screen so I'm
pasting what I've been seeing the in error logs
---- Errors ----
root@monitor:/home/zabbix/AutoCallMatrix/1 $ cat uac_30975_errors.log
sipp: The following events occured:
2017-03-10 09:21:40:420 1489162900.420444: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:21:41 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:21:44:420 1489162904.420305: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:21:45 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:21:48:420 1489162908.420240: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:21:49 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:21:52:419 1489162912.419994: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:21:53 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:21:56:420 1489162916.420085: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:21:57 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:22:00:420 1489162920.420097: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:22:01 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:22:04:421 1489162924.421232: Discarding message which can't be
mapped to a known SIPp call:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 129.82.254.254:5061;branch=z9hG4bK-30930-1-0
Record-Route:
<sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8><sip:129.82.254.202:5066;lr;sipXecs-CallDest=UNK%2CAA;sipXecs-rs=*auth~.*from~MzA5MzBTSVBwVGFnMDAx!083191711afa22cd1495fd22778d74c8>
Record-Route:
<sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9><sip:129.82.254.200;transport=tcp;r2=on;lr;did=36c.3d9>
Record-Route:
<sip:129.82.254.200;r2=on;lr;did=36c.3d9><sip:129.82.254.200;r2=on;lr;did=36c.3d9>
From: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
To: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 1 INVITE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 168
Remote-Party-Id: "IVR"
<sip:IVR@129.82.254.200><sip:IVR@129.82.254.200>;party=calling;privacy=off;screen=no
Date: Fri, 10 Mar 2017 16:22:05 GMT
v=0
o=FreeSWITCH 1489150845 1489150846 IN IP4 129.82.254.200
s=FreeSWITCH
c=IN IP4 129.82.254.200
t=0 0
m=audio 12048 RTP/AVP 0
a=rtpmap:0 PCMU/8000
a=ptime:20
.
2017-03-10 09:22:04:921 1489162924.921063: Discarding message which can't be
mapped to a known SIPp call:
BYE sip:sipp@129.82.254.254:5061 SIP/2.0
Via: SIP/2.0/UDP
129.82.254.200;branch=z9hG4bKf0dd.dcd64e02ac0542f5fe683cff18c426df.0;i=229
Via: SIP/2.0/TCP
129.82.254.202:5066;branch=z9hG4bK-XX-0589jM4`uQ9Y8Im2`gxJrQMhyA
Via: SIP/2.0/UDP 129.82.254.200:15060;rport=15060;branch=z9hG4bKNtFtQ3Q9HcXZK
Max-Forwards: 19
From: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
To: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 104245398 BYE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Reason: SIP;cause=408;text="ACK Timeout"
Content-Length: 0
Date: Fri, 10 Mar 2017 16:22:05 GMT
.
2017-03-10 09:22:05:385 1489162925.385709: Discarding message which can't be
mapped to a known SIPp call:
BYE sip:sipp@129.82.254.254:5061 SIP/2.0
Via: SIP/2.0/UDP
129.82.254.200;branch=z9hG4bKf0dd.dcd64e02ac0542f5fe683cff18c426df.0;i=229
Via: SIP/2.0/TCP
129.82.254.202:5066;branch=z9hG4bK-XX-0589jM4`uQ9Y8Im2`gxJrQMhyA
Via: SIP/2.0/UDP 129.82.254.200:15060;rport=15060;branch=z9hG4bKNtFtQ3Q9HcXZK
Max-Forwards: 19
From: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
To: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 104245398 BYE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Reason: SIP;cause=408;text="ACK Timeout"
Content-Length: 0
Date: Fri, 10 Mar 2017 16:22:05 GMT
.
2017-03-10 09:22:06:385 1489162926.385672: Discarding message which can't be
mapped to a known SIPp call:
BYE sip:sipp@129.82.254.254:5061 SIP/2.0
Via: SIP/2.0/UDP
129.82.254.200;branch=z9hG4bKf0dd.dcd64e02ac0542f5fe683cff18c426df.0;i=229
Via: SIP/2.0/TCP
129.82.254.202:5066;branch=z9hG4bK-XX-0589jM4`uQ9Y8Im2`gxJrQMhyA
Via: SIP/2.0/UDP 129.82.254.200:15060;rport=15060;branch=z9hG4bKNtFtQ3Q9HcXZK
Max-Forwards: 19
From: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
To: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 104245398 BYE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Reason: SIP;cause=408;text="ACK Timeout"
Content-Length: 0
Date: Fri, 10 Mar 2017 16:22:05 GMT
.
2017-03-10 09:22:08:385 1489162928.385672: Discarding message which can't be
mapped to a known SIPp call:
BYE sip:sipp@129.82.254.254:5061 SIP/2.0
Via: SIP/2.0/UDP
129.82.254.200;branch=z9hG4bKf0dd.dcd64e02ac0542f5fe683cff18c426df.0;i=229
Via: SIP/2.0/TCP
129.82.254.202:5066;branch=z9hG4bK-XX-0589jM4`uQ9Y8Im2`gxJrQMhyA
Via: SIP/2.0/UDP 129.82.254.200:15060;rport=15060;branch=z9hG4bKNtFtQ3Q9HcXZK
Max-Forwards: 19
From: 137
<sip:137@129.82.254.200:5060><sip:137@129.82.254.200:5060>;tag=N1QXacZ7Fr6mj
To: sipp
<sip:sipp@129.82.254.254:5061><sip:sipp@129.82.254.254:5061>;tag=30930SIPpTag001
Call-Id: 1-30930@129.82.254.254<mailto:1-30930@129.82.254.254>
Cseq: 104245398 BYE
Contact:
<sip:137@129.82.254.200:15060;transport=udp><sip:137@129.82.254.200:15060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.4.15~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY
Supported: timer, path, replaces
Reason: SIP;cause=408;text="ACK Timeout"
Content-Length: 0
Date: Fri, 10 Mar 2017 16:22:05 GMT
.
2017-03-10 09:22:11:474 1489162931.474507: Aborting call on an unexpected BYE
for call: 1-30975@129.82.254.254<mailto:1-30975@129.82.254.254>.
.:: Command ::.
sipp -sf /home/zabbix/AutoCallMatrix/1/uac.xml 129.82.254.200 -m 1 -au 11012
-ap 24384 -s 137 -i 129.82.254.254 -timeout 90s -timeout_error -d 90000
-trace_screen -trace_err
------------------------------ Scenario Screen -------- [1-9]: Change Screen --
Call-rate(length) Port Total-time Total-calls Remote-host
10.0(90000 ms)/1.000s 5061 32.30 s 1 129.82.254.200:5060(UDP)
Call limit reached (-m 1), 0.000 s period 0 ms scheduler resolution
0 calls (limit 2700) Peak was 1 calls, after 0 s
0 Running, 3 Paused, 0 Woken up
0 dead call msg (discarded) 0 out-of-call msg (discarded)
1 open sockets
Messages Retrans Timeout Unexpected-Msg
INVITE ----------> 1 0 0
100 <---------- 1 0 0 0
180 <---------- 0 0 0 0
183 <---------- 0 0 0 0
200 <---------- E-RTD1 1 1 0 0
ACK ----------> 1 1
Pause [ 1:30] 1 1
BYE ----------> 0 0 0
200 <---------- 0 0 0 0
------------------------------ Test Terminated --------------------------------
----------------------------- Statistics Screen ------- [1-9]: Change Screen --
Start Time | 2017-03-10 09:26:30:160 1489163190.160205
Last Reset Time | 2017-03-10 09:27:02:469 1489163222.469667
Current Time | 2017-03-10 09:27:02:469 1489163222.469781
-------------------------+---------------------------+--------------------------
Counter Name | Periodic value | Cumulative value
-------------------------+---------------------------+--------------------------
Elapsed Time | 00:00:00:000 | 00:00:32:309
Call Rate | 0.000 cps | 0.031 cps
-------------------------+---------------------------+--------------------------
Incoming call created | 0 | 0
OutGoing call created | 0 | 1
Total Call created | | 1
Current Call | 0 |
-------------------------+---------------------------+--------------------------
Successful call | 0 | 0
Failed call | 0 | 1
-------------------------+---------------------------+--------------------------
Response Time 1 | 00:00:00:000 | 00:00:00:211
Call Length | 00:00:00:000 | 00:00:32:208
------------------------------ Test Terminated --------------------------------
2017-03-10 09:27:02:469 1489163222.469379: Aborting call on an unexpected BYE
for call: 1-341@129.82.254.254<mailto:1-341@129.82.254.254>.
Robert Remsik
ACNS
Desk Phone: 970 491 7120
robert.rem...@colostate.edu<mailto:robert.rem...@colostate.edu>
________________________________
From: Sakharam Thorat
<sakharam.tho...@outlook.com><mailto:sakharam.tho...@outlook.com>
Sent: Thursday, March 9, 2017 6:27:54 PM
To: Remsik,Robert;
sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>
Subject: Re: Suggestion for - IVR Scenario
Can we have wireshark trace to debug further ?
Best Regards,
Sakharam Thorat.
________________________________
From: Remsik,Robert
<robert.rem...@colostate.edu><mailto:robert.rem...@colostate.edu>
Sent: Friday, March 10, 2017 3:23 AM
To: sipp-users@lists.sourceforge.net<mailto:sipp-users@lists.sourceforge.net>
Subject: [Sipp-users] Suggestion for - IVR Scenario
Hello!
I'm trying to get a SIPP scenario that will have the client dial a number
(connected to an auto attendant), pick up, detect if there is audio coming
back, and then hang up after 10 seconds.
So far I've been using the basic 'uac.xml' scenario which gets it to call, but
when the client hangs up, the scenario expects a 200 ok but it's getting a 404
not found from the server. I'm unable to track down the origin of the 404 from
the server side, so I'm wondering if I'm using the wrong scenario file for sipp.
Is there a particular scenario file I should be using for this test-case?
Thank you in advance,
Robert
Robert Remsik
ACNS
Desk Phone: 970 491 7120
robert.rem...@colostate.edu<mailto:robert.rem...@colostate.edu>
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net<mailto:Sipp-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------------
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
