One-way audio from GXP-2000 to softphone

Discussion in 'Windows' started by annexus, Mar 20, 2008.

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

    Joined:
    Mar 20, 2008
    Messages:
    1
    Likes Received:
    0
    Hello Everyone,

    We're testing the free version currently and so far it's going pretty well. However, even before we have external VOIP connectivity -- just testing between extensions -- we have run into a problem.

    Between two Grandstream GXP-2000 hardphones, life is wonderful. Calls in both directions work perfectly, every time. Calls established from the 3CX softphone (5.1.4132.0) to the GXP-2000 seem to be working OK as well.

    However, calls established from the GXP-2000 to the softphone result in one-way audio about 50% of the time. When this occurs, the softphone can hear the hardphone but the hardphone cannot hear the softphone. The server log shows a report from the media server "No RTP packets were received" from the softphone's IP, but only when the problem is occurring. When the call goes through correctly, no error occurs -- which, I suppose, makes sense. See log below, extension 101 is the softphone, 102 is the GXP.

    The client workstation running the softphone is on Vista. The symptoms are the same regardless of whether or not the firewalls are enabled on the server and/or the client. If we can get past this bump in the road, we'll be able to start testing externally. We have a customer who is ready to buy, but this is obviously a deal-breaker if we can't resolve it soon.

    Thank you for any insights you can provide,

    Chris


    15:58:44.468 MediaServerReporting::RTPReceiver [MS105000] C:26.2: No RTP packets were received:remoteAddr=192.168.2.44:42010,extAddr=0.0.0.0:0,localAddr=192.168.2.11:7090
    15:58:44.203 Call::Terminate [CM503008]: Call(26): Call is terminated
    15:58:44.203 Call::Terminate [CM503008]: Call(26): Call is terminated
    15:58:35.609 CallCtrl::eek:nLegConnected [CM503007]: Call(26): Device joined: sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23
    15:58:35.593 CallCtrl::eek:nLegConnected [CM503007]: Call(26): Device joined: sip:102@192.168.2.105:5060;transport=udp
    15:58:32.687 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(26): Calling: Ext:101@[Dev:sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23]
    15:58:32.640 CallCtrl::eek:nIncomingCall [CM503001]: Call(26): Incoming call from Ext.102 to [sip:101@192.168.2.11]
    15:58:05.500 Call::Terminate [CM503008]: Call(24): Call is terminated
    15:58:05.500 Call::Terminate [CM503008]: Call(24): Call is terminated
    15:57:54.984 CallCtrl::eek:nLegConnected [CM503007]: Call(24): Device joined: sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23
    15:57:54.968 CallCtrl::eek:nLegConnected [CM503007]: Call(24): Device joined: sip:102@192.168.2.105:5060;transport=udp
    15:57:53.593 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(24): Calling: Ext:101@[Dev:sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23]
    15:57:53.562 CallCtrl::eek:nIncomingCall [CM503001]: Call(24): Incoming call from Ext.102 to [sip:101@192.168.2.11]
    15:57:08.593 MediaServerReporting::RTPReceiver [MS105000] C:23.2: No RTP packets were received:remoteAddr=192.168.2.44:42006,extAddr=0.0.0.0:0,localAddr=192.168.2.11:7080
    15:57:08.343 Call::Terminate [CM503008]: Call(23): Call is terminated
    15:57:08.343 Call::Terminate [CM503008]: Call(23): Call is terminated
    15:56:59.765 CallCtrl::eek:nLegConnected [CM503007]: Call(23): Device joined: sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23
    15:56:59.734 CallCtrl::eek:nLegConnected [CM503007]: Call(23): Device joined: sip:102@192.168.2.105:5060;transport=udp
    15:56:54.453 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(23): Calling: Ext:101@[Dev:sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23]
    15:56:54.406 CallCtrl::eek:nIncomingCall [CM503001]: Call(23): Incoming call from Ext.102 to [sip:101@192.168.2.11]
    15:56:48.968 Call::Terminate [CM503008]: Call(22): Call is terminated
    15:56:48.968 Call::Terminate [CM503008]: Call(22): Call is terminated
    15:56:20.078 CallCtrl::eek:nLegConnected [CM503007]: Call(22): Device joined: sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23
    15:56:20.062 CallCtrl::eek:nLegConnected [CM503007]: Call(22): Device joined: sip:102@192.168.2.105:5060;transport=udp
    15:56:17.015 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(22): Calling: Ext:101@[Dev:sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23]
    15:56:16.984 CallCtrl::eek:nIncomingCall [CM503001]: Call(22): Incoming call from Ext.102 to [sip:101@192.168.2.11]
    15:56:03.546 FaxCfg::updateContact [CM504008]: Fax Service: registered as sip:888@3CXPhoneSystem with contact sip:888@192.168.2.11:5100;user=phone
    15:56:03.046 FaxCfg::updateContact [CM504010]: Fax Service: unregistered contact sip:888:5100;user=phone
    15:55:59.750 StunClient::eek:nInitTests [CM506001]: STUN request to resolve SIP external IP:port mapping is sent to STUN server 64.69.76.23:3478 over Transport 192.168.2.11:5060
    15:54:46.078 MediaServerReporting::RTPReceiver [MS105000] C:21.2: No RTP packets were received:remoteAddr=192.168.2.44:42002,extAddr=0.0.0.0:0,localAddr=192.168.2.11:7072
    15:54:45.828 Call::Terminate [CM503008]: Call(21): Call is terminated
    15:54:45.812 Call::Terminate [CM503008]: Call(21): Call is terminated
    15:54:35.078 CallCtrl::eek:nLegConnected [CM503007]: Call(21): Device joined: sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23
    15:54:35.046 CallCtrl::eek:nLegConnected [CM503007]: Call(21): Device joined: sip:102@192.168.2.105:5060;transport=udp
    15:54:31.250 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(21): Calling: Ext:101@[Dev:sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23]
    15:54:31.218 CallCtrl::eek:nIncomingCall [CM503001]: Call(21): Incoming call from Ext.102 to [sip:101@192.168.2.11]
    15:54:21.750 Call::Terminate [CM503008]: Call(20): Call is terminated
    15:54:21.750 Call::Terminate [CM503008]: Call(20): Call is terminated
    15:54:07.421 CallCtrl::eek:nLegConnected [CM503007]: Call(20): Device joined: sip:102@192.168.2.105:5060;transport=udp
    15:54:07.406 CallCtrl::eek:nLegConnected [CM503007]: Call(20): Device joined: sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23
    15:54:05.312 CallCtrl::eek:nSelectRouteReq [CM503004]: Call(20): Calling: Ext:102@[Dev:sip:102@192.168.2.105:5060;transport=udp]
    15:54:05.281 CallCtrl::eek:nIncomingCall [CM503001]: Call(20): Incoming call from Ext.101 to [sip:102@192.168.2.11:5060]
    15:53:34.218 ExtnCfg::updateContact [CM504001]: Ext.101: new contact is registered. Contact(s): [sip:101@192.168.2.44:5060;rinstance=d37a0d1f062f2e23/101]
    15:53:34.078 ExtnCfg::updateContact [CM504002]: Ext.101: a contact is unregistered. Contact(s): []
     
  2. h2009

    h2009 Member

    Joined:
    Mar 15, 2008
    Messages:
    447
    Likes Received:
    0
    i'd like an answer to this as well.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. dnwklin

    Joined:
    Feb 2, 2009
    Messages:
    10
    Likes Received:
    0
    I saw many similar problems without an answer. If 3CX is problem.
     
  4. discovery1

    discovery1 Member

    Joined:
    Aug 4, 2008
    Messages:
    355
    Likes Received:
    0
    Can you check that the Codecs on the GXP-2000 and the 3CX softphone match?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Vali_3CX

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

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

    If the version you provided here is correct, then my advice is to replace your old 3CX softphones with the latest Voip Phone - http://www.3cx.com/forums/new-update-3cx-softphone-release-candidate-8757.html . Not only since version 5 three other ones were released, but also PBX has changed heavily. Definitely, version 5 of the softphone is no longer supported for technical support.

    Please try to replace them and do your test again - if the one-way audio issue still persist, then we will ask you for further details.

    Regards
    vali
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. deer307

    Joined:
    Nov 11, 2008
    Messages:
    4
    Likes Received:
    0
    HI ~
    I have the two external phone . should I forward the port of firewall in the external. which ports should open in the local of external firewall.

    thanks
     
Thread Status:
Not open for further replies.