Jump to content
Vodia PBX forum
Michael

Agent Group Call Drops And Gap time issues

Recommended Posts

Whatever I set the gap time to the the first message plays in half the time of what it should instead of waiting the full gap time. Perhaps this is the planned behavior by the developers but neither the web interface or wiki say that it should do this on the first time playing the *1 message. After the first message is played the gap time is honored by the system at its full value.

 

Also, after ~120 seconds the call drops and hangs up on the caller. This happens on 100% of the calls into the agent group.

 

[7] 2008/11/18 23:17:36: Set packet length to 30 
[6] 2008/11/18 23:17:36: Sending RTP for 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c to 192.168.1.101:3000 
[7] 2008/11/18 23:17:36: ACD: Entering queue 390 
[7] 2008/11/18 23:17:36: ACD: Next stage in 390 has 6 agents available, 6 selected 
[7] 2008/11/18 23:17:36: Set packet length to 30 
[6] 2008/11/18 23:17:36: Sending RTP for 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c to 98.214.110.245:3000 
[7] 2008/11/18 23:17:41: ACD: Next stage in 390 has no agents available 
[7] 2008/11/18 23:19:36: Last message repeated 23 times 
[5] 2008/11/18 23:19:36: Unconnected call abdccc70@pbx#1657135811 
[7] 2008/11/18 23:19:36: Call ad418d4d@pbx#913810781: Clear last request 
[7] 2008/11/18 23:19:36: Call ef31905a@pbx#1984488040: Clear last request 
[7] 2008/11/18 23:19:36: Call ad418d4d@pbx#913810781: Clear last INVITE 
[5] 2008/11/18 23:19:36: INVITE Response: Terminate ad418d4d@pbx 
[7] 2008/11/18 23:19:36: Other Ports: 5 
[7] 2008/11/18 23:19:36: Call Port: 2f80d4d8@pbx#875509779 
[7] 2008/11/18 23:19:36: Call Port: 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c 
[7] 2008/11/18 23:19:36: Call Port: 4175b227@pbx#1792728335 
[7] 2008/11/18 23:19:36: Call Port: ecdafa91@pbx#1027427496 
[7] 2008/11/18 23:19:36: Call Port: ef31905a@pbx#1984488040 
[7] 2008/11/18 23:19:36: Call 4175b227@pbx#1792728335: Clear last request 
[7] 2008/11/18 23:19:36: Call ef31905a@pbx#1984488040: Clear last INVITE 
[5] 2008/11/18 23:19:36: INVITE Response: Terminate ef31905a@pbx 
[7] 2008/11/18 23:19:36: Other Ports: 4 
[7] 2008/11/18 23:19:36: Call Port: 2f80d4d8@pbx#875509779 
[7] 2008/11/18 23:19:36: Call Port: 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c 
[7] 2008/11/18 23:19:36: Call Port: 4175b227@pbx#1792728335 
[7] 2008/11/18 23:19:36: Call Port: ecdafa91@pbx#1027427496 
[7] 2008/11/18 23:19:36: Call 4175b227@pbx#1792728335: Clear last INVITE 
[5] 2008/11/18 23:19:36: INVITE Response: Terminate 4175b227@pbx 
[7] 2008/11/18 23:19:36: Other Ports: 3 
[7] 2008/11/18 23:19:36: Call Port: 2f80d4d8@pbx#875509779 
[7] 2008/11/18 23:19:36: Call Port: 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c 
[7] 2008/11/18 23:19:36: Call Port: ecdafa91@pbx#1027427496 
[7] 2008/11/18 23:19:36: Call 2f80d4d8@pbx#875509779: Clear last request 
[7] 2008/11/18 23:19:36: Call 2f80d4d8@pbx#875509779: Clear last INVITE 
[5] 2008/11/18 23:19:36: INVITE Response: Terminate 2f80d4d8@pbx 
[7] 2008/11/18 23:19:36: Other Ports: 2 
[7] 2008/11/18 23:19:36: Call Port: 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c 
[7] 2008/11/18 23:19:36: Call Port: ecdafa91@pbx#1027427496 
[7] 2008/11/18 23:19:36: Call 37aef66bda2d61437edec8075492f98c@192.168.1.101#e7cd63951c: Clear last request 
[5] 2008/11/18 23:19:36: BYE Response: Terminate 37aef66bda2d61437edec8075492f98c@192.168.1.101 
[7] 2008/11/18 23:19:36: Other Ports: 1 
[7] 2008/11/18 23:19:36: Call Port: ecdafa91@pbx#1027427496 
[7] 2008/11/18 23:19:37: Call ecdafa91@pbx#1027427496: Clear last request 
[7] 2008/11/18 23:19:37: Call ecdafa91@pbx#1027427496: Clear last INVITE 
[5] 2008/11/18 23:19:37: INVITE Response: Terminate ecdafa91@pbx 

