Toggle sidebar Toggle sidebar

Fast Busy signal when dialing 800/888 numbers

Status
Not open for further replies.

dannybrook

Joined
Feb 24, 2010
Messages
43
Reaction score
0
Im using the free edition and three polycom ip 550 phones. I have no problems other than the fact that I cannot dial toll free numbers. When i do it from the 3cx softphone i get a "server failure" error.

The log reads: “Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060

Any ideas?
 
Hi there,

Server Failure error generally occurs when the phone is not registered. However do they call internally between them?

Also have you set up an Outbound rule? if yes please specify how..

Are you using a voip provider or a pstn device?
 
Phone is registered and I can make calls between extensions and to any other number. I have a SIP trunk from 888voipstore/CogentVOIP, they're one of the officially supported providers.

I have an outbound rule setup that says calls to number length 7-14 uses Cogent VOIP and does not strip digits.
 
What is set as the Prefix in the outbound rule?

is it blank? if it is please do... 0,1,2,3,4,5,6,7,8,9

Regards,
 
Going by the log printout it looks like you are sending the correct digits (1800xxxxxxx) to them, IF that is the format they want. Do other calls work? If so does the log show the same number format being sent to them , 1xxxxxxxxxx, for North America numbers?

If other calls, same format, work, and toll free calls don't, then you'd better talk to your provider, perhaps they don't allow them as a default.
 
16:15:35.605 Active calls counted toward license limit: []
16:15:05.419 Active calls counted toward license limit: []
16:14:35.233 Active calls counted toward license limit: []
16:14:15.608 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:14:11.615 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:14:07.605 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:14:05.047 Active calls counted toward license limit: []
16:14:03.612 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:13:59.634 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:13:57.637 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:13:56.623 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:13:56.139 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
16:13:53.893 [CM503020]: Normal call termination. Reason: Terminated
16:13:53.893 [CM503016]: Call(14): Attempt to reach <sip:[email protected];user=phone> failed. Reason: Reason Unknown
16:13:53.893 [CM503003]: Call(14): Call to sip:[email protected]:5060 has failed; Cause: 183 Session Progress; from IP:66.23.129.253:5060
16:13:47.778 [CM503025]: Call(14): Calling VoIPline:18008661968@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
16:13:47.544 [CM503004]: Call(14): Route 1: VoIPline:18008661968@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
16:13:47.544 [CM503010]: Making route(s) to <sip:[email protected];user=phone>
16:13:47.528 [CM505001]: Ext.100: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_550-UA/2.1.2.0078] PBX contact: [sip:[email protected]:5060]
16:13:47.528 [CM503001]: Call(14): Incoming call from Ext.100 to <sip:[email protected];user=phone>


That is the most recent log. I'm waiting to hear back from the vendor. I have no issues calling any other phone numbers.
 
There is the possibility that the owner of the toll free number that you are calling doesn't like the number, or lack of, that they receive. After all they are paying for the call and most like to "collect' info on callers.
Blocking your caller ID (*67) has no effect when calling a toll free number.

I would wait and see what your provider can tell you.
 
I sent this log to my trunk provider:

10:27:34.824 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:33.979 [CM504002]: Ext.101: a contact is unregistered. Contact(s): []
10:27:32.278 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:30.831 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:28.248 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:26.837 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:26.251 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:25.566 Active calls counted toward license limit: []
10:27:25.253 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:24.752 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:24.535 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 180 Ringing; from IP:66.23.129.253:5060
10:27:23.260 [CM503020]: Normal call termination. Reason: Terminated
10:27:23.260 [CM503016]: Call(16): Attempt to reach <sip:[email protected]> failed. Reason: Reason Unknown
10:27:23.260 [CM503003]: Call(16): Call to sip:[email protected]:5060 has failed; Cause: 183 Session Progress; from IP:66.23.129.253:5060
10:27:22.854 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:19.818 [CM503025]: Call(16): Calling VoIPline:18004633339@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
10:27:19.601 [CM503004]: Call(16): Route 1: VoIPline:18004633339@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
10:27:19.600 [CM503010]: Making route(s) to <sip:[email protected]>
10:27:19.599 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10373.0] PBX contact: [sip:[email protected]:5060]
10:27:19.597 [CM503001]: Call(16): Incoming call from Ext.101 to <sip:[email protected]>
10:27:18.852 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:16.854 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:15.857 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:15.362 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
10:27:14.176 [CM503020]: Normal call termination. Reason: Terminated
10:27:14.176 [CM503016]: Call(15): Attempt to reach <sip:[email protected]> failed. Reason: Reason Unknown
10:27:14.175 [CM503003]: Call(15): Call to sip:[email protected]:5060 has failed; Cause: 183 Session Progress; from IP:66.23.129.253:5060
10:27:12.193 [CM503025]: Call(15): Calling VoIPline:18004633339@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
10:27:11.975 [CM503004]: Call(15): Route 1: VoIPline:18004633339@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
10:27:11.973 [CM503010]: Making route(s) to <sip:[email protected]>
10:27:11.972 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10373.0] PBX contact: [sip:[email protected]:5060]
10:27:11.970 [CM503001]: Call(15): Incoming call from Ext.101 to <sip:[email protected]>

