BCM50 SIP trunking to a hunt group 1

[adamandamy]

I have 2 BCM50s linked together with SIP trunks with MCDN on each machine. I want to take calls from Target Line XXX on Site A and after three rings and forward to a broadcast huntgroup on Site B.
I can't change the DN of the huntgroup on Site B to match the extensions and there are no free active DNs to come up with a forwarding arrangement. I'm looking for the path of least resistance.
TIA

 

[oldestgeek]

No need to change the huntgroup DN. Build a route for whatever DN it already is. If it conflicts, just add an unused digit as a route code and strip it off in the route. Or change it to one of the application DNs and change whatever it conflicts with at the local side.

 

[adamandamy]

THankyou very much for the idea.
So I can build the route on Site A that sends the hunt group DN (397) across the SIP trunks to Site B but how does Site B route the call to the hunt group without a target line.

 

[oldestgeek]

Add the target line with 397 as the received digits (private if you're using MCDN, public if you're not) to the hunt group in the same place where you assign the sets to the hunt group. You should also make the prime set for the target line is 397 as well.

 

[adamandamy]

I had actually tried doing that before I posted last time (I should have mentioned it).
The target line parameters won't allow the HG DN to be the prime set or the Priv. Rec'd number or change the line type parameter to DN:397

 

[oldestgeek]

OK, try this. On the main site system, pick out any unused number that doesn't conflict with your existing dial plan, say for example "500". Set that up as a destination code and point it to the VoIP route with no digit stripping. At the remote pick an unused target line and assign 500 as the received digits. Go to HG 397 and add your sets and that line. You should be able to dial 500 from the main site and ring the hunt group. Now all that is remaining is setting up the forwarding after three rings. If you're not using MCDN, you'll have to turn on "redirect allowed" at the forwarding set since the route class will be public.

 

[adamandamy]

That seems to work well. Thank you so much for your time and advise.

 

[adamandamy]

quick follow up question

I have the target line for the HG configured in a ring group to immediately forward to the AA if the control set puts the system into night mode but for whatever reason it doesn't want to work.
What could I be missing?

TIA

 

[oldestgeek]

In the target line properties, make sure the set with the night button is programmed as the control set for the target line. Set up a greeting table to answer the line when night service isn't on after 10 rings or so to give the hunt group members a chance to answer during normal mode. Does the night service work for other lines?

 

[adamandamy]

yes it works for the other lines and the target line I used was already part of that ring group. I did need to change the control set on the target line but it didn't help in the immediate forwarding of the line to the ring group.
I'm thinking when I made the change to the control set on the TL, the system was already in night mode and needs to be un-engaged and re-engaged to become effective.