Share this post


Link to post
Share on other sites
Whatever I set the gap time to the the first message plays in half the time of what it should instead of waiting the full gap time. Perhaps this is the planned behavior by the developers but neither the web interface or wiki say that it should do this on the first time playing the *1 message. After the first message is played the gap time is honored by the system at its full value.

 

That's a feature. You can also spefify the initial waiting time, just updated http://wiki.pbxnsip.com/index.php/Agent_Group.

 

Also, after ~120 seconds the call drops and hangs up on the caller. This happens on 100% of the calls into the agent group.

 

Are those calls technically connected (on SIP level, did the PBX send "200 Ok")? Otherwise, this is just the regular ringing timeout. Calls generally cannot stay unconnected for a too long time. What is the "Event for connecting the call"?

Share this post


Link to post
Share on other sites
Are those calls technically connected (on SIP level, did the PBX send "200 Ok")? Otherwise, this is just the regular ringing timeout. Calls generally cannot stay unconnected for a too long time. What is the "Event for connecting the call"?

 

It is the default of "Entering the agent group". What should I set it to so that the caller hears music on hold indefinitely until and agent answers the phone, even if it takes 30 min for the agent to answer? If it matters I also have "Ringback tone" set to "No ringback tone, continue playing music".

 

Thank you

Share this post


Link to post
Share on other sites
It is the default of "Entering the agent group". What should I set it to so that the caller hears music on hold indefinitely until and agent answers the phone, even if it takes 30 min for the agent to answer? If it matters I also have "Ringback tone" set to "No ringback tone, continue playing music".

 

Okay, that setting is fine. Of course it is possible to have callers in the queue for 2 minutes (unfortunately for them). 2 minutes just sound like there is a problem on the SIP level. Is there anything in the log where the PBX explains why it disconnects the call? Are you using redirections with the value of two minutes?

Share this post


Link to post
Share on other sites
Okay, that setting is fine. Of course it is possible to have callers in the queue for 2 minutes (unfortunately for them). 2 minutes just sound like there is a problem on the SIP level. Is there anything in the log where the PBX explains why it disconnects the call? Are you using redirections with the value of two minutes?

 

I attached the log in the first post. No idea what most of it means, I was hoping it showed you what you needed.

Share this post


Link to post
Share on other sites
Well, that log did not reveal what the problem was... It would be good to see the SIP packets. See http://wiki.pbxnsip.com/index.php/Log_Setup on how to turn that on.

 

 

From what I can tell pbxnsip is initiating the disconnect. See below for the trace.

 

192.168.1.100:8790 = Grandstream GXP2000 (originates the call to agent group 1 but could have been any other phone or PSTN call)

192.168.1.100:48536 = Aastra 480i (the agent in the agent group)

192.168.1.199 = pbxnsip

 

U +3.658095 192.168.1.100:8790 -> 192.168.1.199:5060
INVITE sip:1@omnilec.omnilec.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK175f355fb2a12104.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: replaces, timer, path.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58408 INVITE.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Type: application/sdp.
Content-Length: 409.
.
v=0.
o=5090 8000 8000 IN IP4 192.168.1.100.
s=SIP Call.
c=IN IP4 192.168.1.100.
t=0 0.
m=audio 5004 RTP/AVP 0 8 4 18 2 99 9 3 101.
a=sendrecv.
a=rtpmap:0 PCMU/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:4 G723/8000.
a=rtpmap:18 G729/8000.
a=rtpmap:2 G726-32/8000.
a=rtpmap:99 iLBC/8000.
a=fmtp:99 mode=20.
a=rtpmap:9 G722/16000.
a=rtpmap:3 GSM/8000.
a=ptime:20.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.

#
U +0.002353 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK175f355fb2a12104.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58408 INVITE.
Content-Length: 0.
.

