locked
Exchange will not Receive Fax RRS feed

  • Question

  • I've got Exchange working wonderfully with OCS 2007 R2, but I can't get it to answer a Fax Call.

    Using an Audiocodes Mediant 1000, I route all fax extensions directly to the Exchange UM server where I created a separte dial plan just for faxes.  Added the additional extensions to each user.

    I can see from syslog traces on the Mediant 1000 that the fax calls are getting routed directly to the Exchange UM server.  But the call is not connecting through.

    I have set all parameters up according to the Audiocodes instrutions for this setup.  I'm trying to figure out whether I have an Exchange issue or A gateway issue, or both.

    I believe I have Exchange setup correctly to receive faxes.
    Monday, June 22, 2009 10:51 PM

Answers

  • Documentation and Books, and apparently this forum are pathetic when it comes to UM and Hunt Groups.

    Docs and the book MS Exchange Unleashed talk about PBX's and then barely cover the details of what Exchange Does with Hunt Groups.

    Exchange Unleashed tells you to delete the Default Hunt Group that gets created when you create a UM IP Gateway.  Nonsense.  If you do that you will not be able to create another Hunt Group using the Exchange Console if you want a "Blank" Pilot ID.

    The Pilot ID directly links the Gateway to an extension and frankly I don't see what the stupid hunt group is for, because if you don't have a "blank" piolot id you will have to have a hunt group for every extension you want Exchange To answer a call for.  If you just want to only allow callers to call say an auto attendant and/or a subscriber number, then fine...

    BUT if you want to be able to call any extenstion, you will have to have a Hunt Group with a blank Pilot ID.

    I see this form does not get much attention either.  I suppose not that many people are using Exchange UM.  We find it wonderful.

    Oh well.  Now there is a thread about Hunt Gruops for some other poor slob like me that may have the same problem (or perhaps for one that is as ignorant is me?).

    -Barry
    • Marked as answer by Barry Adkins Thursday, June 25, 2009 8:22 AM
    Thursday, June 25, 2009 8:22 AM

All replies

  • Syslog shows the UM is rejecting the call.

    The event log says:

    The Unified Messaging server rejected an incoming call with the ID "1097716665236200924747@10.0.0.1". Reason: "The Unified Messaging server cannot find a valid UM hunt group for "2603" associated with UM IP gateway "10.0.0.1"."

    There is a hunt group configured for that gateway with a Pilot ID of 2600.  Perhaps I don't understand the "Pilot Identifier".  There is obviously a problem with the UM coniguration, but I know it has to be a simple thing, because in the first place the configuration for this is not much to do.

    -Barry

    Tuesday, June 23, 2009 8:18 AM
  • If I create a Hunt Group that has the extension I am calling as the Pilot Identifier, then the call goes through.  This is however not a practical situation, as it would be ridiculous to create a hunt group for each extension.

    My understanding of Hunt Groups was that for all 4 digit extensions beginning with 26, could be covered by a Hunt Group with the Pilot ID of 2600.

    Please, someone pitch in.  I've searched the docs and get no appropriate hits.

    Since the hunt group thing seems to discuss the Pilot ID as relating to the "PBX" I'm going to try to come up with a pilot ID that relates to the Media Gateway (Mediate 1000).

    Still fishing, getting some bites, but I'd appreciate a fishing guide...

    -Barry
    Tuesday, June 23, 2009 7:52 PM
  • Documentation and Books, and apparently this forum are pathetic when it comes to UM and Hunt Groups.

    Docs and the book MS Exchange Unleashed talk about PBX's and then barely cover the details of what Exchange Does with Hunt Groups.

    Exchange Unleashed tells you to delete the Default Hunt Group that gets created when you create a UM IP Gateway.  Nonsense.  If you do that you will not be able to create another Hunt Group using the Exchange Console if you want a "Blank" Pilot ID.

    The Pilot ID directly links the Gateway to an extension and frankly I don't see what the stupid hunt group is for, because if you don't have a "blank" piolot id you will have to have a hunt group for every extension you want Exchange To answer a call for.  If you just want to only allow callers to call say an auto attendant and/or a subscriber number, then fine...

    BUT if you want to be able to call any extenstion, you will have to have a Hunt Group with a blank Pilot ID.

    I see this form does not get much attention either.  I suppose not that many people are using Exchange UM.  We find it wonderful.

    Oh well.  Now there is a thread about Hunt Gruops for some other poor slob like me that may have the same problem (or perhaps for one that is as ignorant is me?).

    -Barry
    • Marked as answer by Barry Adkins Thursday, June 25, 2009 8:22 AM
    Thursday, June 25, 2009 8:22 AM