3CX v10 voice problem VOIP-provider

Discussion in '3CX Phone System - General' started by Sergiy, Feb 5, 2014.

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

    Joined:
    Dec 12, 2011
    Messages:
    15
    Likes Received:
    0
    Hi to all.
    I have in my office ipLDK100 pbx connected with 3CX as VOIP provider. All works fine, but approximately one time in day I need to restart 3CX services. The problem with incoming calls from LDK, opponents are not hear each other (outgoing to LDK still OK). Once services were restarted all works fine. Logs of calls after and before restart are equal. Firewall not drops packets.
    Please, help me to solve this problem.

    Invites:
    Code:
    13:11:18.113  [CM503008]: Call(2253): Call is terminated
    13:11:12.504  [CM503007]: Call(2253): Device joined: sip:1004@192.168.1.81:5062
    13:11:12.496  [CM503007]: Call(2253): Device joined: sip:1000@192.168.1.130:5060
    13:11:12.494  [MS210007] C:2253.1:Answer provided. Connection(by pass mode): 192.168.1.81:11782(11783)
    13:11:12.493  [MS210001] C:2253.2:Answer received. RTP connection[unsecure]: 192.168.1.81:11782(11783)
    13:11:12.492  Remote SDP is set for legC:2253.2
    13:11:09.946  [CM505001]: Ext.1004: Device info: Device Identified: [Man: Yealink;Mod: T20;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T20P 9.60.14.24] PBX contact: [sip:1004@192.168.1.131:5060]
    13:11:09.946  [CM503002]: Call(2253): Alerting sip:1004@192.168.1.81:5062
    13:11:09.610  [CM503025]: Call(2253): Calling Ext:Ext.1004@[Dev:sip:1004@192.168.1.81:5062]
    13:11:09.609  [MS210006] C:2253.2:Offer provided. Connection(by pass mode): 192.168.1.130:2054(2055)
    13:11:09.572  [CM503004]: Call(2253): Route 1: Ext:Ext.1004@[Dev:sip:1004@192.168.1.81:5062]
    13:11:09.570  [CM503010]: Making route(s) to <sip:1004@62.XXX.XXX.XXX:5060>
    13:11:09.570  [MS210000] C:2253.1:Offer received. RTP connection: 192.168.1.130:2054(2055)
    13:11:09.569  Remote SDP is set for legC:2253.1
    13:11:09.569  [CM505003]: Provider:[LDK100] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [VP-2009P 23.70.14.14] PBX contact: [sips:1000@192.168.1.131:5060]
    13:11:09.566  [CM503001]: Call(2253): Incoming call from 7993@(Ln.10005@LDK100) to <sip:1004@62.XXX.XXX.XXX:5060>
    13:11:09.558  [CM503012]: Inbound any hours rule (unnamed) for 10005 forwards to DN:1004
    13:11:09.557  Look[i][/i]ing for inbound target: called=1004; caller=7993
    13:11:09.555  [CM500002]: Info on incoming INVITE:
      INVITE sip:1004@192.168.1.131;user=phone SIP/2.0
      Via: SIP/2.0/UDP 192.168.1.130:5060;branch=z9hG4bK-5134c-13d3631a-425e07ce
      Max-Forwards: 70
      Contact: <sip:7993@192.168.1.130:5060>
      To: <sip:1004@192.168.1.131;user=phone>
      From: "������� �"<sip:7993@192.168.1.131>;tag=e01518-c0a80182-13c4-50029-5134c-1516ecec-5134c
      Call-ID: e07ec8-c0a80182-13c4-50029-5134c-359a266e-5134c
      CSeq: 1 INVITE
      Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, UPDATE, OPTIONS, INFO
      Supported: replaces, UPDATE, INFO
      Content-Length: 0
    after
    Code:
    13:17:18.538  [CM503008]: Call(11): Call is terminated
    13:17:09.409  Session 313 of leg C:11.1 is confirmed
    13:17:09.369  [CM503007]: Call(11): Device joined: sip:1004@192.168.1.81:5062
    13:17:09.367  [CM503007]: Call(11): Device joined: sip:1000@192.168.1.130:5060
    13:17:09.365  [MS210007] C:11.1:Answer provided. Connection(by pass mode): 192.168.1.81:11784(11785)
    13:17:09.363  [MS210001] C:11.2:Answer received. RTP connection[unsecure]: 192.168.1.81:11784(11785)
    13:17:09.362  Remote SDP is set for legC:11.2
    13:17:07.857  Currently active calls - 1: [11]
    13:17:06.664  [CM505001]: Ext.1004: Device info: Device Identified: [Man: Yealink;Mod: T20;Rev: General] Capabilities:[reinvite, no-replaces, unable-no-sdp, no-recvonly] UserAgent: [Yealink SIP-T20P 9.60.14.24] PBX contact: [sip:1004@192.168.1.131:5060]
    13:17:06.663  [CM503002]: Call(11): Alerting sip:1004@192.168.1.81:5062
    13:17:06.301  [CM503025]: Call(11): Calling Ext:Ext.1004@[Dev:sip:1004@192.168.1.81:5062]
    13:17:06.300  [MS210006] C:11.2:Offer provided. Connection(by pass mode): 192.168.1.130:2052(2053)
    13:17:06.255  [CM503004]: Call(11): Route 1: Ext:Ext.1004@[Dev:sip:1004@192.168.1.81:5062]
    13:17:06.254  [CM503010]: Making route(s) to <sip:1004@62.XXX.XXX.XXX:5060>
    13:17:06.253  [MS210000] C:11.1:Offer received. RTP connection: 192.168.1.130:2052(2053)
    13:17:06.252  Remote SDP is set for legC:11.1
    13:17:06.252  [CM505003]: Provider:[LDK100] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:1000@192.168.1.131:5060]
    13:17:06.249  [CM503001]: Call(11): Incoming call from 7993@(Ln.10005@LDK100) to <sip:1004@62.XXX.XXX.XXX:5060>
    13:17:06.235  [CM503012]: Inbound any hours rule (unnamed) for 10005 forwards to DN:1004
    13:17:06.235  Looking for inbound target: called=1004; caller=7993
    13:17:06.235  [CM500002]: Info on incoming INVITE:
      INVITE sip:1004@192.168.1.131;user=phone SIP/2.0
      Via: SIP/2.0/UDP 192.168.1.130:5060;branch=z9hG4bK-514b2-13d8d782-6dbaacb9
      Max-Forwards: 70
      Contact: <sip:7993@192.168.1.130:5060>
      To: <sip:1004@192.168.1.131;user=phone>
      From: "������� �"<sip:7993@192.168.1.131>;tag=df9f80-c0a80182-13c4-50029-514b2-63dab6a3-514b2
      Call-ID: e09288-c0a80182-13c4-50029-514b2-71fff2b5-514b2
      CSeq: 1 INVITE
      Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, UPDATE, OPTIONS, INFO
      Supported: replaces, UPDATE, INFO
      Content-Length: 0
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,373
    Likes Received:
    230
    Do I understand correctly, you are using the a Bridge trunk, in 3CX as the Master to connect to another VoIP PBX?

    Has this problem always been there? If not, what happened (changed) just before this issue began?

    It would seem that the voice packets are not finding their way through to 3CX, so... (without seeing your entire network set-up) my first guess would be some sort of firewall, or perhaps a router problem. For testing purposes, you may want to disable any firewalls temporarily and eliminate anything (in the 3CX server PC) that may cause this blockage.

    When you restart 3CX, are you re-booting the PC/Server, or just stopping and restarting the 3CX programme?
     
  3. Sergiy

    Joined:
    Dec 12, 2011
    Messages:
    15
    Likes Received:
    0
    Generic VoIP provider.

    The problem begun appear after I had moved the 3CX to another server (virtual machine), at the same time the VP530 was connected as external client (TLS+SRTP). And one more detail is that external client doesn't work too when the problem arises.
    3CX server connected with LDK over LAN.

    Firewall settings on server:
    3CXPhoneSystem.exe ALLOW
    UDP 9000-9049 ALLOW

    Just restarting 3CX services.
     
  4. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    In log - both calls are processed in "by pass" mode. Both, provider and phone are in the same network. Provider configuration is not "Generic VoIP provider". Template was "Generic VoIP provider" but configuration was modified.
    "by pass" means that devices are talking directly. PBX does not participate in this process.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Sergiy

    Joined:
    Dec 12, 2011
    Messages:
    15
    Likes Received:
    0
    I understand what you talking about, but I just say facts. Seem the problem is gone after restart server (Windows).
    What ever it was, 3CX participates in this process, maybe codec negotiation or something else - I don't know. If problem with symptoms that I described not first experience, then I can send you logs.
     
Thread Status:
Not open for further replies.