Jump to content
Vodia PBX forum
Doug

Exchane UM calling Hunt Group does not work

Recommended Posts

We are evaluating pbxnsip. We have pbxnsip, Exchange 2007, and OCS R2 working together. Basic calls, UM AA routing, message taking etc work great.

 

We need to have a selection from the Exchange UM AA call a hunt group in pbxnsip. We need call the hunt group because we want to call multiple extensions in pbxnsip and use the "Service Flag" to do the calls based upon time of day.

 

We have no problem calling regular extensions from UM.

 

We had to enter a dial route of the 111 to be an "Call Extension" otherwise the call would go out the default trunk instead of being processed by pbxnsip.

 

But when we try to route icalls to a hunt group number, we get an error indicating the number

 

[5] 2009/04/19 10:09:57: Dialplan Standard Dialplan: 111 goes to extension

[5] 2009/04/19 10:09:57: Could not start call to extension 111 because there is no registration or the extension is busy

 

If we route the call to an extension that then forwards the call to the hunt group we get the same problem.

 

We actually could do part of what we want to do if an extension could use a "service Flag" to ring based upon time of day but that doesn't seem to be an option.

 

If we route the inbound trunk to a pbxnsip AA, all works fine. If we even route the inbound trunk directly to the hunt group it works fine. It seems to only be an issue when the inbound trunk comes into pbxnsip then routes to the Exchange AA, then back to pbxnsip.

 

Is there a way to:

 

1. have a service flag be attached to a regular extension?

2. Have Exchange UM/OCS route a call to a hunt group?

 

 

Thanks for any help.

 

Doug

Share this post


Link to post
Share on other sites
But when we try to route icalls to a hunt group number, we get an error indicating the number

 

[5] 2009/04/19 10:09:57: Dialplan Standard Dialplan: 111 goes to extension

[5] 2009/04/19 10:09:57: Could not start call to extension 111 because there is no registration or the extension is busy

 

If we route the call to an extension that then forwards the call to the hunt group we get the same problem.

 

Hmm. That simply was not envisioned... Sending a call from the dial plan to an extension was really only for an extension. We may provide you a build that also allows calling other accounts like extensions.

Share this post


Link to post
Share on other sites

With version -3.3.2.3183 and setting an alias on the hunt group 110 of +110. Calls to hunt groups are working.

 

You guys are great.

 

Thanks.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...