Can't make Calls to 800 877 or 866 Toll Free Numbers

Discussion in '3CX Phone System - General' started by brian595, Jun 24, 2009.

Thread Status:
Not open for further replies.
  1. brian595

    Joined:
    Jun 22, 2009
    Messages:
    4
    Likes Received:
    0
    I can't make calls to any toll free numbers it appears. I have two different sip trunks. And I can make long distance calls just fine. I've even made some Outbound rules for the 800 numbers. Any ideas? Thanks in adavance.

    Code:
    15:27:09.477  [CM503008]: Call(17): Call is terminated
    
    15:27:09.461  [CM503015]: Call(17): Attempt to reach <sip:18775328829@192.168.20.5> failed. Reason: Not Found
    
    15:27:09.461  [CM503003]: Call(17): Call to sip:+18775328829@4.55.13.163:5060 has failed; Cause: 404 Not Found; from IP:4.79.132.209:5060
    
    15:27:08.524  [CM503016]: Call(17): Target is not registered: VoIPline:18775328829 dialed on (AnyLine@NexVortex Test)
    
    15:27:08.524  [CM303003]: There are no available outbound lines on gateway NexVortex Test at this time.
    
    15:27:08.524  [CM503024]: Call(17): Calling VoIPline:18775328829@(Ln.10000@Sotel)@[Dev:sip:4352284648@termination.sotelips.net:5060]
    
    15:27:08.524  [MS210002] C:17.2:Offer provided. Connection(transcoding mode): 209.33.198.125:9020(9021)
    
    15:27:07.196  [CM503004]: Call(17): Route 1: VoIPline:18775328829@(Ln.10000@Sotel)@[Dev:sip:4352284648@termination.sotelips.net:5060]
    
    15:27:07.180  [MS210000] C:17.1:Offer received. RTP connection: 192.168.20.128:16452(16453)
    
    15:27:07.180  [CM503010]: Making route(s) to <sip:18775328829@192.168.20.5>
    
    15:27:07.164  Remote SDP is set for legC:17.1
    
    15:27:07.164  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA942-6.1.5(a)] Transport: [sip:192.168.20.5:5060]
    
    15:27:07.164  [CM503001]: Call(17): Incoming call from Ext.100 to <sip:18775328829@192.168.20.5>
    
    15:27:07.164  [CM500002]: Info on incoming INVITE:
    
      INVITE sip:18775328829@192.168.20.5 SIP/2.0
    
      Via: SIP/2.0/UDP 192.168.20.128:5060;branch=z9hG4bK-6ca9f538
    
      Max-Forwards: 70
    
      Contact: "100"<sip:100@192.168.20.128:5060>
    
      To: <sip:18775328829@192.168.20.5>
    
      From: "100"<sip:100@192.168.20.5>;tag=d87b8d3e848c1760o0
    
      Call-ID: 8091d116-cfae568@192.168.20.128
    
      CSeq: 102 INVITE
    
      Expires: 240
    
      Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
    
      Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",nonce="414d535c00532b2b12:ad585b9eb8e08864443a5e5090d8a13c",uri="sip:18775328829@192.168.20.5",algorithm=MD5,response="1d304dc9e9f00cf691d0bf98151f8bfb"
    
      Supported: replaces
    
      User-Agent: Linksys/SPA942-6.1.5(a)
    
      Content-Length: 0
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,362
    Likes Received:
    227
    Are you getting :
    15:27:08.524 [CM303003]: There are no available outbound lines on gateway NexVortex Test at this time.

    Every time you attempt a toll free call?

    Do you have that particular trunk group set up to allow more than one call at a time? I also noticed the + in front of the outbound number. Are you placing calls from within North America? if so, does your provider require the international access code before the number. With the +, the next "1" becomes the code for North America not the LD access prefix. What does a working LD call show, do you see the + in the log?
     
  3. brian595

    Joined:
    Jun 22, 2009
    Messages:
    4
    Likes Received:
    0
    I am placing the calls inside North America. Here is a successful long distance call.
    Code:
    11:34:03.712  [CM503008]: Call(28): Call is terminated
    
    11:34:03.696  [CM503008]: Call(28): Call is terminated
    
    11:34:01.337  Session 23366 of leg C:28.1 is confirmed
    
    11:34:01.228  [CM503007]: Call(28): Device joined: sip:4352284648@termination.sotelips.net:5060
    
    11:34:01.228  [CM503007]: Call(28): Device joined: sip:100@192.168.20.128:5060
    
    11:34:01.228  [MS210001] C:28.2:Answer received. RTP connection: 4.55.6.6:11500(11501)
    
    11:34:01.228  Remote SDP is set for legC:28.2
    
    11:34:00.275  [MS210003] C:28.1:Answer provided. Connection(transcoding mode):192.168.20.5:7062(7063)
    
    11:34:00.275  [MS210001] C:28.2:Answer received. RTP connection: 4.55.6.6:11500(11501)
    
    11:34:00.275  Remote SDP is set for legC:28.2
    
    11:34:00.275  [CM505003]: Provider:[Sotel] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.20.5:5060]
    
    11:34:00.275  [CM503002]: Call(28): Alerting sip:4352284648@termination.sotelips.net:5060
    
    11:33:56.696  [CM503016]: Call(28): Target is not registered: VoIPline:18015752400 dialed on (AnyLine@NexVortex Test)
    
    11:33:56.696  [CM303003]: There are no available outbound lines on gateway NexVortex Test at this time.
    
    11:33:56.696  [CM503024]: Call(28): Calling VoIPline:18015752400@(Ln.10000@Sotel)@[Dev:sip:4352284648@termination.sotelips.net:5060]
    
    11:33:56.696  [MS210002] C:28.2:Offer provided. Connection(transcoding mode): 209.33.198.125:9040(9041)
    
    11:33:56.368  [CM503004]: Call(28): Route 1: VoIPline:18015752400@(Ln.10000@Sotel)@[Dev:sip:4352284648@termination.sotelips.net:5060]
    
    11:33:56.337  [MS210000] C:28.1:Offer received. RTP connection: 192.168.20.128:16466(16467)
    
    11:33:56.337  [CM503010]: Making route(s) to <sip:18015752400@192.168.20.5>
    
    11:33:56.337  Remote SDP is set for legC:28.1
    
    11:33:56.337  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA942-6.1.5(a)] Transport: [sip:192.168.20.5:5060]
    
    11:33:56.321  [CM503001]: Call(28): Incoming call from Ext.100 to <sip:18015752400@192.168.20.5>
    
    11:33:56.321  [CM500002]: Info on incoming INVITE:
    
      INVITE sip:18015752400@192.168.20.5 SIP/2.0
    
      Via: SIP/2.0/UDP 192.168.20.128:5060;branch=z9hG4bK-cf84432e
    
      Max-Forwards: 70
    
      Contact: "100"<sip:100@192.168.20.128:5060>
    
      To: <sip:18015752400@192.168.20.5>
    
      From: "100"<sip:100@192.168.20.5>;tag=b86b2db8c95dde6o0
    
      Call-ID: e286dfa0-e8c7951e@192.168.20.128
    
      CSeq: 102 INVITE
    
      Expires: 240
    
      Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
    
      Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",nonce="414d535c0054460476:6a30ec51950fb11f5e11ef8f54cc8bd8",uri="sip:18015752400@192.168.20.5",algorithm=MD5,response="6b3705f4c23ce522d32ee2766735ca19"
    
      Supported: replaces
    
      User-Agent: Linksys/SPA942-6.1.5(a)
    
      Content-Length: 0
    
    
    So it doesn't appear to have the + sign in front of it. Is that not allowing me to make the calls?
     
  4. brian595

    Joined:
    Jun 22, 2009
    Messages:
    4
    Likes Received:
    0
    I tried making a call without the prefix 1 which appears to eliminate the +, but it still doesn't allow the call to go through.

    Code:
    11:57:18.812  [CM503008]: Call(31): Call is terminated
    
    11:57:18.812  [CM503015]: Call(31): Attempt to reach <sip:8775328829@192.168.20.5> failed. Reason: Not Found
    
    11:57:18.812  [CM503003]: Call(31): Call to sip:+18775328829@4.55.13.163:5060 has failed; Cause: 404 Not Found; from IP:4.79.132.209:5060
    
    11:57:17.891  [CM503016]: Call(31): Target is not registered: VoIPline:8775328829 dialed on (AnyLine@NexVortex Test)
    
    11:57:17.891  [CM303003]: There are no available outbound lines on gateway NexVortex Test at this time.
    
    11:57:17.891  [CM503024]: Call(31): Calling VoIPline:8775328829@(Ln.10000@Sotel)@[Dev:sip:4352284648@termination.sotelips.net:5060]
    
    11:57:17.875  [MS210002] C:31.2:Offer provided. Connection(transcoding mode): 209.33.198.125:9046(9047)
    
    11:57:17.422  [CM503004]: Call(31): Route 1: VoIPline:8775328829@(Ln.10000@Sotel)@[Dev:sip:4352284648@termination.sotelips.net:5060]
    
    11:57:17.406  [MS210000] C:31.1:Offer received. RTP connection: 192.168.20.128:16472(16473)
    
    11:57:17.406  [CM503010]: Making route(s) to <sip:8775328829@192.168.20.5>
    
    11:57:17.406  Remote SDP is set for legC:31.1
    
    11:57:17.391  [CM505001]: Ext.100: Device info: Device Identified: [Man: Linksys;Mod: SPA Series;Rev: General] Capabilities:[reinvite, no-replaces, able-no-sdp, recvonly] UserAgent: [Linksys/SPA942-6.1.5(a)] Transport: [sip:192.168.20.5:5060]
    
    11:57:17.391  [CM503001]: Call(31): Incoming call from Ext.100 to <sip:8775328829@192.168.20.5>
    
    11:57:17.391  [CM500002]: Info on incoming INVITE:
    
      INVITE sip:8775328829@192.168.20.5 SIP/2.0
    
      Via: SIP/2.0/UDP 192.168.20.128:5060;branch=z9hG4bK-4efedd23
    
      Max-Forwards: 70
    
      Contact: "100"<sip:100@192.168.20.128:5060>
    
      To: <sip:8775328829@192.168.20.5>
    
      From: "100"<sip:100@192.168.20.5>;tag=307dec22838145cfo0
    
      Call-ID: 215c2cde-b03b9c43@192.168.20.128
    
      CSeq: 102 INVITE
    
      Expires: 240
    
      Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
    
      Proxy-Authorization: Digest username="100",realm="3CXPhoneSystem",nonce="414d535c00544b7d06:714febdad53c4df31d6c8367b31a9974",uri="sip:8775328829@192.168.20.5",algorithm=MD5,response="94bc47405e1b2f95c0349c5bf79cdc0f"
    
      Supported: replaces
    
      User-Agent: Linksys/SPA942-6.1.5(a)
    
      Content-Length: 0
    
      
    
    
     
  5. brian595

    Joined:
    Jun 22, 2009
    Messages:
    4
    Likes Received:
    0
    It appears it was a problem with the Sip Trunk :roll: . I got a new DID number from them and everything works. Thanks for your help.
     
  6. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,362
    Likes Received:
    227
    When you get messages like the "no trunks available" you have to start thinking that it just might be your provider, glad you got it resolved.
     
Thread Status:
Not open for further replies.