locked
Um Hunt Group and PilotIdentifier RRS feed

  • Question

  • Hey there,

    I started to trace how the Skype and E2013 UM are really working together and instead of having messy Exchange organization with multiple IP gateways by ps1 script I started to setup the UM connectivity with my own.

    Current status is:
    Test-CsExUMConnectivity
    Result        : Success
    Latency       : 00:00:00.0520990

    So it is working   \o/

    But during the setup I found out that UM Hunt Group should be defined like:
    New-UMHuntGroup -Name HuntGroup01 -UMIPGateway SkypePool01 -PilotIdentifier ExchDialPlan01 -UMDialPlan ExchDialPlan01

    While reading the "new-UMHuntGroup" defination for PilotIdentifier, it says:

    "The PilotIdentifier parameter specifies the number string used to uniquely identify the pilot access number for the specified IP gateway. This number must match the subscriber access number configured in the UM dial plan.
    Required?                    false"

    Perhaps my English is not the most perfect, but I read above so it can be basically what ever as long as it makes unique object together with hunt group name.

    But that was not correct, as while testing I realized that UM is not working with Skype until PilotIdentifier (mine: ExchDialPlan01) is same than UM Dial Plan name (mine: ExchDialPlan01).

    If these do not match, then UM reject the calls by:
    Log Name:      Application
    Source:        MSExchange Unified Messaging
    Event ID:      1647
    Task Category: UMCallRouter
    Level:         Error
    Description:
    The Microsoft Exchange Unified Messaging Call Router service rejected the call for the following reason: 15601;source="E2013srv01.domain.com";reason="The Unified Messaging server cannot find a valid UM hunt group associated with the UM IP gateway. Pilot number: ExchDialPlan01. UMIPGateway: SkypePool01.domain.com."

    The last part of the help text says: "This number must match the subscriber access number configured in the UM dial plan." and I found this article [Configure a Subscriber Access Number on a UM Dial Plan]. But if I do have access number: "+123456789" and PilotIdentifier also: "+123456789" I still get above error message.

    So how the PilotIdentifier really should be populated and for what purposes that is needed?


    Petri

    Tuesday, March 21, 2017 8:48 PM

All replies

  • The Exchange UCUtil Script do some more configuration steps.

    If you want to do this manual the PilotIdentifier sholud be the name of your DialplanName.

    The PilotIdentifier will use for the created Dialplan.


    regards Holger Technical Specialist UC


    Sunday, April 30, 2017 11:18 AM
  • Thanks Holger,

    By your answer, do you mean the description on the TechNet is incorrect?


    Petri

    Friday, May 5, 2017 1:52 PM
  • From my experience, yes, because in my environments the pilotidentifier is always the name of the Dialplan.

    regards Holger Technical Specialist UC

    Wednesday, July 12, 2017 4:54 PM