Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Sipgate Setup Problem

Discussion in '3CX Phone System - General' started by adi_2007, Nov 28, 2010.

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

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    Hi All,

    New to this and just trying to find my way round. iv managed to get the extensions working. But i can't seem to get my sipgate account working on 3cx.

    I have added sipgate through the Add VOIP provider wizard and once it was set up nothing worked even though the Ports/Trunks Status said registered.

    I then looked at ports being closed and took ny firewall down and tried again, still nothing.

    I have tried the firewall checker and it tells me there are a few problems, but im having trouble understanding what its trying to tell me.

    This is a copy of the results, can anyone guide me?

    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
    <22:06:07>: Phase 1, checking servers connection, please wait...
    <22:06:07>: Stun Checker service is reachable. Phase 1 check passed.
    <22:06:07>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <22:06:07>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 51236::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/
    <22:06:07>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <22:06:07>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 51236::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/
    <22:06:07>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <22:06:07>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 51237::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/
    <22:06:07>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <22:06:14>: UDP RTP Port 9000. Response received WITH TRANSLATION 51238::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/
    <22:06:14>: UDP RTP Port 9001. Response received WITH TRANSLATION 51239::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/
    <22:06:14>: UDP RTP Port 9002. Response received WITH TRANSLATION 51240::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/
    <22:06:14>: UDP RTP Port 9003. Response received WITH TRANSLATION 51241::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/
    <22:06:14>: UDP RTP Port 9004. Response received WITH TRANSLATION 51242::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/
    <22:06:14>: UDP RTP Port 9005. Response received WITH TRANSLATION 51243::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/
    <22:06:14>: UDP RTP Port 9006. Response received WITH TRANSLATION 51244::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/
    <22:06:14>: UDP RTP Port 9007. Response received WITH TRANSLATION 51245::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/
    <22:06:14>: UDP RTP Port 9008. Response received WITH TRANSLATION 51246::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/
    <22:06:14>: UDP RTP Port 9009. Response received WITH TRANSLATION 51247::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/
    <22:06:14>: UDP RTP Port 9010. Response received WITH TRANSLATION 51248::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/
    <22:06:14>: UDP RTP Port 9011. Response received WITH TRANSLATION 51249::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/
    <22:06:14>: UDP RTP Port 9012. Response received WITH TRANSLATION 51250::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/
    <22:06:14>: UDP RTP Port 9013. Response received WITH TRANSLATION 51251::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/
    <22:06:14>: UDP RTP Port 9014. Response received WITH TRANSLATION 51252::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/
    <22:06:14>: UDP RTP Port 9015. Response received WITH TRANSLATION 51253::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/
    <22:06:14>: UDP RTP Port 9016. Response received WITH TRANSLATION 51254::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/
    <22:06:14>: UDP RTP Port 9017. Response received WITH TRANSLATION 51255::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/
    <22:06:14>: UDP RTP Port 9018. Response received WITH TRANSLATION 51256::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/
    <22:06:14>: UDP RTP Port 9019. Response received WITH TRANSLATION 51257::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/
    <22:06:14>: UDP RTP Port 9020. Response received WITH TRANSLATION 51258::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/
    <22:06:14>: UDP RTP Port 9021. Response received WITH TRANSLATION 51259::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/
    <22:06:14>: UDP RTP Port 9022. Response received WITH TRANSLATION 51260::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/
    <22:06:14>: UDP RTP Port 9023. Response received WITH TRANSLATION 51261::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/
    <22:06:14>: UDP RTP Port 9024. Response received WITH TRANSLATION 51262::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/
    <22:06:14>: UDP RTP Port 9025. Response received WITH TRANSLATION 51263::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/
    <22:06:14>: UDP RTP Port 9026. Response received WITH TRANSLATION 51264::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/
    <22:06:14>: UDP RTP Port 9027. Response received WITH TRANSLATION 51265::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/
    <22:06:14>: UDP RTP Port 9028. Response received WITH TRANSLATION 51266::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/
    <22:06:14>: UDP RTP Port 9029. Response received WITH TRANSLATION 51267::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/
    <22:06:14>: UDP RTP Port 9030. Response received WITH TRANSLATION 51268::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/
    <22:06:14>: UDP RTP Port 9031. Response received WITH TRANSLATION 51269::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/
    <22:06:14>: UDP RTP Port 9032. Response received WITH TRANSLATION 51270::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/
    <22:06:14>: UDP RTP Port 9033. Response received WITH TRANSLATION 51271::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/
    <22:06:14>: UDP RTP Port 9034. Response received WITH TRANSLATION 51272::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/
    <22:06:14>: UDP RTP Port 9035. Response received WITH TRANSLATION 51273::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/
    <22:06:14>: UDP RTP Port 9036. Response received WITH TRANSLATION 51274::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/
    <22:06:14>: UDP RTP Port 9037. Response received WITH TRANSLATION 51275::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/
    <22:06:14>: UDP RTP Port 9038. Response received WITH TRANSLATION 51276::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/
    <22:06:14>: UDP RTP Port 9039. Response received WITH TRANSLATION 51277::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/
    <22:06:14>: UDP RTP Port 9040. Response received WITH TRANSLATION 51278::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/
    <22:06:14>: UDP RTP Port 9041. Response received WITH TRANSLATION 51279::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/
    <22:06:14>: UDP RTP Port 9042. Response received WITH TRANSLATION 51280::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/
    <22:06:14>: UDP RTP Port 9043. Response received WITH TRANSLATION 51281::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/
    <22:06:14>: UDP RTP Port 9044. Response received WITH TRANSLATION 51282::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/
    <22:06:14>: UDP RTP Port 9045. Response received WITH TRANSLATION 51283::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/
    <22:06:14>: UDP RTP Port 9046. Response received WITH TRANSLATION 51284::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/
    <22:06:14>: UDP RTP Port 9047. Response received WITH TRANSLATION 51285::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/
    <22:06:14>: UDP RTP Port 9048. Response received WITH TRANSLATION 51286::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/
    <22:06:14>: UDP RTP Port 9049. Response received WITH TRANSLATION 51287::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/

    Application exit code is 53
     
  2. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    Hi, What router are you using? and do you have a firewall on both the Router and PC - which is running 3CX?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    By the looks of things you did no portforwarding on your firewall ort if you have a complex router like sonicwall you might not have done it properly.

    please ensure there ports have been portforwarded:

    5060
    5090
    9000-9050
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. adi_2007

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    Hi mfm,

    thanks for your reply...
    Your going to groan and grumble at me for this, But im on a BT Home Hub and i have read tonight that BT tend to block port 5060. I read this post http://forums.thinkbroadband.com/voip/3755133-link-fritzbox-to-bt-home-hub.html

    Is there a way of using other ports?
     
  5. adi_2007

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    Hi David,

    I am using a BT Home Hub firewall...not the best i know!. The PC that runs 3CX does not have a firewall on it.
     
  6. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    Hi, I’ve sent you a private message
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    BThome hub?? hmm well the ideal thing is to change the PBX port from the network settings. Or you might want to change your router. I see issues in your near future with a router such as that!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    I have provided adi_2007 with remote desktop support, I have reinstalled 3CX to out rule any issues with the installation.
    Firewall at pc and router been disabled.

    Tryed with and without Stun enabled. But still same result
    I have suggested that he replaces his router and test again and report back here
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    Glad to see you help him out, it is necessary for him to have a router that doesnt play silly games like block PBX ports..
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. adi_2007

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    Hi Chaps,

    Quick update for you...

    Yes the BT Home Hub Router is blocking ports for the BT Talk service, I changed the router for a little old Netgear DG834G i had kicking about and it worked straight away.

    So thanks to davidbenwell I’m almost up and working.

    I’m still getting a few problems: :roll:
    1, Can receive calls but cannot make calls
    2, Can’t add call queue's (possibly because i only have 1 line?)
    3, Some System Extensions are not registered
    4, Digital Receptionist > Call by name (does not work)

    But other then them small snags, all good!
     
  11. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    Hi, pleased its now working. :p

    when you try to make calls what happens? can you try again and post logs here?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. adi_2007

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    Hi David,

    I did a little test, just something that ran through my head, dont know why but i tried it.

    if i dial (01522) 123456 (example phone number) it wont connect but if i dial 000(01522)123456 it works.....

    must be a setting somewhere.... any ideas?

    Adam
     
  13. swim

    Joined:
    Sep 23, 2008
    Messages:
    26
    Likes Received:
    0
    are you stripping digits in your outgoing rules?
     
  14. adi_2007

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    Hi swim,

    Strip Digits is set to 3 which makes sense, if i select 0 will that effect anything?
     
  15. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    HI,

    Please paste the screenshot of your outbound rules, also not being able to add queues should work if you dont have anything connected.. it sounds like your on the free edition.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    Yes he is using the Free Edition
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. adi_2007

    Joined:
    Nov 28, 2010
    Messages:
    7
    Likes Received:
    0
    The outbound call rule is no issue to me now i know to put 000 infront of the phone number. But the call que is, but i am using the free version to get my business up and running, its a shame the call que is not active in the free version as i do have upto 15 calls at anyone time on my 0845 number.

    But i will have to wait till i buy the full version.
     
  18. davidbenwell

    davidbenwell Active Member

    Joined:
    Apr 27, 2010
    Messages:
    704
    Likes Received:
    0
    on the outbound rule, you ony need 0

    this will then route all outoging calls as normal, any probs, give me a call and ill log in and set it up for you.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.