#
U +0.000704 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 401 Authentication Required.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK175f355fb2a12104.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58408 INVITE.
User-Agent: OmniLEC-PBX/3.0.1.3023.
WWW-Authenticate: Digest realm="omnilec.omnilec.com",nonce="50da4e7b02d06da8ad8f2eb4fbc5fd14",domain="sip:1@omnilec.omnilec.com",algorithm=MD5.
Content-Length: 0.
.

##
U +0.055248 192.168.1.100:8790 -> 192.168.1.199:5060
ACK sip:1@omnilec.omnilec.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK175f355fb2a12104.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: path.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58408 ACK.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Length: 0.
.

#
U +0.024412 192.168.1.100:8790 -> 192.168.1.199:5060
INVITE sip:1@omnilec.omnilec.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK05702f12417c1916.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: replaces, timer, path.
Authorization: Digest username="5090", realm="omnilec.omnilec.com", algorithm=MD5, uri="sip:1@omnilec.omnilec.com", nonce="50da4e7b02d06da8ad8f2eb4fbc5fd14", response="dced1fd63bc438734d92c1bf78c551f3".
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58409 INVITE.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Type: application/sdp.
Content-Length: 409.
.
v=0.
o=5090 8000 8001 IN IP4 192.168.1.100.
s=SIP Call.
c=IN IP4 192.168.1.100.
t=0 0.
m=audio 5004 RTP/AVP 0 8 4 18 2 99 9 3 101.
a=sendrecv.
a=rtpmap:0 PCMU/8000.
a=rtpmap:8 PCMA/8000.
a=rtpmap:4 G723/8000.
a=rtpmap:18 G729/8000.
a=rtpmap:2 G726-32/8000.
a=rtpmap:99 iLBC/8000.
a=fmtp:99 mode=20.
a=rtpmap:9 G722/16000.
a=rtpmap:3 GSM/8000.
a=ptime:20.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-11.

#
U +0.002488 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 100 Trying.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK05702f12417c1916.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58409 INVITE.
Content-Length: 0.
.

#
U +0.003545 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK05702f12417c1916.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58409 INVITE.
Contact: <sip:5090@192.168.1.199:5060>.
Supported: 100rel, replaces, norefersub.
Allow-Events: refer.
Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE.
Accept: application/sdp.
User-Agent: OmniLEC-PBX/3.0.1.3023.
Content-Type: application/sdp.
Content-Length: 218.
.
v=0.
o=- 1690052149 1690052149 IN IP4 192.168.1.199.
s=-.
c=IN IP4 192.168.1.199.
t=0 0.
m=audio 57946 RTP/AVP 0 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=ptime:20.
a=sendrecv.

#
U +0.000614 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK05702f12417c1916.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58409 INVITE.
Contact: <sip:5090@192.168.1.199:5060>.
Supported: 100rel, replaces, norefersub.
Allow-Events: refer.
Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE.
Accept: application/sdp.
User-Agent: OmniLEC-PBX/3.0.1.3023.
Content-Type: application/sdp.
Content-Length: 218.
.
v=0.
o=- 1690052149 1690052149 IN IP4 192.168.1.199.
s=-.
c=IN IP4 192.168.1.199.
t=0 0.
m=audio 57946 RTP/AVP 0 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=ptime:20.
a=sendrecv.

#####
U +0.051859 192.168.1.100:8790 -> 192.168.1.199:5060
ACK sip:5090@192.168.1.199:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK94ca30858faf927b.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: path.
Authorization: Digest username="5090", realm="omnilec.omnilec.com", algorithm=MD5, uri="sip:1@omnilec.omnilec.com", nonce="50da4e7b02d06da8ad8f2eb4fbc5fd14", response="dced1fd63bc438734d92c1bf78c551f3".
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58409 ACK.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Length: 0.
.

###
U +0.102185 192.168.1.100:8790 -> 192.168.1.199:5060
ACK sip:5090@192.168.1.199:5060 SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bKcbb7d2d7c60f0490.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
To: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: path.
Authorization: Digest username="5090", realm="omnilec.omnilec.com", algorithm=MD5, uri="sip:1@omnilec.omnilec.com", nonce="50da4e7b02d06da8ad8f2eb4fbc5fd14", response="dced1fd63bc438734d92c1bf78c551f3".
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 58409 ACK.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Length: 0.
.

