Can't recieve nor make calls

Discussion in '3CX Phone System - General' started by Turbo123, Sep 6, 2011.

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

    Joined:
    Sep 6, 2011
    Messages:
    3
    Likes Received:
    0
    Hello, I am new to this whole SIP/PBX thing and hope I can get some help here. Here is my information,

    I just got my service from Via Talk and CAN connect/call/receive through a SIP Phone (X-Lite) just fine. I am running the 3cx system on a dedicated server I own, The firewall is OFF and the router is a linksys, I have forwarded all the ports needed (I run game servers/voips off of the box as well) so I know it is set correctly. I have provisioned my Polycom 501 (SoundPoint IP 501) with PBX and they ARE connected.

    3cx shows that my Trunk is Registered(idle) & my extensions shows up Registered(idle) and when I call voicemail even though it's not connected to my Via Talk Voicemail for some reason? I do see it go yellow and say "Connected" in 3cx.

    My problem is that I cannot make calls nor receive them, If say I call out it says "Called Number Does Not Exist" (I set something up in 3cx so it says an error and doesn't just give me a busy signal like it was going)

    Error Log for calling out:

    18:52:06.633 [CM503008]: Call(7): Call is terminated
    18:52:01.428 [CM503007]: Call(7): Device joined: sip:EndCall@127.0.0.1:40600;rinstance=2a252158b4e19f26
    18:52:01.424 [CM503007]: Call(7): Device joined: sip:123@192.168.1.104:5060
    18:52:01.419 [CM503002]: Call(7): Alerting sip:EndCall@127.0.0.1:40600;rinstance=2a252158b4e19f26
    18:52:01.271 [CM503025]: Call(7): Calling Unknown:Ext.EndCall@[Dev:sip:EndCall@127.0.0.1:40600;rinstance=2a252158b4e19f26]
    18:52:01.227 [CM503016]: Call(7): Attempt to reach <sip:phone-number@192.168.1.103;user=phone> failed. Reason: Not Found
    18:52:01.227 [CM503014]: Call(7): No known route to target: <sip:phone-number@192.168.1.103;user=phone>
    18:52:01.226 [CM503010]: Making route(s) to <sip:phone-number@192.168.1.103;user=phone>
    18:52:01.225 [CM505001]: Ext.123: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_501-UA/3.1.7.0134] PBX contact: [sip:123@192.168.1.103:5060]
    18:52:01.220 [CM503001]: Call(7): Incoming call from Ext.123 to <sip:phone-number@192.168.1.103;user=phone>
    18:51:35.898 [CM503008]: Call(6): Call is terminated
    18:51:30.691 [CM503007]: Call(6): Device joined: sip:EndCall@127.0.0.1:40600;rinstance=2a252158b4e19f26
    18:51:30.690 [CM503007]: Call(6): Device joined: sip:123@192.168.1.104:5060
    18:51:30.685 [CM503002]: Call(6): Alerting sip:EndCall@127.0.0.1:40600;rinstance=2a252158b4e19f26
    18:51:30.537 [CM503025]: Call(6): Calling Unknown:Ext.EndCall@[Dev:sip:EndCall@127.0.0.1:40600;rinstance=2a252158b4e19f26]
    18:51:30.492 [CM503016]: Call(6): Attempt to reach <sip:phone-number@192.168.1.103;user=phone> failed. Reason: Not Found
    18:51:30.491 [CM503014]: Call(6): No known route to target: <sip:phone-number@192.168.1.103;user=phone>
    18:51:30.490 [CM503010]: Making route(s) to <sip:phone-number@192.168.1.103;user=phone>
    18:51:30.487 [CM503001]: Call(6): Incoming call from Ext.123 to <sip:phone-number@192.168.1.103;user=phone>

    (Phone-number i put in of course so no one calls my home line) :)

    But i have called both local and US LD and this happens every time... From what I read it could be my Outbound Rules so here is my Outbound Rules,

    [​IMG]

    Now I have one for LD as well but i just need to know why my local calls are not working and then i am sure LD will be fixed. Also 719 is my local area code.

    I don't have a Gateway setup, No Digital Receptionist, No Bridges, No Inbound Rules, & No DiD's? I have no idea if any of these could be the problem.


    Firewall stuff,

    I have 5060 (UDP/TCP),5090 (UDP/TCP), & Port Triggering Forwarding of 900-9040 (UDP/TCP) forwarded in my router

    Firewall Checker:

    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <19:02:31>: Phase 1, checking servers connection, please wait...
    <19:02:31>: Stun Checker service is reachable. Phase 1 check passed.
    <19:02:31>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <19:02:31>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <19:02:31>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <19:02:31>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <19:02:31>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <19:02:31>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 5091::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <19:02:31>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <19:02:36>: UDP RTP Port 9000. Response received WITH TRANSLATION 9050::9000. Phase 4-01 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9001. Response received WITH TRANSLATION 9051::9001. Phase 4-02 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9002. Response received WITH TRANSLATION 9052::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9003. Response received WITH TRANSLATION 9053::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9004. Response received WITH TRANSLATION 9054::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9005. Response received WITH TRANSLATION 9055::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9006. Response received WITH TRANSLATION 9056::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9007. Response received WITH TRANSLATION 9057::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9008. Response received WITH TRANSLATION 9058::9008. Phase 4-09 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9009. Response received WITH TRANSLATION 9059::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9010. Response received WITH TRANSLATION 9060::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9011. Response received WITH TRANSLATION 9061::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9012. Response received WITH TRANSLATION 9062::9012. Phase 4-13 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9013. Response received WITH TRANSLATION 9063::9013. Phase 4-14 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9014. Response received WITH TRANSLATION 9064::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9015. Response received WITH TRANSLATION 9065::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9016. Response received WITH TRANSLATION 9066::9016. Phase 4-17 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9017. Response received WITH TRANSLATION 9067::9017. Phase 4-18 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9018. Response received WITH TRANSLATION 9068::9018. Phase 4-19 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9019. Response received WITH TRANSLATION 9069::9019. Phase 4-20 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9020. Response received WITH TRANSLATION 9070::9020. Phase 4-21 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9021. Response received WITH TRANSLATION 9071::9021. Phase 4-22 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9022. Response received WITH TRANSLATION 9072::9022. Phase 4-23 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9023. Response received WITH TRANSLATION 9073::9023. Phase 4-24 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9024. Response received WITH TRANSLATION 9074::9024. Phase 4-25 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9025. Response received WITH TRANSLATION 9075::9025. Phase 4-26 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9026. Response received WITH TRANSLATION 9076::9026. Phase 4-27 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9027. Response received WITH TRANSLATION 9077::9027. Phase 4-28 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9028. Response received WITH TRANSLATION 9078::9028. Phase 4-29 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9029. Response received WITH TRANSLATION 9079::9029. Phase 4-30 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9030. Response received WITH TRANSLATION 9080::9030. Phase 4-31 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9031. Response received WITH TRANSLATION 9081::9031. Phase 4-32 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9032. Response received WITH TRANSLATION 9082::9032. Phase 4-33 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9033. Response received WITH TRANSLATION 9083::9033. Phase 4-34 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9034. Response received WITH TRANSLATION 9084::9034. Phase 4-35 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9035. Response received WITH TRANSLATION 9085::9035. Phase 4-36 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9036. Response received WITH TRANSLATION 9086::9036. Phase 4-37 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9037. Response received WITH TRANSLATION 9087::9037. Phase 4-38 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9038. Response received WITH TRANSLATION 9088::9038. Phase 4-39 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9039. Response received WITH TRANSLATION 9089::9039. Phase 4-40 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9040. Response received WITH TRANSLATION 9090::9040. Phase 4-41 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9041. Response received WITH TRANSLATION 9091::9041. Phase 4-42 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9042. Response received WITH TRANSLATION 9092::9042. Phase 4-43 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9043. Response received WITH TRANSLATION 9093::9043. Phase 4-44 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9044. Response received WITH TRANSLATION 9094::9044. Phase 4-45 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9045. Response received WITH TRANSLATION 9095::9045. Phase 4-46 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9046. Response received WITH TRANSLATION 9096::9046. Phase 4-47 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9047. Response received WITH TRANSLATION 9097::9047. Phase 4-48 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9048. Response received WITH TRANSLATION 9098::9048. Phase 4-49 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <19:02:36>: UDP RTP Port 9049. Response received WITH TRANSLATION 9099::9049. Phase 4-50 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    Thanks for any help any of you can give me!

    EDIT: Totally forgot when someone calls me it says the person at this extension isn't available and automatically sends them to my voicemail and yes i am set as available in 3cx/my personal phone.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    First off, I would be concerned about the port translations your router is doing, that may be why you are not getting any calls. Do incoming calls even show in the 3CX log? If not, then it's probably your router/firewall or the settings in one or the other.

    As far as your outgoing calls, it's probably your outbound rule. You are trying to dial numbers as 7 digits but you are stripping off 3, then pre-pending with an area code, so....you are only sending a 7 digit number out to your provider. 719XXXX

    Be sure that your provider wants only 10 digit numbers and no prefix, as well.
     
  3. Turbo123

    Joined:
    Sep 6, 2011
    Messages:
    3
    Likes Received:
    0
    Ok well I see what you mean... (I will be getting a new router soon)

    But the outbound I have tried EVERYTHING for... I mean... LITERALLY EVERYTHING KNOWN TO MAN... I have tried no pre-prend, No stripping in fact nothing at all. Then changed it up. So can you tell me if I wanted to call a local number (719) what would I do?
     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    First, be sure of the format that your provider wants. Do they want 1719xxxxxxx? or 719XXXXXXX or something else?

    If you just want to dial 7 digits for local calls and they don't require a 1 first, then by setting Strip Digits to 0, should work. the logs will confirm the number you are sending. If they require a 1 in front, then still strip 0, but put 1719 in the Prepend. Again, check the logs to confirm the number actually sent out.
     
  5. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Add extension 123 to MANAGEMENT group.
    Question about log:
    <sip:phone-number@192.168.1.103;user=phone>
    How many digits in phone-number?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Turbo123

    Joined:
    Sep 6, 2011
    Messages:
    3
    Likes Received:
    0
    I contacted Via Talk and they said that they don't require 1719 nor 719 when calling locally, I have then set it up the way you said and (please read below)

    I have now added 123 to MANAGEMENT and the phone-number is 7 digits.


    Now I don't know which one changed my calling message/my error message but i did what you both asked (THANK YOU SO MUCH we are getting closer i think!)

    And now the phone says "Canceled" when i call a local number. (my home) Now the "1's" are my actual business line and the 0's are my home phone in the log below. This is a different error now so hopefully we are getting closer. Again thank you both!

    15:22:10.204 [CM503008]: Call(11): Call is terminated
    15:22:06.791 [CM503007]: Call(11): Device joined: sip:EndCall@127.0.0.1:40600;rinstance=c989272ef81fb8ef
    15:22:06.789 [CM503007]: Call(11): Device joined: sip:123@192.168.1.100:5060
    15:22:06.784 [CM503002]: Call(11): Alerting sip:EndCall@127.0.0.1:40600;rinstance=c989272ef81fb8ef
    15:22:06.637 [CM503025]: Call(11): Calling Unknown:Ext.EndCall@[Dev:sip:EndCall@127.0.0.1:40600;rinstance=c989272ef81fb8ef]
    15:22:06.581 [CM503016]: Call(11): Attempt to reach <sip:0000000@192.168.1.103;user=phone> failed. Reason: Not Acceptable HereReason Unknown
    15:22:06.579 [CM503003]: Call(11): Call to sip:0000000@grimlock.vtnoc.net:5060 has failed; Cause: 407 Proxy Authentication Required; warning: Noisy feedback tells: pid=20263 req_src_ip=71.196.212.4 req_src_port=5061 in_uri=sip:0000000@grimlock.vtnoc.net:5060 out_uri=sip:0000000@grimlock.vtnoc.net:5060 via_cnt==1; from IP:174.133.67.154:5060
    15:22:03.627 [CM503025]: Call(11): Calling VoIPline:00000002@(Ln.10000@Via Talk)@[Dev:sip:11111111111@grimlock.vtnoc.net:5060]
    15:22:03.479 [CM503004]: Call(11): Route 1: VoIPline:0000000@(Ln.10000@Via Talk)@[Dev:sip:11111111111@grimlock.vtnoc.net:5060]
    15:22:03.478 [CM503010]: Making route(s) to <sip:0000000@192.168.1.103;user=phone>
    15:22:03.477 [CM505001]: Ext.123: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_501-UA/3.1.7.0134] PBX contact: [sip:123@192.168.1.103:5060]
    15:22:03.472 [CM503001]: Call(11): Incoming call from Ext.123 to <sip:0000000@192.168.1.103;user=phone>
    15:21:54.971 [CM503008]: Call(10): Call is terminated
    15:21:51.564 [CM503007]: Call(10): Device joined: sip:EndCall@127.0.0.1:40600;rinstance=c989272ef81fb8ef
    15:21:51.562 [CM503007]: Call(10): Device joined: sip:123@192.168.1.100:5060
    15:21:51.557 [CM503002]: Call(10): Alerting sip:EndCall@127.0.0.1:40600;rinstance=c989272ef81fb8ef
    15:21:51.410 [CM503025]: Call(10): Calling Unknown:Ext.EndCall@[Dev:sip:EndCall@127.0.0.1:40600;rinstance=c989272ef81fb8ef]
    15:21:51.355 [CM503016]: Call(10): Attempt to reach <sip:0000000@192.168.1.103;user=phone> failed. Reason: Not Acceptable HereReason Unknown
    15:21:51.352 [CM503003]: Call(10): Call to sip:0000000@grimlock.vtnoc.net:5060 has failed; Cause: 407 Proxy Authentication Required; warning: Noisy feedback tells: pid=20264 req_src_ip=71.196.212.4 req_src_port=5061 in_uri=sip:0000000@grimlock.vtnoc.net:5060 out_uri=sip:0000000@grimlock.vtnoc.net:5060 via_cnt==1; from IP:174.133.67.154:5060
    15:21:50.977 [CM503025]: Call(10): Calling VoIPline:0000000@(Ln.10000@Via Talk)@[Dev:sip:11111111111@grimlock.vtnoc.net:5060]
    15:21:50.843 [CM503004]: Call(10): Route 1: VoIPline:0000000@(Ln.10000@Via Talk)@[Dev:sip:11111111111@grimlock.vtnoc.net:5060]
    15:21:50.842 [CM503010]: Making route(s) to <sip:0000000@192.168.1.103;user=phone>
    15:21:50.839 [CM503001]: Call(10): Incoming call from Ext.123 to <sip:0000000@192.168.1.103;user=phone>

    EDIT: Also my Long Distant calls say the Area Code is "860" if i dial say "860-000-0000" it will say "Canceled" as well, And if i put a 1 it gives the original error message. "This line does not exist".

    and for my outbound Local Calls rule i have everything the same except 0 strip digits and no prepend.
     
  7. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,749
    Likes Received:
    285
    Looks like some of your setting are still not what your provider wants.
     
  8. Pablooo

    Joined:
    Oct 5, 2011
    Messages:
    16
    Likes Received:
    0
    Hi Folks,

    Today I was earlier for a meeting and I needed to call my office so I tried with my 3CX Phone on my lap.
    I started but the phone didn´t connect, I got into accounts/manage SIP and selected my extension (the only extension configured in my lap), I specified "out of office" and press OK.. I tried several ways to get the phone started but nothing works. Couple of weeks ago I use my phone-lap to call the office from home without any trouble.
    This is the log

    14:25:46.925|.\StunClient.cpp(356)|Log2|STUN|StunClient::eek:nInitTests:[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>
    14:25:50.026|.\StunClient.cpp(411)|Log2|STUN|StunClient::eek:nTestTout:[CM506004]: STUN request to STUN server 96.9.132.83:3478 has timed out; used Transport: [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>
    14:41:35.516|.\Authorization.cpp(180)|Critical0|Authorization|AuthMgr::eek:nAuthFailure:[CM102001]: Authentication failed for SipReq: REGISTER 187.162.29.222:5060 tid=4b1c5058753abb51 cseq=REGISTER contact=101@189.178.45.37:54630 / 2 from(wire); Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings<br>
    14:45:46.996|.\StunClient.cpp(356)|Log2|STUN|StunClient::eek:nInitTests:[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>
    15:05:47.871|.\StunClient.cpp(356)|Log2|STUN|StunClient::eek:nInitTests:[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>
    15:25:47.929|.\StunClient.cpp(356)|Log2|STUN|StunClient::eek:nInitTests:[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>
    15:45:48.006|.\StunClient.cpp(356)|Log2|STUN|StunClient::eek:nInitTests:[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>
    16:05:48.805|.\StunClient.cpp(356)|Log2|STUN|StunClient::eek:nInitTests:[CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server [ V4 96.9.132.83:3478 UDP target domain=unspecified mFlowKey=0 ] over Transport [ V4 192.168.0.100:5060 UDP target domain=unspecified mFlowKey=0 ]<br>

    hope you can help me to find out what can I do.
    Thanks,

    Pablo
     
  9. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Please check extension configuration. If extension is mobile and may be used from outside of the LAN then you need to allow it explicitly by removing tick from "Disallow use of extension outside the LAN"
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.