Cannot connect to Voicemail internally

Discussion in '3CX Phone System - General' started by DXS_Matt, Feb 12, 2009.

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

    Joined:
    Feb 12, 2009
    Messages:
    41
    Likes Received:
    0
    Hey everyone,
    I'm trying to get the free version of 3cx up and running before we purchase our Enterprise license, however I'm running into a deal breaking issue.

    First let me tell you how things are setup.
    Dedicated External IP -> Mapped to internal IP of 3cx server at 10.10.1.200 via our Juniper SSG-140
    Local clients on the 10.10.1.x subnet

    The 3cx server is up and running and I can successfully connect to other callers using the 3cx provided SIP phone client.

    However when attempting to dial 999 the softphone connects, but I never hear anything. No prompts, no error speech, nothing.

    Here is my log during the voicemail attempt.

    Code:
    11:40:02.397  [MS004000] C:1.1: (PASSTHROUGH): Can't send RTP stream to 0.0.0.0:42002 destination unreachable (298)
    11:40:02.194  [CM503007]: Call(1): Device joined: sip:999@127.0.0.1:40600;rinstance=56d95cebec142695
    11:40:02.179  [CM503007]: Call(1): Device joined: sip:102@10.10.1.92:5070;rinstance=8ef5dd3a99417397
    11:40:02.179  [CM505001]: Ext.999: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:10.10.1.200:5060]
    11:40:02.179  [CM503002]: Call(1): Alerting sip:999@127.0.0.1:40600;rinstance=56d95cebec142695
    11:40:01.694  [CM503004]: Call(1): Calling: Ext:Ext.999@[Dev:sip:999@127.0.0.1:40600;rinstance=56d95cebec142695]
    11:40:01.694  [CM503010]: Making route(s) to <sip:999@3cx.company.com:5060>
    11:40:01.694  [CM505001]: Ext.102: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Phone 7.0.4526.0] Transport: [sip:10.10.1.200:5060]
    11:40:01.694  [CM503001]: Call(1): Incoming call from Ext.102 to <sip:999@3cx.company.com:5060>
    11:39:57.913  [CM504001]: Ext.102: new contact is registered. Contact(s): [sip:102@10.10.1.92:5070;rinstance=8ef5dd3a99417397/102]
    11:39:02.891  IP(s) added:[10.10.1.200]
    
    As this is a directly mapped IP to our internal address of 10.10.1.200, there is no firewall on our 3cx server which is running windows 2003 enterprise.
    All NAT destinations are mapped directly to the internal IP.
    But the issue here is with internal callers trying to get to the voicemail system.

    Am I missing a configuration step here somewhere? We just setup the system, no other configuration has been completed as we're waiting for our SIP trunk provider to get back to us with our provisioned accounts.
    There are no inbound our outbound rules, no Digital Receptionists, call queues or ring groups.

    Any help would be greatly appreciated as we need to have a working system in place by the end of next week.

    Thanks very much,
    Matt
     
  2. DXS_Matt

    Joined:
    Feb 12, 2009
    Messages:
    41
    Likes Received:
    0
    Ok, so immediately after I finished writing the post above, I changed my connection string in the client to be 10.10.1.200 instead of 3cx.company.com.

    Why would using the IP work but using the FQDN of the server not?

    Thanks for your time,
    Matt
     
  3. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    Matt,

    It looks like the FQDN "3cx.company.com" and address "10.10.1.200" are different entities, isn't it?

    Thanks
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. DXS_Matt

    Joined:
    Feb 12, 2009
    Messages:
    41
    Likes Received:
    0
    No, internally, 3cx.company.com resolves to 10.10.1.200 on both the 3cx server and client attempting to connect, which has left me wondering why there is a difference.

    As I said before, using 3cx.company.com allows us to call other internal extensions, but not access voicemail.

    Thanks,
    Matt
     
Thread Status:
Not open for further replies.