#######################
U +2.098687 192.168.1.199:5060 -> 192.168.1.100:48536
INVITE sip:5075@192.168.1.100:48536;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
Max-Forwards: 70.
Contact: <sip:5075@192.168.1.199:5060;transport=udp>.
Supported: 100rel, replaces, norefersub.
Allow-Events: refer.
Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE.
Accept: application/sdp.
User-Agent: OmniLEC-PBX/3.0.1.3023.
Content-Type: application/sdp.
Content-Length: 206.
.
v=0.
o=- 1230543817 1230543817 IN IP4 192.168.1.199.
s=-.
c=IN IP4 192.168.1.199.
t=0 0.
m=audio 59898 RTP/AVP 0 101.
a=rtpmap:0 pcmu/8000.
a=rtpmap:101 telephone-event/8000.
a=fmtp:101 0-16.
a=sendrecv.

#
U +0.007375 192.168.1.199:5060 -> 198.88.121.95:50031
NOTIFY sip:5055@192.168.1.46:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-0135420987da5c0fc0f154f8728c5d27;rport.
From: <sip:5075@omnilec.omnilec.com:5060>;tag=a9a062bf15.
To: 5055 <sip:5055@omnilec.omnilec.com:5060>;tag=05c3c49a22104f3.
Call-ID: d09623605b87a1903257171e5369e614@192.168.1.46.
CSeq: 2045 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=36.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000743 192.168.1.199:5060 -> 192.168.1.100:5060
NOTIFY sip:5059@192.168.1.100:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-3c1b059180e4239f3a9ba1546b9409a4;rport.
From: Mike <sip:5075@omnilec.omnilec.com:5060>;tag=11db9e64c1.
To: 5059 <sip:5059@omnilec.omnilec.com:5060>;tag=c12577db7b27541.
Call-ID: 4283720fa297f13d46ee1836bc93e151@192.168.1.100.
CSeq: 22282 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=38.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000735 192.168.1.199:5060 -> 192.168.1.100:13368
NOTIFY sip:5062@192.168.1.121:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-8982bfa2b09691cf5b20dfc7fb88d843;rport.
From: Mike <sip:5075@omnilec.omnilec.com:5060>;tag=084a7e54b6.
To: 5062 <sip:5062@omnilec.omnilec.com:5060>;tag=6a05ae5be5c35e3.
Call-ID: 3c83e076d31b5b0b17c75bf6f9dbab84@192.168.1.121.
CSeq: 20142 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=40.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000729 192.168.1.199:5060 -> 192.168.1.100:13772
NOTIFY sip:5060@192.168.1.181:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-2716b749e5350cedf332c2bd4cfaf65e;rport.
From: <sip:5075@omnilec.omnilec.com:5060>;tag=1a811b4594.
To: 5060 <sip:5060@omnilec.omnilec.com:5060>;tag=d4703475047a844.
Call-ID: 68d80c42366ab8752e417f6984978764@192.168.1.181.
CSeq: 21423 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=41.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000736 192.168.1.199:5060 -> 207.152.102.12:5060
NOTIFY sip:5074@192.168.2.2:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-b669a9c2e90ea95db83dda075d075b7c;rport.
From: <sip:5075@omnilec.omnilec.com:5060>;tag=3fe28f42a5.
To: 5074 <sip:5074@omnilec.omnilec.com:5060>;tag=2d245a6fc606564.
Call-ID: 73c2ee1e1d549179cdc9a28c5c8092d2@192.168.2.2.
CSeq: 28934 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=44.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000734 192.168.1.199:5060 -> 192.168.1.100:65422
NOTIFY sip:5056@192.168.1.108:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-2adfff669dfeb5607cabc110145295b8;rport.
From: Mike <sip:5075@omnilec.omnilec.com:5060>;tag=42781e1db2.
To: 5056 <sip:5056@omnilec.omnilec.com:5060>;tag=47877deee2f2de8.
Call-ID: 7572130428fe77e4a184f5b53bbad359@192.168.1.108.
CSeq: 22961 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=43.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000729 192.168.1.199:5060 -> 192.168.1.100:44004
NOTIFY sip:5063@192.168.1.101:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-534e1bf55af2368823152f143f1a0884;rport.
From: <sip:5075@omnilec.omnilec.com:5060>;tag=290a5b0ec4.
To: "5063" <sip:5063@omnilec.omnilec.com:5060>;tag=cfb35f81eb.
Call-ID: 8cd31650efde460c.
CSeq: 12765 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=29.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000732 192.168.1.199:5060 -> 192.168.1.100:53582
NOTIFY sip:5643@192.168.1.198:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-091170e7b0bae6b7eb3c865138f5910b;rport.
From: Mike <sip:5075@omnilec.omnilec.com:5060>;tag=b7820852d7.
To: 5643 <sip:5643@omnilec.omnilec.com:5060>;tag=b5dc39ebc7572c6.
Call-ID: edbffbe21e8edfae2b2a53b20b0f091a@192.168.1.198.
CSeq: 18955 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=25.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000744 192.168.1.199:5060 -> 98.214.205.164:5060
NOTIFY sip:5052@192.168.3.100;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-d14d617cb6cfb65036efb57b0cf5d157;rport.
From: Mike <sip:5075@omnilec.omnilec.com:5060>;tag=9d198b5f12.
To: 5052 <sip:5052@omnilec.omnilec.com:5060>;tag=925105144c4e400.
Call-ID: 7674f7d114df3404e164458d40e3f9d2@192.168.3.100.
CSeq: 25232 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=24.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000741 192.168.1.199:5060 -> 192.168.1.100:15608
NOTIFY sip:5061@192.168.1.182:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-7617f3eea9dcc076f4324ad56628ffac;rport.
From: <sip:5075@omnilec.omnilec.com:5060>;tag=cbbe1cad79.
To: 5061 <sip:5061@omnilec.omnilec.com:5060>;tag=54dee33a4f9e6f2.
Call-ID: 8fcaf294b7606bf53b4af94ec1b6d74a@192.168.1.182.
CSeq: 32533 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=29.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