AND THIS WAS THEIR RESPONSE.....
Hello,

The 1st call attempt at 18:27:09 (GMT):

There were 4 200OKs sent to the customer IP before the call was dropped with no ACK sent in response:

U 2010/02/25 18:27:12.514069 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:13.008632 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:14.005649 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:16.003365 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

On the 2nd call at 18:27:17 (GMT) another handful to 200OKs were returned without an ACK from the customer 3CX

U 2010/02/25 18:27:21.902978 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
ba2fc71e2067474d-1---d8754z-;rport=5060..From: "13234757710";tag=eb1a0c5a..To: ;
tag=gK09dbfa3e..Call-ID: MDE1M2E2MDY5MzZjNjMzYjBiNWFkZGM5NTRlNDMzY2E...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 237..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 4055 28481 IN IP4 67.16.1
10.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 26
226 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000.
.a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:22.404183 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
ba2fc71e2067474d-1---d8754z-;rport=5060..From: "13234757710";tag=eb1a0c5a..To: ;
tag=gK09dbfa3e..Call-ID: MDE1M2E2MDY5MzZjNjMzYjBiNWFkZGM5NTRlNDMzY2E...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 237..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 4055 28481 IN IP4 67.16.1
10.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 26
226 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000.
.a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:23.402205 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
ba2fc71e2067474d-1---d8754z-;rport=5060..From: "13234757710";tag=eb1a0c5a..To: ;
tag=gK09dbfa3e..Call-ID: MDE1M2E2MDY5MzZjNjMzYjBiNWFkZGM5NTRlNDMzY2E...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 237..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 4055 28481 IN IP4 67.16.1
10.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 26
226 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000.
.a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:23.988207 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:25.396252 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
ba2fc71e2067474d-1---d8754z-;rport=5060..From: "13234757710";tag=eb1a0c5a..To: ;
tag=gK09dbfa3e..Call-ID: MDE1M2E2MDY5MzZjNjMzYjBiNWFkZGM5NTRlNDMzY2E...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 237..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 4055 28481 IN IP4 67.16.1
10.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 26
226 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000.
.a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:27.981872 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:29.429389 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
ba2fc71e2067474d-1---d8754z-;rport=5060..From: "13234757710";tag=eb1a0c5a..To: ;
tag=gK09dbfa3e..Call-ID: MDE1M2E2MDY5MzZjNjMzYjBiNWFkZGM5NTRlNDMzY2E...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 237..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 4055 28481 IN IP4 67.16.1
10.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 26
226 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000.
.a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:31.974705 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
801697305646d511-1---d8754z-;rport=5060..From: "13234757710";tag=8466d269..To: ;
tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 238..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 29150 12262 IN IP4 67.16.
110.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 1
3086 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000
..a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:33.384213 66.23.129.253:5060 -> 216.240.61.165:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 216.240.61.165:5060;branch=z9hG4bK-d8754z-
ba2fc71e2067474d-1---d8754z-;rport=5060..From: "13234757710";tag=eb1a0c5a..To: ;
tag=gK09dbfa3e..Call-ID: MDE1M2E2MDY5MzZjNjMzYjBiNWFkZGM5NTRlNDMzY2E...CSeq
: 2 INVITE..Record-Route: ..Accept: application/sdp, application/isup, application/dtm
f, application/dtmf-relay, multipart/mixed..Contact: ..Allow: INVITE,ACK,CANCEL,BYE,REGISTER,INFO,SUBSCRIBE,NOTIF
Y,PRACK,UPDATE,OPTIONS..Supported: timer..Session-Expires: 3600;refresher=u
as..Content-Length: 237..Content-Disposition: session; handling=required..
Content-Type: application/sdp....v=0..o=Sonus_UAC 4055 28481 IN IP4 67.16.1
10.141..s=SIP Media Capabilities..c=IN IP4 67.16.110.142..t=0 0..m=audio 26
226 RTP/AVP 0 101..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000.
.a=fmtp:101 0-15..a=sendrecv..a=maxptime:20..

U 2010/02/25 18:27:35.971610 66.23.129.253:5060 -> 216.240.61.165:5060
BYE sip:[email protected]:5060 SIP/2.0..Record-Route: ..Via: SIP/2.0/UDP 66.23.129.
253:5060;branch=z9hG4bK9fc3.47e630d4.0..Via: SIP/2.0/UDP 67.16.110.141:5060
;branch=z9hG4bK0eB46d425c9068e5e6a..From: ;tag=gK0e8b8144..To: "13234757710" ;ta
g=8466d269..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU...CSeq: 76
21 BYE..Max-Forwards: 16..Content-Length: 0....

