We have an issue with one SIP trunk with incomming calls being aswered by ACD path. Here is the scenario:
1) First external user calls DDI that goes into ACD Path, the call is aswered and a RAD message is played to the caller
2) After few seconds a second external user calls the same DDI and because the RAD port is busy (there is only 1 RAD port assigned to the ACD Path) the second caller hears ringback tone
3) The first caller hangs up, the RAD port is released, the 2nd caller stops hearing the ring back tone and the call is established, but no RAD message is played to the 2nd caller.
I analyzed the SIP trunk signalling for both callers and found following:
- The RTP stream in the second call is not present (both ways)
- The INVITE command of the second caller is sent with Connection Information: IN IPv4 0.0.0.0 and with Media Attribute: inactive (not sure why)
I contacted the SIP trunk provider and they responded that sending "Connection Information: IN IPv4 0.0.0.0 and Media Attribute: inactive" in the INVITE packet is actually correct, and the problem is on our side that the RTP stream is not started. I was playing with the settings in the SIP Peer Profile, but without any positive results. Any ideas?
The first (correct) call looks like the following:
|Time | 195.39.106.25 |
| | | 10.0.0.2 |
|2013-07-09 11:01:28.227219| INVITE SDP (g729 g711A telephone-eventRTPType-...) |SIP From: <sip:733641075@cz.in.gtsce.com;user=phone To:"377183420 377183420"<sip:377183420@cz.in.gtsce.com
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:28.228213| 100 Trying| |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:28.412055| 180 Ringing SDP (g729 g711A telephone-eventRTP...e-101) |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:28.431467| PRACK | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:28.432285| 200 OK | |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:41.929029| 200 OK SDP (g729 g711A telephone-eventRTPType-...) |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:41.960493| ACK | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:41.961070| INVITE | |SIP From: <sip:733641075@cz.in.gtsce.com;user=phone To:"377183420 377183420"<sip:377183420@cz.in.gtsce.com
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:41.963778| 100 Trying| |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:41.994705| 491 Request Pending |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:42.009528| ACK | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:43.292056| INVITE SDP (g711A g711U telephone-eventRTPType...1) |SIP Request
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:43.341148| 200 OK SDP (g711A g711U telephone-eventRTPType...1) |SIP Status
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:43.407878| ACK | |SIP Request
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:43.445355| RTP (g711A) |RTP Num packets:713 Duration:14.245s SSRC:0x2418B6
| |(47742) <------------------ (20788) |
|2013-07-09 11:01:43.475104| RTP (g711A) |RTP Num packets:711 Duration:14.199s SSRC:0xADA58E12
| |(47742) ------------------> (20788) |
|2013-07-09 11:01:57.711100| BYE | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:57.712018| 200 OK | |SIP Status
| |(5060) <------------------ (5060) |
The second call with no RTP stream established looks like the following:
|Time | 195.39.106.25 |
| | | 10.0.0.2 |
|2013-07-09 11:01:47.592499| INVITE SDP (g729 g711A telephone-eventRTPType-...) |SIP From: <sip:775587412@cz.in.gtsce.com;user=phone To:"377183420 377183420"<sip:377183420@cz.in.gtsce.com
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:47.593604| 100 Trying| |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:47.792658| 180 Ringing SDP (g729 g711A telephone-eventRTP...e-101) |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:01:47.811307| PRACK | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:01:47.812109| 200 OK | |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:02:00.185926| 200 OK SDP (g729 g711A telephone-eventRTPType-...) |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:02:00.218604| ACK | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:02:00.219102| INVITE | |SIP From: <sip:775587412@cz.in.gtsce.com;user=phone To:"377183420 377183420"<sip:377183420@cz.in.gtsce.com
| |(5060) ------------------> (5060) |
|2013-07-09 11:02:00.221900| 100 Trying| |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:02:00.252632| 200 OK SDP (g711A g711U telephone-eventRTPType...1) |SIP Status
| |(5060) <------------------ (5060) |
|2013-07-09 11:02:00.303032| ACK SDP (g711A g711U telephone-eventRTPType-101) |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:02:21.906971| BYE | |SIP Request
| |(5060) ------------------> (5060) |
|2013-07-09 11:02:21.908028| 200 OK | |SIP Status
| |(5060) <------------------ (5060) |
195.39.106.25 is the IP of the SIP trunk, 10.0.0.2 is WAN IP of the MBG