#
U +0.000749 192.168.1.199:5060 -> 192.168.1.100:11262
NOTIFY sip:5642@192.168.1.179:5060;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-54b877eea20f80c39768d6d38c7c194b;rport.
From: <sip:5075@omnilec.omnilec.com:5060>;tag=d97ae2ab07.
To: 5642 <sip:5642@omnilec.omnilec.com:5060>;tag=afe34fa99e0b3aa.
Call-ID: 8084d01b9f3987dd90baa04c1af79002@192.168.1.179.
CSeq: 10321 NOTIFY.
Max-Forwards: 70.
Contact: <sip:192.168.1.199:5060;transport=udp>.
Event: dialog.
Subscription-State: active;expires=28.
Content-Type: application/dialog-info+xml.
Content-Length: 485.
.
<?xml version="1.0"?>.
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="6" state="full" entity="sip:5075@omnilec.omnilec.com"><dialog id="dummy" call-id="a7cc4b66e54fac4f@192.168.1.177" direction="recipient"><state>confirmed</state><remote><identity>sip:5090@omnilec.omnilec.com</identity><target uri="sip:5090@omnilec.omnilec.com"/></remote><local><identity>sip:1@omnilec.omnilec.com</identity><target uri="sip:1@omnilec.omnilec.com"/></local></dialog></dialog-info>.

############
U +0.109795 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 100 Trying.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

####
U +0.019420 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 180 Ringing.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
Call-Info: <sip:omnilec.omnilec.com>;appearance-index=1.
Allow-Events: talk, hold, conference.
Contact: 5075 <sip:5075@192.168.1.100:48536>.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

################################################################################
#################################################################################
#################################################################################
##########################################################################
U +25.413277 192.168.1.100:8790 -> 192.168.1.199:5060
REGISTER sip:omnilec.omnilec.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK1762bedb230336cd.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=77c8cd8ed7c55457.
To: <sip:5090@omnilec.omnilec.com>.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: path.
Authorization: Digest username="5090", realm="omnilec.omnilec.com", algorithm=MD5, uri="sip:omnilec.omnilec.com", nonce="5a9673f054b1031b8da68dffab6f78dc", response="4910088c35028862a4ed7caed3578706".
Call-ID: 85112a388df2a32d@192.168.1.177.
CSeq: 35700 REGISTER.
Expires: 60.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Length: 0.
.

#
U +0.001850 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK1762bedb230336cd.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=77c8cd8ed7c55457.
To: <sip:5090@omnilec.omnilec.com>;tag=3a927480a8.
Call-ID: 85112a388df2a32d@192.168.1.177.
CSeq: 35700 REGISTER.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>;expires=60.
Content-Length: 0.
.

