URGENT: Remote Extension - Softphone/Tunnel - Intermittant

Discussion in 'Windows' started by hades, Oct 31, 2009.

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

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Hi all.. I'm currently trialling the 3cx pbx system and soft-phones for use within my company.

    I have setup the 3cx phone system on a Windows Vista Business 64 system at the office and have 3 extensions configured and all work on the office network just fine.

    I sometimes work from home however and would like to login from home.

    I have opened ports on the office router firewall and my home router firewall as follows:

    9000 - 9049
    5070 - 5100 **
    3400 - 3499

    ** Note I've also changed the default port in the server to start at 5070 - this was due to a conflict with another service used on our network that uses 5060 and 5061

    I have tried both with and without a tunnel (yes it's enabled on the server) but the phone and assistant both will not connect from my home.

    My home network was tested with one PC connected directly to my BT Home Hub which is connected to the internet and has the above ports forwarded to my PC's static LAN IP.

    I'd be really grateful for any advice here as it's driving me insane and I've tried everything I can find for similar issues on this forum.
     
  2. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Re: remote Extensions 3CX Phone/Assistant

    Ok.. my bad... I was trying to connect to the wrong IP.. that's sorted now but I get no audio in either direction when making / receiving calls.

    Any ideas?
     
  3. KerryG

    KerryG Active Member

    Joined:
    Jun 19, 2009
    Messages:
    960
    Likes Received:
    0
    Re: remote Extensions 3CX Phone/Assistant

    That is almost always a NAT issue. Do you have stun settings setup?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Re: remote Extensions 3CX Phone/Assistant

    Yup, stun and nat were both configured correctly. I restarted all services on the server and the phone is now connected and audio working in both directions.

    Still can't get the assistant to connect though.
     
  5. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Re: remote Extensions 3CX Phone/Assistant

    Ok... I have had the phone and assistant working together ....

    The phone is setup to use a tunnel on a custom port (yes it's configured in the pbx)
    - If I try to connect the phone without the tunnel I can connect but get no audio in either direction.
    - No NAT on either end as both ends are DMZ'd and Widows firewall is turned off.

    - When using the tunnel I can get connected and get audio ok, but the phone intermittantly drops calls/audio
    - Callers report that audio is stuttery/echoing
    - When I get disconnected the next few reconnection attempts fail with the error "Invalid PIN" yet nothing has changed.


    The only way I could get the assistant working was without the tunnel... wierd?
    - Trying to connect via a tunnel connects intermittantly but most often times out
    - Connecting without tunnel works fine


    finally... in the Phone system web-admin under the "Phones" section on the left my remote extension appears multiple times... it seems each reconnection generates a new "Phone" in there.


    This is really becoming an issue as several of my staff work from home and the ability to take calls at home is important to my business. I was planning to purchase a license for this 3CX system once all the kinks are ironed out but it's getting me more and more frustrated at present and I may just scrap the whole thing and look a some of the other options on the market. A few of my friends businesses use something called Asterisk and say they have nothing like these problems.
     
  6. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,476
    Likes Received:
    67
    Re: remote Extensions 3CX Phone/Assistant

    It looks like being a misproper STUN usage on the phone:
    - if the PBX is located on interent, then specify its address on "I am out of the office - extern IP" field (this enables STUN).
    - if the PBX is located on intranet, then specify its address on "I am in the office - local IP" field (this disables STUN).
    If you invert them, almost for sure you will have no audio.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Ok... Let me get this all down so weknow where we're at.

    I have a 3CX phone system setup at the office.
    - No firewall on PC
    - NAT router with DMZ configured for 3CX box's LAN IP.

    All extensions on the LAN with the 3CX box work perfectly.

    I have the 3cx soft phone installed on my home PC.
    - BT Home Hub router
    - Ports opened to my PC's local IP....

    Code:
    TCP	5070-5100	5070-5100	TCP	0
    UDP	5070-5100	5070-5100	UDP	0
    TCP	1000-5000	1000-5000	TCP	0
    UDP	1000-5000	1000-5000	UDP	0
    TCP	7000-9049	7000-9049	TCP	0
    UDP	7000-9049	7000-9049	UDP	0
    I opened more on the ranges to ensure that I had everything covered.

    In the soft phone I have tried connecting without the tunnel...
    - no audio in either direction but connection is otherwise stable

    ... and with the tunnel
    - Port is correct in both phone and 3cx system
    - Tunnel Password has been checked and double checked
    - Audio ok in both directions
    - connection drops out about every 1-3 minutes

    Phone Debug log:
    Code:
    <16:04:52> Attempting to connect 212.159.94.88
    <16:04:52> Using network interface 127.0.0.1
    <16:04:52> Tunnel got as listening port 4404
    <16:04:52> Tunnel got as local SIP port 4405
    <16:04:52> Phone got as local port 4406
    <16:04:53> RTP engine OK
    <16:04:53> SIP engine OK
    <16:04:53> Sound mic device OK [{BD6DD71B-3DEB-11D1-B171-00C04FC20002}]
    <16:04:53> Sound ring device OK []
    <16:04:53> Sound play device OK [{BD6DD71A-3DEB-11D1-B171-00C04FC20002}]
    <16:04:53> Tunnel required cfg file:C:\Documents and Settings\Lee\Local Settings\Application Data\3CX VoIP Phone\3CxVoipPhone.ini
    <16:04:53> Tunnel logfile output:C:\Documents and Settings\Lee\Local Settings\Application Data\3CX VoIP Phone\Logs
    <16:04:53> Tunnel logging: off
    <16:04:53> Tunnel connection created OK
    <16:04:53> Attempting to start the tunnel
    <16:04:53> Tunnel started
    <16:04:53> Tunnel is attempting to connect remote end
    <16:05:02> Tunnel connection established
    <16:05:02> Tunnel send from phone to PBX: REGISTER
    <16:05:05> Tunnel received from PBX status 407
    <16:05:05> Tunnel send from phone to PBX: REGISTER
    <16:05:09> Tunnel received from PBX status 407
    <16:05:09> Tunnel send from phone to PBX: REGISTER
    <16:05:09> Tunnel received from PBX status 200
    <16:05:09> Phone online status is now 'Available'
    <16:05:09> Phone is now connected
    <16:05:09> Tunnel received from PBX to phone: NOTIFY
    <16:05:09> Tunnel send from phone to PBX: SUBSCRIBE
    <16:05:09> Tunnel send from phone to PBX status 405
    <16:05:10> Tunnel received from PBX status 407
    <16:05:10> Tunnel send from phone to PBX: SUBSCRIBE
    <16:05:10> Tunnel received from PBX status 200
    <16:05:10> Tunnel received from PBX to phone: NOTIFY
    <16:05:10> Tunnel send from phone to PBX status 200
    <16:05:11> Tunnel send from phone to PBX: INVITE
    <16:05:11> Tunnel RTP ports OK
    <16:05:12> Tunnel received from PBX status 407
    <16:05:12> Tunnel send from phone to PBX: INVITE
    <16:05:12> Tunnel RTP ports OK
    <16:05:16> Tunnel received from PBX status 180
    <16:05:20> Tunnel received from PBX status 200
    <16:05:20> Tunnel answer SDP
    <16:05:20> Tunnel send from phone to PBX: ACK
    <16:05:20> Tunnel received from PBX status 200
    <16:05:20> Tunnel send from phone to PBX: ACK
    <16:05:43> Tunnel send from phone to PBX: BYE
    <16:05:44> Tunnel received from PBX status 200
    <16:06:58> Tunnel send from phone to PBX: SUBSCRIBE
    <16:06:59> Tunnel received from PBX status 200
    <16:06:59> Tunnel received from PBX to phone: NOTIFY
    <16:06:59> Tunnel send from phone to PBX status 200
    <16:08:47> Tunnel send from phone to PBX: SUBSCRIBE
    <16:08:52> Tunnel has been disconnected by remote end
    <16:08:52> Tunnel is attempting to connect remote end
    <16:08:53> Phone is no longer connected
    <16:09:02> Tunnel connection established
    <16:09:02> Tunnel send from phone to PBX: REGISTER
    <16:09:15> Tunnel has been disconnected by remote end
    <16:09:15> Tunnel is attempting to connect remote end
    <16:09:17> Tunnel connection established
    <16:09:17> Tunnel send from phone to PBX: REGISTER
    <16:09:26> Tunnel received from PBX status 407
    <16:09:26> Tunnel send from phone to PBX: REGISTER
    <16:09:34> Tunnel received from PBX status 407
    <16:09:34> Tunnel send from phone to PBX: REGISTER
    <16:09:36> Tunnel received from PBX status 200
    <16:09:36> Phone online status is now 'Available'
    <16:09:36> Phone is now connected
    <16:09:36> Tunnel received from PBX to phone: NOTIFY
    <16:09:36> Tunnel send from phone to PBX: SUBSCRIBE
    <16:09:36> Tunnel send from phone to PBX status 405
    <16:09:38> Tunnel received from PBX status 407
    <16:09:38> Tunnel send from phone to PBX: SUBSCRIBE
    <16:09:43> Tunnel received from PBX status 200
    <16:09:43> Tunnel received from PBX to phone: NOTIFY
    <16:09:43> Tunnel send from phone to PBX status 200
    <16:11:11> Tunnel has been disconnected by remote end
    <16:11:11> Phone is no longer connected
    <16:11:12> Tunnel is attempting to connect remote end
    <16:11:14> Tunnel connection established
    <16:11:16> Tunnel send from phone to PBX: REGISTER
    <16:11:19> Tunnel received from PBX status 407
    <16:11:19> Tunnel send from phone to PBX: REGISTER
    <16:11:31> Tunnel has been disconnected by remote end
    <16:11:31> Tunnel is attempting to connect remote end
    <16:11:35> Tunnel connection established
    <16:11:35> Tunnel send from phone to PBX: REGISTER
    <16:11:54> Tunnel is attempting to connect remote end
    <16:11:54> Tunnel has been disconnected by remote end
    <16:12:04> Tunnel connection established
    <16:12:04> Tunnel send from phone to PBX: REGISTER
    <16:12:47> Tunnel has been disconnected by remote end
    <16:12:47> Tunnel is attempting to connect remote end
    <16:12:56> Tunnel connection established
    <16:12:56> Tunnel send from phone to PBX: REGISTER
    <16:13:02> Tunnel is attempting to connect remote end
    <16:13:02> Tunnel has been disconnected by remote end
    <16:13:05> Tunnel connection established
    <16:13:05> Tunnel send from phone to PBX: REGISTER
    <16:13:09> Tunnel has been disconnected by remote end
    <16:13:10> Tunnel is attempting to connect remote end
    <16:13:10> Tunnel connection established
    <16:13:10> Tunnel send from phone to PBX: REGISTER
    <16:13:10> Tunnel received from PBX status 407
    <16:13:10> Tunnel send from phone to PBX: REGISTER
    <16:13:11> Tunnel received from PBX status 200
    <16:13:11> Tunnel received from PBX to phone: NOTIFY
    <16:13:11> Phone online status is now 'Available'
    <16:13:11> Phone is now connected
    <16:13:11> Tunnel send from phone to PBX: SUBSCRIBE
    <16:13:11> Tunnel send from phone to PBX status 405
    <16:13:11> Tunnel received from PBX status 407
    <16:13:11> Tunnel send from phone to PBX: SUBSCRIBE
    <16:13:12> Tunnel received from PBX status 200
    <16:13:12> Tunnel received from PBX to phone: NOTIFY
    <16:13:12> Tunnel send from phone to PBX status 200
    <16:13:42> Tunnel has been disconnected by remote end
    <16:13:42> Phone is no longer connected
    <16:13:42> Tunnel is attempting to connect remote end
    <16:13:43> Tunnel connection established
    <16:13:47> Tunnel send from phone to PBX: REGISTER
    <16:13:49> Tunnel received from PBX status 407
    <16:13:49> Tunnel send from phone to PBX: REGISTER
    <16:13:51> Tunnel received from PBX status 200
    <16:13:51> Phone online status is now 'Available'
    <16:13:51> Phone is now connected
    <16:13:51> Tunnel received from PBX to phone: NOTIFY
    <16:13:51> Tunnel send from phone to PBX: SUBSCRIBE
    <16:13:51> Tunnel send from phone to PBX status 405
    <16:13:52> Tunnel received from PBX status 407
    <16:13:52> Tunnel send from phone to PBX: SUBSCRIBE
    <16:13:52> Tunnel received from PBX status 200
    <16:13:52> Tunnel received from PBX to phone: NOTIFY
    <16:13:52> Tunnel send from phone to PBX status 200
    <16:15:10> Tunnel has been disconnected by remote end
    <16:15:10> Phone is no longer connected
    <16:15:10> Tunnel is attempting to connect remote end
    <16:15:12> Tunnel connection established
    <16:15:15> Tunnel send from phone to PBX: REGISTER
    <16:15:18> Tunnel has been disconnected by remote end
    <16:15:18> Tunnel is attempting to connect remote end
    <16:15:39> Tunnel connection attempt failed
    <16:15:40> Tunnel is attempting to connect remote end
    <16:15:40> Tunnel connection established
    <16:15:40> Tunnel send from phone to PBX: REGISTER
    <16:15:41> Tunnel received from PBX status 407
    <16:15:41> Tunnel send from phone to PBX: REGISTER
    <16:15:44> Tunnel received from PBX status 407
    <16:15:44> Tunnel send from phone to PBX: REGISTER
    <16:15:45> Tunnel received from PBX status 200
    <16:15:45> Phone online status is now 'Available'
    <16:15:45> Phone is now connected
    <16:15:45> Tunnel send from phone to PBX: SUBSCRIBE
    <16:15:45> Tunnel received from PBX to phone: NOTIFY
    <16:15:45> Tunnel send from phone to PBX status 405
    <16:15:45> Tunnel received from PBX status 407
    <16:15:46> Tunnel send from phone to PBX: SUBSCRIBE
    <16:15:47> Tunnel received from PBX status 200
    <16:15:47> Tunnel received from PBX to phone: NOTIFY
    <16:15:47> Tunnel send from phone to PBX status 200
    <16:17:35> Tunnel send from phone to PBX: SUBSCRIBE
    <16:17:37> Tunnel received from PBX status 200
    <16:17:37> Tunnel received from PBX to phone: NOTIFY
    <16:17:38> Tunnel send from phone to PBX status 200
    <16:19:01> Tunnel is attempting to connect remote end
    <16:19:01> Tunnel has been disconnected by remote end
    <16:19:01> Phone is no longer connected
    <16:19:09> Tunnel connection established
    <16:19:09> Tunnel send from phone to PBX: REGISTER
    <16:19:15> Tunnel received from PBX status 407
    <16:19:15> Tunnel send from phone to PBX: REGISTER
    <16:19:17> Tunnel received from PBX status 200
    <16:19:17> Phone online status is now 'Available'
    <16:19:17> Phone is now connected
    <16:19:17> Tunnel received from PBX to phone: NOTIFY
    <16:19:17> Tunnel send from phone to PBX: SUBSCRIBE
    <16:19:17> Tunnel send from phone to PBX status 405
    <16:19:25> Tunnel received from PBX status 407
    <16:19:25> Tunnel send from phone to PBX: SUBSCRIBE
    <16:19:38> Tunnel is attempting to connect remote end
    <16:19:38> Tunnel has been disconnected by remote end
    <16:19:38> Phone is no longer connected
    <16:19:46> Tunnel connection established
    <16:19:46> Tunnel send from phone to PBX: REGISTER
    Server log for same period:
    Code:
    16:19:01.922  [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449/100,sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456/100,sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a/100,sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2/100,sip:100@127.0.0.1:4406;rinstance=6468a9c606854eb7/100,sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6/100,sip:100@127.0.0.1:4406;rinstance=c0f373e365136ee4/100,sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534/100,sip:100@127.0.0.1:4406;rinstance=91d0f2457db7e346/100,sip:100@127.0.0.1:4406;rinstance=9e6053674361a84b/100,sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970/100,sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95/100,sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b/100,sip:100@127.0.0.1:4406;rinstance=b5a6084247fbf6fb/100,sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4/100,sip:100@127.0.0.1:2929;rinstance=f235c152863546f9/100]
    16:15:29.266  [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5/100,sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449/100,sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456/100,sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a/100,sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8/100,sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2/100,sip:100@127.0.0.1:4406;rinstance=6468a9c606854eb7/100,sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6/100,sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e/100,sip:100@127.0.0.1:4406;rinstance=c0f373e365136ee4/100,sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534/100,sip:100@127.0.0.1:4406;rinstance=9e6053674361a84b/100,sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970/100,sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95/100,sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b/100,sip:100@127.0.0.1:4406;rinstance=b5a6084247fbf6fb/100,sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4/100,sip:100@127.0.0.1:2929;rinstance=f235c152863546f9/100]
    16:13:39.894  [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.21:3478 over Transport 192.168.0.18:5070
    16:13:35.990  [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5/100,sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449/100,sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456/100,sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a/100,sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8/100,sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2/100,sip:100@127.0.0.1:4406;rinstance=6468a9c606854eb7/100,sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6/100,sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e/100,sip:100@127.0.0.1:4406;rinstance=c0f373e365136ee4/100,sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534/100,sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970/100,sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95/100,sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b/100,sip:100@127.0.0.1:4406;rinstance=b5a6084247fbf6fb/100,sip:100@127.0.0.1:2929;rinstance=736fa40eb79693bf/100,sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4/100,sip:100@127.0.0.1:2929;rinstance=f235c152863546f9/100]
    16:12:55.355  [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5/100,sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449/100,sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456/100,sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a/100,sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8/100,sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2/100,sip:100@127.0.0.1:4406;rinstance=6468a9c606854eb7/100,sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6/100,sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e/100,sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534/100,sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970/100,sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95/100,sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b/100,sip:100@127.0.0.1:4406;rinstance=b5a6084247fbf6fb/100,sip:100@127.0.0.1:2929;rinstance=736fa40eb79693bf/100,sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4/100,sip:100@127.0.0.1:2929;rinstance=f235c152863546f9/100]
    16:09:20.616  [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5/100,sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449/100,sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456/100,sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a/100,sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8/100,sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2/100,sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6/100,sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e/100,sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534/100,sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970/100,sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95/100,sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b/100,sip:100@127.0.0.1:4406;rinstance=b5a6084247fbf6fb/100,sip:100@127.0.0.1:2929;rinstance=736fa40eb79693bf/100,sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4/100,sip:100@127.0.0.1:2929;rinstance=f235c152863546f9/100,sip:100@127.0.0.1:2929;rinstance=b06729bed4c5b392/100]
    16:05:28.753  [CM503008]: Call(128): Call is terminated
    16:05:03.915  [CM503007]: Call(128): Device joined: sip:441629706322@phone.vopr.vonage.net:5060
    16:05:03.913  [CM503007]: Call(128): Device joined: sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456
    16:05:03.911  [CM505003]: Provider:[Vonage UK] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:441629706322@212.159.94.88:5070]
    16:05:03.911  [CM503002]: Call(128): Alerting sip:441629706322@phone.vopr.vonage.net:5060
    16:05:00.303  [CM505003]: Provider:[Vonage UK] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:441629706322@212.159.94.88:5070]
    16:05:00.303  [CM503002]: Call(128): Alerting sip:441629706322@phone.vopr.vonage.net:5060
    16:04:58.148  [CM503025]: Call(128): Calling VoIPline:*6701904345963@(Ln.10000@Vonage UK)@[Dev:sip:441629706322@phone.vopr.vonage.net:5060]
    16:04:57.892  [CM503004]: Call(128): Route 1: VoIPline:*6701904345963@(Ln.10000@Vonage UK)@[Dev:sip:441629706322@phone.vopr.vonage.net:5060]
    16:04:57.890  [CM503010]: Making route(s) to <sip:01904345963@192.168.0.18:5070>
    16:04:57.888  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:04:57.886  [CM503001]: Call(128): Incoming call from Ext.100 to <sip:01904345963@192.168.0.18:5070>
    16:04:53.951  [CM504001]: Ext.100: new contact is registered. Contact(s): [sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5/100,sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449/100,sip:100@127.0.0.1:4406;rinstance=7604d1dd15e57456/100,sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a/100,sip:100@127.0.0.1:2929;rinstance=f7896a2c2fb63cc8/100,sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8/100,sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2/100,sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6/100,sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e/100,sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534/100,sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970/100,sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95/100,sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b/100,sip:100@127.0.0.1:2929;rinstance=736fa40eb79693bf/100,sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4/100,sip:100@127.0.0.1:2929;rinstance=3cf087b785061a8b/100,sip:100@127.0.0.1:2929;rinstance=f235c152863546f9/100,sip:100@127.0.0.1:2929;rinstance=b06729bed4c5b392/100,sip:100@127.0.0.1:2929;rinstance=c07271f58db1c48f/100]
    16:04:49.930  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 408 Request Timeout; internal
    16:04:49.928  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 408 Request Timeout; internal
    16:03:50.472  [CM503008]: Call(127): Call is terminated
    16:03:47.058  [CM503016]: Call(127): Attempt to reach <sip:01904345963@127.0.0.1:5070> failed. Reason: Not Implemented
    16:03:47.057  [CM503003]: Call(127): Call to sip:*6701904345963@phone.vopr.vonage.net:5060 has failed; Cause: 488 Not Acceptable Here; from IP:216.115.20.41:5061
    16:03:46.667  [CM503025]: Call(127): Calling VoIPline:*6701904345963@(Ln.10000@Vonage UK)@[Dev:sip:441629706322@phone.vopr.vonage.net:5060]
    16:03:46.389  [CM503004]: Call(127): Route 1: VoIPline:*6701904345963@(Ln.10000@Vonage UK)@[Dev:sip:441629706322@phone.vopr.vonage.net:5060]
    16:03:46.387  [CM503010]: Making route(s) to <sip:01904345963@127.0.0.1:5070>
    16:03:45.777  [CM503007]: Call(127): Device joined: sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4
    16:03:45.776  [CM503007]: Call(127): Device joined: sip:MakeCall@127.0.0.1:40600;rinstance=52d6bda30382d455
    16:03:41.752  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:03:41.752  [CM503002]: Call(127): Alerting sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4
    16:03:41.749  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:03:41.749  [CM503002]: Call(127): Alerting sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2
    16:03:41.380  [MS105000] C:125.3: No RTP packets were received:remoteAddr=192.168.0.18:10010,extAddr=0.0.0.0:0,localAddr=192.168.0.18:7054
    16:03:41.267  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:41.265  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:41.263  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:41.255  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:41.244  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.892  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:03:40.892  [CM503002]: Call(127): Alerting sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449
    16:03:40.796  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.794  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.792  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.790  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.788  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.786  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.770  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.759  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.749  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.735  [CM503003]: Call(127): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:40.732  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=c07271f58db1c48f]
    16:03:40.726  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=b06729bed4c5b392]
    16:03:40.720  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=f235c152863546f9]
    16:03:40.714  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=3cf087b785061a8b]
    16:03:40.709  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4]
    16:03:40.703  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=736fa40eb79693bf]
    16:03:40.697  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b]
    16:03:40.692  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95]
    16:03:40.686  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970]
    16:03:40.681  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534]
    16:03:40.676  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e]
    16:03:40.670  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6]
    16:03:40.665  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2]
    16:03:40.660  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8]
    16:03:40.655  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=f7896a2c2fb63cc8]
    16:03:40.650  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a]
    16:03:40.645  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449]
    16:03:40.640  [CM503025]: Call(127): Calling Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5]
    16:03:40.591  [CM503004]: Call(127): Route 1: Ext:Ext.100@[Dev:sip:100@127.0.0.1:2929;rinstance=b2d6a1f53a6268b5,Dev:sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449,Dev:sip:100@127.0.0.1:2929;rinstance=de4e07503cab747a,Dev:sip:100@127.0.0.1:2929;rinstance=f7896a2c2fb63cc8,Dev:sip:100@127.0.0.1:2929;rinstance=19ad8624418f20c8,Dev:sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2,Dev:sip:100@127.0.0.1:2929;rinstance=2e98dd804e156ce6,Dev:sip:100@127.0.0.1:2929;rinstance=e484cd30e45c2c8e,Dev:sip:100@127.0.0.1:2929;rinstance=ea86e53300da2534,Dev:sip:100@127.0.0.1:2929;rinstance=37007f8b3d3f9970,Dev:sip:100@127.0.0.1:2929;rinstance=9ba32af5f5416f95,Dev:sip:100@127.0.0.1:2929;rinstance=af46c1d581d50a5b,Dev:sip:100@127.0.0.1:2929;rinstance=736fa40eb79693bf,Dev:sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4,Dev:sip:100@127.0.0.1:2929;rinstance=3cf087b785061a8b,Dev:sip:100@127.0.0.1:2929;rinstance=f235c152863546f9,Dev:sip:100@127.0.0.1:2929;rinstance=b06729bed4c5b392,Dev:sip:100@127.0.0.1:2929;rinstance=c07271f58db1c48f]
    16:03:40.590  [CM503010]: Making route(s) to <sip:100@127.0.0.1:5070>
    16:03:40.589  [CM505001]: Ext.MakeCall: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX MakeCall helper] PBX contact: [sip:MakeCall@127.0.0.1:5070]
    16:03:40.588  [CM503001]: Call(127): Incoming call from Ext.MakeCall to <sip:100@127.0.0.1:5070>
    16:03:37.563  [CM503008]: Call(125): Call is terminated
    16:03:37.558  [CM503003]: Call(125): Call to sip:100@192.168.0.18:5070 has failed; Cause: 486 Busy Here; from IP:192.168.0.18:5080
    16:03:37.556  [CM503020]: Normal call termination. Reason: Busy
    16:03:37.556  [CM503016]: Call(125): Attempt to reach <sip:100@127.0.0.1:5070> failed. Reason: Busy
    16:03:37.552  [CM503003]: Call(125): Call to sip:100@192.168.0.18:5070 has failed; Cause: 486 Busy Here; from IP:192.168.0.18:5080
    16:03:37.541  [CM503008]: Call(126): Call is terminated
    16:03:37.536  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 486 Busy Here; from IP:192.168.0.18:5080
    16:03:37.532  [CM503020]: Normal call termination. Reason: Busy
    16:03:37.532  [CM503016]: Call(126): Attempt to reach <sip:100@127.0.0.1:5070> failed. Reason: Busy
    16:03:37.530  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 486 Busy Here; from IP:192.168.0.18:5080
    16:03:37.408  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:03:37.407  [CM503002]: Call(126): Alerting sip:100@127.0.0.1:2929;rinstance=4caf0cc73fe95449
    16:03:37.405  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:03:37.404  [CM503002]: Call(125): Alerting sip:100@127.0.0.1:2929;rinstance=204f8659e3cb6bd4
    16:03:34.102  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:34.100  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:34.098  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:34.089  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:34.077  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:33.635  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:33.633  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:33.631  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:33.629  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    16:03:33.627  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXVoipPhone 4.0.9530.0] PBX contact: [sip:100@192.168.0.18:5070]
    16:03:33.627  [CM503002]: Call(125): Alerting sip:100@127.0.0.1:2929;rinstance=3ca348a9147554e2
    16:03:33.623  [CM503003]: Call(126): Call to sip:100@192.168.0.18:5070 has failed; Cause: 503 Remote end of tunnel is not connected; warning: Remote end of the bridge is not connected; from IP:192.168.0.18:5080
    
    also, it may be relevant... everytime my tunnel disconnect/reconnects it creates a new "Phone" in the "Phones" section of the web admin.
     
  8. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Update... also, 5070 is the port configured in my 3cx... 5060 was in use by another service on our network
     
  9. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,476
    Likes Received:
    67
    Hi

    Look, I could ask you for PBX's tunnel tracelog to try to understand what's happen (definitely, PBX tunnel is the one which is "not happy" with something and it disconnects) but my advice is to have a little patience two days (I guess), we will have a new release, including tunnel and phone. Then, if you will still encounter this issue, we will dig in. As far as I know, tunnel to be released has been improved in stability and speed, so I expect it will works better.

    Regards
    vali

    P.S Which PBX version do you use now? (the one shown on the Console's login page)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    I'm currently using 3CX Phone System v8.0.9532.468 and the latest download of the phone/assistant pack from your download pages.

    It is causing me a real problem when working from home at present. If the new version is going to be any more than 2 days away I will really need some help to get this fixed.

    Also, will there be an upgrade path from the version I'm using to the new one as reinstalling it all on a system that is running a live phone system is going to be problematic.


    To be honest I'd prefer not to use the tunnel but without it I get no audio in either direction despite having all the relevant ports open in the routers at both ends.
     
  11. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Ok, I'm working from home again today so if you need anything testing let me know.

    Curiously the phone is behaving its self today so far, but it is 8:30am.

    Could this be an issue with my ISP / Broadband it's self?
     
  12. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Joined:
    Dec 12, 2008
    Messages:
    1,476
    Likes Received:
    67
    ok, a new release is available (phonesystem, assistant, phone) so you may try it to see if tunnel disconnection persists.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    Ok... I'm upgrading

    For the record today the phone has stayed connected all day with the exception of at 17:00 exactly it disconnected me from the call I was on and wouldn't let me reconnect.

    17:00 is the end of our office hours as configured in the PBX... would this have closed the tunnel?
     
  14. LeonidasG

    LeonidasG Support Team
    Staff Member 3CX Support

    Joined:
    Nov 19, 2008
    Messages:
    1,455
    Likes Received:
    92

    I havent heard of a Tunnel Disconnecting you when it's Out of office hours :p That would be funny.
    Office Hours / Out of Office hours shouldnt disconnect you from any existing calls, and will only apply to: "Internal Extensions with Forwarding Rules" "Incoming DID Calls"


    Can you confirm that this happens tomorrow too at the same time? :p Although i will double check it for myself.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. hades

    Joined:
    Oct 31, 2009
    Messages:
    33
    Likes Received:
    0
    I've noticed it twice now, but only when on an external extension connecting via the tunnel using the 3cx softphone.

    I've been having issues as above anyway but on the days in question I had no disconnects all day and was on an active call at 17:00. As soon as 17:00 arrived my outbound audio was stopped (but I could still hear the other person). After hanging up the soft fone would show "Not connected" and would not reconnect.

    From that point on it just gives "Invalid PIN" when trying to connect.

    First time it happened I didn't really pay it much attention due to the other issues I'd been having, but this time I remembered it happening before after a day of good connectivity and it made me wonder.
     
Thread Status:
Not open for further replies.