3cx V9 Cannot connect to Trunk

Discussion in '3CX Phone System - General' started by webby, Jun 30, 2012.

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

    Joined:
    Oct 20, 2009
    Messages:
    25
    Likes Received:
    0
    I have a 3CX machine running perfectly for my business phones.
    For redundancy and incase of faliure I recently decided it was a good idea to set up a virtual machine to run when any problems arose.

    To do this I set up a fresh VirtualBox
    Installed Windows XP Pro SP3
    Installed 3CX V9 the same version that is running on my currently working phone system machine.
    Backed up my settings from 3CX
    Powered down the original machine
    Powered up the Virtual machine
    Restored the 3CX settings from my other machine
    Changed the IP address to the same fixed IP address of the original machine

    All my local network phones will call eachother and all register fine
    But my VoIP Trunk / Line / Port what ever you want to call it will not register. It just says Request timed out.
    I ran the firewall checker and it came back with

    "Application exit code 1"

    I presume my fire wall is correct as I already have a fully working system that I have been using for 2 years.
    I am presuming the problem lies with my VirtualBox some how.

    The virtual box is set to "Network Bridge mode" so it appears as a computer on my network in it own right.
    The IP address is the same as the original machine
    The original machine is powered off so is not affecting it.
    I have a dedicated BroadBand connection for the phone system and ONLY the phone computer goes out over it.
    The VIrtualBox External IP is the Fixed IP addresss of that BroadBand
    3CX have the fixed IP address stored and STUN turned OFF.

    Anyone have any ideas or experience?
    Thanks In advance
     
  2. jpillow

    jpillow Well-Known Member

    Joined:
    Jun 20, 2011
    Messages:
    1,342
    Likes Received:
    0
    what does the server log say when you attempt to register VoIP provider other than time out? any other errors? please post the logs in your next post.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. webby

    Joined:
    Oct 20, 2009
    Messages:
    25
    Likes Received:
    0
    Sorry for delay in reply, been so busy with other stuff at work only now got back to this problem.
    Here is the log of my trunk trying to connect: (Actually it's 3 trunks)


    19:18:00.079 Connection error Timeout while contacting DNS servers for _sip._udp.sip.voip-unlimited.net
    19:17:47.036 Connection error Timeout while contacting DNS servers for _sip._udp.sip.voip-unlimited.net
    19:17:35.049 Connection error Timeout while contacting DNS servers for _sip._udp.sip.voip-unlimited.net
    19:17:18.160 [CM504008]: Fax Service: registered as sip:88@192.168.2.33:5060 with contact sip:88@192.168.2.33:5100;user=phone
    19:17:17.972 [CM504003]: Sent registration request for 10003@Voip Umlinited 2
    19:17:00.675 [CM504003]: Sent registration request for 10002@71710
    19:16:45.721 [CM504003]: Sent registration request for 10004@Test
    19:16:33.977 [EC100007]: External application is connected: application:xp-template:0/QueueManager local:127.0.0.1:5482 remote:127.0.0.1:1049
    19:16:32.722 [CM504003]: Sent registration request for 10002@71710
    19:16:21.069 [EC200004]: IVR server is connected: application:xp-template:0/IVRServer local:127.0.0.1:5482 remote:127.0.0.1:1047
    19:16:21.052 [EC200005]: Parking Orbit server is connected: application:xp-template:0/3CXParkOrbit local:127.0.0.1:5482 remote:127.0.0.1:1046
    19:16:21.035 [EC200002]: Media server is connected: application:xp-template:0/MediaServer local:127.0.0.1:5482 remote:127.0.0.1:1043
    19:16:20.844 [EC200006]: Conference server is connected: application:xp-template:0/3CXConferenceRoom local:127.0.0.1:5482 remote:127.0.0.1:1041
    19:16:20.429 [CM504003]: Sent registration request for 10003@Voip Umlinited 2
    19:16:06.133 IP(s) added:[192.168.2.33]
    19:15:18.809 [CM506005]: Public IP=91.151.12.214 is used for WAN communications through local interface with IP=192.168.2.33
     
  4. webby

    Joined:
    Oct 20, 2009
    Messages:
    25
    Likes Received:
    0
    I have done a fire wall check.
    Here are the results

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

    <19:22:22>: Phase 1, checking servers connection, please wait...
    <19:22:22>: Stun Checker service is reachable. Phase 1 check passed.
    <19:22:22>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <19:22:22>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 44228::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:22:22>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <19:22:23>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 44228::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:22:23>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <19:22:23>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 33192::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:22:23>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <19:22:30>: UDP RTP Port 9000. Response received WITH TRANSLATION 33193::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:22:30>: UDP RTP Port 9001. Response received WITH TRANSLATION 33194::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:22:30>: UDP RTP Port 9002. Response received WITH TRANSLATION 33195::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:22:30>: UDP RTP Port 9003. Response received WITH TRANSLATION 33196::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:22:30>: UDP RTP Port 9004. Response received WITH TRANSLATION 33197::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:22:30>: UDP RTP Port 9005. Response received WITH TRANSLATION 33198::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:22:30>: UDP RTP Port 9006. Response received WITH TRANSLATION 33199::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:22:30>: UDP RTP Port 9007. Response received WITH TRANSLATION 33200::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:22:30>: UDP RTP Port 9008. Response received WITH TRANSLATION 33201::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:22:30>: UDP RTP Port 9009. Response received WITH TRANSLATION 33202::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:22:30>: UDP RTP Port 9010. Response received WITH TRANSLATION 33203::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:22:30>: UDP RTP Port 9011. Response received WITH TRANSLATION 33204::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:22:30>: UDP RTP Port 9012. Response received WITH TRANSLATION 33205::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:22:30>: UDP RTP Port 9013. Response received WITH TRANSLATION 33206::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:22:30>: UDP RTP Port 9014. Response received WITH TRANSLATION 33207::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:22:30>: UDP RTP Port 9015. Response received WITH TRANSLATION 33208::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:22:30>: UDP RTP Port 9016. Response received WITH TRANSLATION 33209::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:22:30>: UDP RTP Port 9017. Response received WITH TRANSLATION 33210::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:22:30>: UDP RTP Port 9018. Response received WITH TRANSLATION 33211::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:22:30>: UDP RTP Port 9019. Response received WITH TRANSLATION 33212::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:22:30>: UDP RTP Port 9020. Response received WITH TRANSLATION 33213::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:22:30>: UDP RTP Port 9021. Response received WITH TRANSLATION 33214::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:22:30>: UDP RTP Port 9022. Response received WITH TRANSLATION 33215::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:22:30>: UDP RTP Port 9023. Response received WITH TRANSLATION 33216::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:22:30>: UDP RTP Port 9024. Response received WITH TRANSLATION 33217::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:22:30>: UDP RTP Port 9025. Response received WITH TRANSLATION 33218::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:22:30>: UDP RTP Port 9026. Response received WITH TRANSLATION 33219::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:22:30>: UDP RTP Port 9027. Response received WITH TRANSLATION 33220::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:22:30>: UDP RTP Port 9028. Response received WITH TRANSLATION 33221::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:22:30>: UDP RTP Port 9029. Response received WITH TRANSLATION 33222::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:22:30>: UDP RTP Port 9030. Response received WITH TRANSLATION 33223::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:22:30>: UDP RTP Port 9031. Response received WITH TRANSLATION 33224::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:22:30>: UDP RTP Port 9032. Response received WITH TRANSLATION 33225::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:22:30>: UDP RTP Port 9033. Response received WITH TRANSLATION 33226::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:22:30>: UDP RTP Port 9034. Response received WITH TRANSLATION 33227::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:22:30>: UDP RTP Port 9035. Response received WITH TRANSLATION 33228::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:22:30>: UDP RTP Port 9036. Response received WITH TRANSLATION 33229::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:22:30>: UDP RTP Port 9037. Response received WITH TRANSLATION 33230::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:22:30>: UDP RTP Port 9038. Response received WITH TRANSLATION 33231::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:22:30>: UDP RTP Port 9039. Response received WITH TRANSLATION 33232::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:22:30>: UDP RTP Port 9040. Response received WITH TRANSLATION 33233::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:22:30>: UDP RTP Port 9041. Response received WITH TRANSLATION 33234::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:22:30>: UDP RTP Port 9042. Response received WITH TRANSLATION 33235::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:22:30>: UDP RTP Port 9043. Response received WITH TRANSLATION 33236::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:22:30>: UDP RTP Port 9044. Response received WITH TRANSLATION 33237::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:22:30>: UDP RTP Port 9045. Response received WITH TRANSLATION 33238::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:22:30>: UDP RTP Port 9046. Response received WITH TRANSLATION 33239::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:22:30>: UDP RTP Port 9047. Response received WITH TRANSLATION 33240::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:22:30>: UDP RTP Port 9048. Response received WITH TRANSLATION 33241::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:22:30>: UDP RTP Port 9049. Response received WITH TRANSLATION 33242::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
     
  5. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,321
    Likes Received:
    253
    Is this the VOIP you are trying to authenticate to:
    _sip._udp.sip.voip-unlimited.net ?

    Is that the correct host name? I can not resolve that to an IP Address.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. webby

    Joined:
    Oct 20, 2009
    Messages:
    25
    Likes Received:
    0
    That is the settings I copied from my working 3cx machine.

    I will double check it now and report back
     
  7. webby

    Joined:
    Oct 20, 2009
    Messages:
    25
    Likes Received:
    0
    THANK YOU SOO MUCH - Don't kno how i didn't spot the name not resolving.

    I compared settings couldnt see any difference so took a fresh back up from my working system and restored again to my back up and Robert fast became my mothers brother.

    Excellent! I can go on holiday wiht peace of mind knowing they will have a back up to use
     
  8. wagner.damiao

    Joined:
    Jul 6, 2012
    Messages:
    17
    Likes Received:
    0
    Hello Weby,

    You can use the plugin VMWare Converter Standalone;

    https://my.vmware.com/web/vmware/info/slug/infrastructure_operations_management/vmware_vcenter_converter_standalone/5_0?rct=j&url=http://www.vmware.com/go/download-converter&q=vmware%2520converter%2520standalone&ei=E4n8T-7dEYf89QTMo5j4Bg&usg=AFQjCNGQHFn-L8p2eyDVLYIchT9q2c-9WQ

    This plugin makes a copy of your server and you can run on another server faster.

    Best Regards.
     
  9. webby

    Joined:
    Oct 20, 2009
    Messages:
    25
    Likes Received:
    0
    Yes I have that VM Ware converter - it's very good.

    I am currently using VirtualBox, and for ease of use and continuity I wanted to use all of my virtual machines through the same interface.
    Also my Dad has to use it and he doen't need to learn how to use anymore software
     
  10. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    3,321
    Likes Received:
    253
    Glad you got it sorted out...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.