################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
##################
U +45.026119 192.168.1.100:8790 -> 192.168.1.199:5060
REGISTER sip:omnilec.omnilec.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK7dc7ac93648903c4.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=77c8cd8ed7c55457.
To: <sip:5090@omnilec.omnilec.com>.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: path.
Authorization: Digest username="5090", realm="omnilec.omnilec.com", algorithm=MD5, uri="sip:omnilec.omnilec.com", nonce="5a9673f054b1031b8da68dffab6f78dc", response="4910088c35028862a4ed7caed3578706".
Call-ID: 85112a388df2a32d@192.168.1.177.
CSeq: 35701 REGISTER.
Expires: 60.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Length: 0.
.

#
U +0.001725 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bK7dc7ac93648903c4.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=77c8cd8ed7c55457.
To: <sip:5090@omnilec.omnilec.com>;tag=3a927480a8.
Call-ID: 85112a388df2a32d@192.168.1.177.
CSeq: 35701 REGISTER.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>;expires=59.
Content-Length: 0.
.

################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#################################################################################
#############################################################################
U +45.026195 192.168.1.100:8790 -> 192.168.1.199:5060
REGISTER sip:omnilec.omnilec.com SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bKdefbe8adc4ad2476.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=77c8cd8ed7c55457.
To: <sip:5090@omnilec.omnilec.com>.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Supported: path.
Authorization: Digest username="5090", realm="omnilec.omnilec.com", algorithm=MD5, uri="sip:omnilec.omnilec.com", nonce="5a9673f054b1031b8da68dffab6f78dc", response="4910088c35028862a4ed7caed3578706".
Call-ID: 85112a388df2a32d@192.168.1.177.
CSeq: 35702 REGISTER.
Expires: 60.
User-Agent: Grandstream GXP2000 1.1.5.99.
Max-Forwards: 70.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Content-Length: 0.
.

#
U +0.001743 192.168.1.199:5060 -> 192.168.1.100:8790
SIP/2.0 200 Ok.
Via: SIP/2.0/UDP 192.168.1.100:8790;branch=z9hG4bKdefbe8adc4ad2476.
From: "Name" <sip:5090@omnilec.omnilec.com>;tag=77c8cd8ed7c55457.
To: <sip:5090@omnilec.omnilec.com>;tag=3a927480a8.
Call-ID: 85112a388df2a32d@192.168.1.177.
CSeq: 35702 REGISTER.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>;expires=61.
Content-Length: 0.
.

#######################################
U +4.385167 192.168.1.199:5060 -> 192.168.1.100:48536
CANCEL sip:5075@192.168.1.100:48536;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 CANCEL.
Max-Forwards: 70.
Content-Length: 0.
.

############
U +0.014848 192.168.1.199:5060 -> 192.168.1.100:8790
BYE sip:5090@192.168.1.100:8790;transport=udp SIP/2.0.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-cb12e83ed73d01c21e31e98cf7db82c5;rport.
From: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
To: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 14870 BYE.
Max-Forwards: 70.
Contact: <sip:5090@192.168.1.199:5060>.
RTP-RxStat: Dur=122,Pkt=6108,Oct=1050576,Underun=0.
RTP-TxStat: Dur=122,Pkt=6113,Oct=1051436.
Content-Length: 0.
.

#
U +0.027178 192.168.1.100:8790 -> 192.168.1.199:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-cb12e83ed73d01c21e31e98cf7db82c5;rport.
From: <sip:1@omnilec.omnilec.com>;tag=bbbae5dc0d.
To: "Name" <sip:5090@omnilec.omnilec.com>;tag=0173a8f438ba9faa.
Call-ID: a7cc4b66e54fac4f@192.168.1.177.
CSeq: 14870 BYE.
User-Agent: Grandstream GXP2000 1.1.5.99.
Contact: <sip:5090@192.168.1.100:8790;transport=udp>.
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK,MESSAGE.
Supported: replaces, timer.
Content-Length: 0.
.

##########
U +0.072983 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 200 OK.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 CANCEL.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
Contact: 5075 <sip:5075@192.168.1.100:48536>.
Supported: replaces.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

##
U +0.013778 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 487 Request Terminated.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

######
U +0.498798 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 487 Request Terminated.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

###############
U +0.999994 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 487 Request Terminated.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

###########
U +2.000138 192.168.1.100:48536 -> 192.168.1.199:5060
SIP/2.0 487 Request Terminated.
Call-ID: 1c2bb9be@pbx.
CSeq: 12604 INVITE.
From: "Test (5090)" <sip:5090@omnilec.omnilec.com>;tag=75704733.
To: <sip:1@omnilec.omnilec.com>;tag=4e8c642811db23f.
Via: SIP/2.0/UDP 192.168.1.199:5060;branch=z9hG4bK-ec24ca9d0acaf9df017155c228c2ed17;rport.
Content-Length: 0.
User-Agent: Aastra 480i/1.4.3.23 Brcm Callctrl/1.5.1.0 MxSF/v3.2.8.45.
.

