3CX and IPKall - no audio

Discussion in '3CX Phone System - General' started by dsummer, Jan 31, 2012.

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

    Joined:
    Dec 6, 2010
    Messages:
    13
    Likes Received:
    0
    Hi all. I'm having trouble setting up 3CX for personal use to work with IPKall. I have never setup a PBX before and only use 3CXPhone on a regular basis.

    3CX Phone System 10 (SP5) is installed on a Win 7 server and 3CXPhone 5.0.14900 is installed on a Win 7 desktop. Both are within the same LAN and the firewalls of the router and individual systems are configured properly. Firewall Checker completes successfully.

    From what I understand, I created a new trunk for IPKall using the VOIP Provider Wizard and Generic VoIP Provider template. I specified the IPKall IP address under the 'SIP server hostname or IP' field and left the 'Outbound proxy hostname or IP' field blank. Secondly, I added an extension 100 and assigned a password to it. This allowed 3CXPhone to login to 3CX. Thirdly, I went to Settings > Advanced, checked 'Allow calls to external SIP URIs' to allow direct SIP calls, and specified a dynamic DNS hostname in 'Local SIP domain'.

    When I call my IPKall number, it rings successfully and connects. However, there is no audio in either direction.

    I think there is some setting I must have missed. Could someone kindly help me?

    Here are the entries from the server activity log for an inbound call:

    Code:
    05:19:20.065  [CM503008]: Call(6): Call is terminated
    05:19:16.071  Currently active calls - 1: [6]
    05:19:10.283  [CM503007]: Call(6): Device joined: sip:100@192.168.1.11:58506;rinstance=ce15287735fc1a3f
    05:19:10.283  [CM503007]: Call(6): Device joined: sip:100@66.54.140.46:5060
    05:19:04.075  [CM505001]: Ext.100: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone 5.0.14900.0] PBX contact: [sip:100@192.168.1.10:5060]
    05:19:04.075  [CM503002]: Call(6): Alerting sip:100@192.168.1.11:58506;rinstance=ce15287735fc1a3f
    05:19:03.919  [CM503025]: Call(6): Calling Ext:Ext.100@[Dev:sip:100@192.168.1.11:58506;rinstance=ce15287735fc1a3f]
    05:19:03.872  [CM503004]: Call(6): Route 1: Ext:Ext.100@[Dev:sip:100@192.168.1.11:58506;rinstance=ce15287735fc1a3f]
    05:19:03.872  [CM503010]: Making route(s) to <sip:100@192.168.1.10:5060>
    05:19:03.872  [CM505003]: Provider:[IPK] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [IPKall] PBX contact: [sip:100@98.207.98.182:5060]
    05:19:03.856  [CM503001]: Call(6): Incoming call from 2066820185@(Ln.10000@IPK) to <sip:100@192.168.1.10:5060>
    05:19:03.856  [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,855
    Likes Received:
    301
    No audio issues is almost always the result of the voice packets being blocked by either a router or firewall.

    I question this port number, where did it come from?

     
  3. dsummer

    Joined:
    Dec 6, 2010
    Messages:
    13
    Likes Received:
    0
    Hi leejor. Thank you for your reply.

    The WAN ports that are open on the router to the server are 5060 TCP+UDP, 5090 TCP+UDP, 7000-7499 UDP, and 9000-9049 UDP.

    I believe that port number is a listening port randomly opened by the 3CXPhone application. If I run the command 'netstat -a -o -n', I have these lines for the process ID of 3CXPhone.exe:

    Code:
    Active Connections
    
      Proto  Local Address          Foreign Address        State           PID
      TCP    0.0.0.0:52633          0.0.0.0:0              LISTENING       3324
      TCP    0.0.0.0:52634          0.0.0.0:0              LISTENING       3324
      UDP    0.0.0.0:52633          *:*                                    3324
    which seems to match the server log for another test call:

    Code:
    00:42:54.172  [CM503016]: Call(9): Attempt to reach <sip:100@192.168.1.10:5060> failed. Reason: Busy
    00:42:47.449  Currently active calls - 1: [9]
    00:42:43.065  [CM503002]: Call(9): Alerting sip:100@192.168.1.11:52633;rinstance=c17a31dcfb0d9c6c
    00:42:42.862  [CM503004]: Call(9): Route 1: Ext:Ext.100@[Dev:sip:100@192.168.1.11:52633;rinstance=c17a31dcfb0d9c6c]
    00:42:42.862  [CM505003]: Provider:[IPK] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [IPKall] PBX contact: [sip:100@98.207.98.182:5060]
    00:42:42.847  [CM503012]: Inbound out-of-office hours rule (unnamed) for 10000 forwards to DN:100
    00:42:07.903  [CM503016]: Call(8): Attempt to reach <sip:100@192.168.1.10:5060> failed. Reason: Busy
    I'm stumped. I'm beginning to understand why most people just forward IPKall to a SIP provider. :(

    Thank you,
    Eugene

     
  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,855
    Likes Received:
    301
    I have it working just fine, send directly to my DynDNS URL. I haven't opened any ports beyond the "normal" ones used by 3CX. You might try a different router as some (especially the more "complicated") don't play well with SIP some times.

    You could try bypassing your router and (for a short test) let the 3CX server pick up a public IP. If that worked, then you know you have a router issue. Are you positive that there are no firewall programmes running?
     
  5. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    "Verbose" log may provide more information. It contains entries which are describing "media" part of negotiations.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.