U 2010/02/25 18:27:36.146400 216.240.61.165:5060 -> 66.23.129.253:5060
SIP/2.0 200 OK..Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK9fc3.47e6
30d4.0..Via: SIP/2.0/UDP 67.16.110.141:5060;branch=z9hG4bK0eB46d425c9068e5e
6a..Record-Route: ..Contact: ..To: "13234757710";tag=8466d269..From: ;tag=gK0e8b8144..Call-ID: MDU5Nzk5ZmFiODA4Y2QzNWM5YjFhMDA4ZWEwZDhmODU
...CSeq: 7621 BYE..User-Agent: 3CXPhoneSystem 8.0.10708.0..Content-Length:
0....

When the call is disconnected, the 3CX does send a 200OK to the BYE, so the problem does not appear to be an edge device issue.

Why is the 3CX NOT acking the 200OKs?

Any ideas why this is not working for toll-free numbers?
 
Can you post a 3CX log of a working call for comparison? Just XXX out the area code. 3CX should be sending back a SIP ACK to acknowledgement of receipt of the SIP 200 OK message from the provider. Not sure why it wouldn't do it based on digits dialled.
 
Here is another log comparing a call to my cell phone and a call to 18004633339 (FEDEX). It is DEFINITELY behaving differently when I call an 800 number which really leads me to believe it's a carrier/trunk issue.


13:01:48.554 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:44.566 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:40.562 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:36.564 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:32.579 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:30.577 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:29.575 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:29.084 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 200 OK; from IP:66.23.129.253:5060
13:01:27.678 [CM503020]: Normal call termination. Reason: Terminated
13:01:27.678 [CM503016]: Call(26): Attempt to reach <sip:[email protected]> failed. Reason: Reason Unknown
13:01:27.678 [CM503003]: Call(26): Call to sip:[email protected]:5060 has failed; Cause: 183 Session Progress; from IP:66.23.129.253:5060
13:01:27.566 Active calls counted toward license limit: [26]
13:01:25.708 [CM503025]: Call(26): Calling VoIPline:18004633339@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
13:01:25.471 [CM503004]: Call(26): Route 1: VoIPline:18004633339@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
13:01:25.469 [CM503010]: Making route(s) to <sip:[email protected]>
13:01:25.468 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10373.0] PBX contact: [sip:[email protected]:5060]
13:01:25.466 [CM503001]: Call(26): Incoming call from Ext.101 to <sip:[email protected]>
13:00:56.738 [CM503008]: Call(25): Call is terminated
13:00:55.566 Active calls counted toward license limit: [25]
13:00:50.697 [CM503007]: Call(25): Device joined: sip:[email protected]:5060
13:00:50.696 [CM503007]: Call(25): Device joined: sip:[email protected]:59739;rinstance=b6273188e65c6746
13:00:42.275 [CM505003]: Provider:[Cogent] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
13:00:42.275 [CM503002]: Call(25): Alerting sip:[email protected]:5060
13:00:40.306 [CM503025]: Call(25): Calling VoIPline:1XXX4708722@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
13:00:40.089 [CM503004]: Call(25): Route 1: VoIPline:1XXX4708722@(Ln.10000@Cogent)@[Dev:sip:[email protected]:5060]
13:00:40.088 [CM503010]: Making route(s) to <sip:[email protected]>
13:00:40.086 [CM505001]: Ext.101: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 4.0.10373.0] PBX contact: [sip:[email protected]:5060]
13:00:40.085 [CM503001]: Call(25): Incoming call from Ext.101 to <sip:[email protected]>
 
It sure looks like they are handling the calls differently. The only other thing you could do is to hook up something like Wireshark between your modem and router and again compare the messaging for both of these types of calls. They claim that they were sending the 200 OK messages but received no ACK from you (3CX), this way you will know for sure as it will be on the "outside" of your router. It would give you some "ammo" to go back to them with if it shows you do not receive exactly the same SIP messaging for both a standard LD call and a toll free number call.
 
I'm not sure how I would hookup the wireshark software between my wan and router, but I can put the 3cx box directly on the wan and run wireshark. Do you think this will work?
 
Modem into a Hub (not a switch) then one RJ-45 out to router and one out to second PC running WS. Wireshark will then see all traffic between modem and router
 
Thanks, now I remember! Just need myself a hub since they've almost entirely been phased out. The trunk provider had me do a test using X-lite connected to the trunk directly and it failed to call toll free number so that effectively proves that it is their problem.

Just for everyone's info, the provider is 888voipstore or cogentvoip.com
 
((((UPDATE))))

It turned out to be my Cisco Small Business WRV210 Firewall...utter crap. Other than VPN, the WRT54G is a better device in every way, and it's 5-6 years old.
 
Glad to hear that you found the problem

dannybrook said:
Other than VPN, the WRT54G is a better device in every way
Click to expand...

You mean other than lacking VPN? Are you running the WRT54G with the original firmware or DD-WRT VPN firmware?
 
I'm running a Snapgear SG565 now, but I confirmed the WRV210 was not working with a WRT150N
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,880
Messages
589,533
Members
164,735
Latest member
998742
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom