Exchange UM Integration

Discussion in '3CX Phone System - General' started by Anonymous, May 19, 2007.

  1. Anonymous

    Anonymous Guest

    Has anyone run into this issue when trying to integrate 3CX with Exchange UM:

    When I try to start the Exchange Unified Messaging Service, I recieve the following error in the event log

    Event ID: 1038
    The Microsoft Exchange Unified Messaging service was unable to start. More information: "The service was unable to start listening for SIP calls. The connection manager was unable to listen using the address and port supplied."

    Can't figure this one out. Could it be an authentication issue?

    Brian
    http://www.jaydien.com
     
  2. Alexander

    Joined:
    Nov 10, 2006
    Messages:
    73
    Likes Received:
    0
    Hi Brian !

    I think the 5060 port of the machine where MS Exchnage has been installed is used by some software. The most probable candidates are SIP-phones, SIP PBXs (including 3CX PBX).

    To see the ports opened by applications use the "netstat -a -b" command from command string. This command displays PIDs (identifiers) of processes which opened ports. To get a process information by PID, use the "tasklist" command.
     
  3. Anonymous

    Anonymous Guest

    Sounds right. My current configuration is as follows:

    Windows Server 2003 Ent x64
    Excahnge 2007 Ent x64
    3CX Enterprise
    2 Cisco 7960 IP Phones (Using port 5060)

    When I run the netstat -b -a command, there are two entries for port 5060:

    TCP ippbx:5060 ippbx.exchange07.local:0 LISTENING 3272
    [3CXPhoneSystem.exe]

    UDP ippbx:5060 *:* 3272
    [3CXPhoneSystem.exe]

    Should I change the ports that 3cx uses? Thanks for your assistance.

    Brian
    http://www.jaydien.com
     
  4. Anonymous

    Anonymous Guest

    Quick update:

    I changed the SIP port in 3CX to 5070 and I was then able to start the service. I still left the exchange integration port as 5060. Is this normal behavior? Should I keep my configuration like this?

    Brian
    http://www.jaydien.com
     
  5. Alexander

    Joined:
    Nov 10, 2006
    Messages:
    73
    Likes Received:
    0
    Hm... so you have MS Exchange and 3CX PBX installed on the same machine. Frankly we did not test such configuration, because MS Exchange implies external PBX to be installed on different machine (or it's a hardware PBX with its own IP).

    It's ok if you changed 3CX PBX port from 5060 to 5070. The question is will MS Exchange accept calls from 3CX PBX ? In the MS Exchange console you can define just IP of external PBX, but not its port.
    Please try, probably it will :)
     
  6. Anonymous

    Anonymous Guest

    In my configuration, I specified FQDN instead of IP address in both Exchange and 3cx. The connection seems to be established between 3CX and exchange. I can make calls between extension no problem but when the call goes to voicemail, it just drops.

    Here is what the log shows in 3CX:

    08:36:19.093 StratLink::eek:nHangUp Call(C:2): MSExchIVR.SpecMenu(999) hung up call; reason: BYE

    08:36:17.562 MediaServerReporting::DTMFhandler from 'ippbx:0/MediaServer':DTMF (in-band) from 192.168.0.2:20776 detected.

    08:36:16.828 CallLegImpl::eek:nConnected Call(C:2): Created audio channel for MSExchIVR.SpecMenu(999) (192.168.0.2:20776) with Media Server (192.168.0.2:7006)

    08:36:16.796 StratInOut::eek:nConnected Call(C:2): Setup completed for call from Ext.101 to MSExchIVR.SpecMenu(999)

    08:36:16.796 CallLegImpl::eek:nConnected Call(C:2): Created audio channel for Ext.101 (192.168.0.222:26356) with Media Server (192.168.0.2:7004)

    08:36:16.734 CallConf::eek:nProvisional Call(C:2): got response from 999
    08:36:16.515 CallConf::eek:nIncoming Call(C:2): Incoming call from Ext.101 to sip:104@192.168.0.2

    Exchange Log:
    The Application log had Error 1128:

    No operator extension number has been configured for the UM auto attendant named "Day AA", or for the Dial Plan to which it belongs. Therefore, incoming calls received by this UM auto attendant cannot be transferred to the operator.

    I set extension 101 as the operator in Exchange and now all calls are fowarded to operator when the voicemail for an extension picks up????

    Brian
     

Share This Page