Share this post


Link to post
Share on other sites
From what I can tell pbxnsip is initiating the disconnect. See below for the trace.

 

192.168.1.100:8790 = Grandstream GXP2000 (originates the call to agent group 1 but could have been any other phone or PSTN call)

192.168.1.100:48536 = Aastra 480i (the agent in the agent group)

192.168.1.199 = pbxnsip

 

Hmm. That trace is from the phone; it does not show the LOG messages of the PBX in the context. Yes, it does receive the BYE from the PBX with a beautiful two-way audio stream.

 

Anyway, it smells a little bit like the call is technically not established (still "ringing"). Then the PBX typically disconnects after two minutes. This could be a problem with the ACK routing. A LOG from the PBX would be able to show this.

Share this post


Link to post
Share on other sites
Hmm. That trace is from the phone; it does not show the LOG messages of the PBX in the context. Yes, it does receive the BYE from the PBX with a beautiful two-way audio stream.

 

Anyway, it smells a little bit like the call is technically not established (still "ringing"). Then the PBX typically disconnects after two minutes. This could be a problem with the ACK routing. A LOG from the PBX would be able to show this.

 

 

The very first post is the log file for this (not the same call but the same situation). The trace is on the pbxnsip server using ngrep, not from the phone. I don't understand what else you need from me. If you would like I can register my 2 phones to a test pbxnsip sever over the Internet (I am assuming you have one setup that way) and you could see whatever you need to see on your own server.

Share this post


Link to post
Share on other sites
The very first post is the log file for this (not the same call but the same situation). The trace is on the pbxnsip server using ngrep, not from the phone. I don't understand what else you need from me. If you would like I can register my 2 phones to a test pbxnsip sever over the Internet (I am assuming you have one setup that way) and you could see whatever you need to see on your own server.

 

You should see the SIP messages embedded in the PBX log like the following example:

 

 [5] 2008/12/04 09:53:23: Identify trunk (domain name match) 17
[7] 2008/12/04 09:53:23: SIP Tx tcp:215.111.36.226:2096:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.11.188:2096;branch=z9hG4bK-cpeym97f03ql;rport=2096;received=215.111.36.226
From: <sip:524@pbxnsip.com>;tag=t1qkfe13b2
To: <sip:*97@pbxnsip.com;user=phone>;tag=0b3eebce61
Call-ID: 3c2690d4ed8e-y9flwusywaav
CSeq: 1 INVITE
Content-Length: 0

 

Check out http://wiki.pbxnsip.com/index.php/Log_Setup on how to turn SIP packet logging on.

 

Having the SIP packets with the other log messages of the PBX makes it a lot easier to figure out why and what is gonig on. Maybe you can give that a quick shot. It you cannot get a SIP trace, send me a PM and we'll try to register from here.

Share this post


Link to post
Share on other sites
You should see the SIP messages embedded in the PBX log like the following example:

 

 [5] 2008/12/04 09:53:23: Identify trunk (domain name match) 17
[7] 2008/12/04 09:53:23: SIP Tx tcp:215.111.36.226:2096:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 192.168.11.188:2096;branch=z9hG4bK-cpeym97f03ql;rport=2096;received=215.111.36.226
From: <sip:524@pbxnsip.com>;tag=t1qkfe13b2
To: <sip:*97@pbxnsip.com;user=phone>;tag=0b3eebce61
Call-ID: 3c2690d4ed8e-y9flwusywaav
CSeq: 1 INVITE
Content-Length: 0

 

Check out http://wiki.pbxnsip.com/index.php/Log_Setup on how to turn SIP packet logging on.

 

Having the SIP packets with the other log messages of the PBX makes it a lot easier to figure out why and what is gonig on. Maybe you can give that a quick shot. It you cannot get a SIP trace, send me a PM and we'll try to register from here.

 

I have way too much activity on my system to be able to produce a useful log file. I will PM you.

Share this post


Link to post
Share on other sites
I have way too much activity on my system to be able to produce a useful log file. I will PM you.

You can get the log file at Admin->Status->Logfile on the PBX. (yes, it is useful to get the log when there is no other activity on the system)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...