Hunt Group Forwarding Across SCN

[BetterWithAV]

Hey guys,

I have 2 IP500's both running 4.2(4) connected across a SCN with a T1. The remote site has a huntgroup that I set out of service using button programming and then I have a Out of Service huntgroup set up that forwards back to the host site. Originally, I had button programming set up at the host site that also set the remote site hunt group out of service. Somewhere, somehow, the program got screwed up. When you activate the button programming at the host site, it actually clears the out of service huntgroup field in the programming for the remote site.

Has anyone even seen anything like this? This is really driving me crazy and Avaya can't seem to find a fix. Does anyone have any thoughts or at least a work around that I could use?

I know my explanation is a little confusing, let me know if you have any questions

Thanks all.

 

[piethief]

are the hunt groups the same number at both sites?

 

[IPXTech]

Are you sure the button that is programmed as Set > Set HuntGroup Out of Service? There are a few other button options that could be mucking with it. There's also Set Out of Service Group, and there is also Call > Clear HuntGroup Out of Service.

That would be the first thing I'd check, anyways..

 

[BetterWithAV]

Hunt group numbers are unique and the button programming is truly "Set HuntGroup Out of Service". The hunt group goes out of service just fine, the problem is that pressing that button clears whatever i have selected from the pulldown menu for my fallback huntgroup.

Avaya told me i had a corrupted program so i reprogrammed the entire thing from scratch but the problem still remains.

 

[Westi]

do you use centralized voicemail for the sites?
if yes then you could use the voicemail and a user variable to send the calls to the hunt group or to the night target. You could use the same shortcode on both systems to set the condition on or off so if the one side forgets you could do it from the other and users would not have to rethink where they are and what they want to do.


Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[3Sixty]

Do you need the advanced version of SCN for this funtion maybe? or is that what you have.

Marshall

 

[tlpeter]

I think you do


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[BetterWithAV]

I don't know if the advanced license is needed or not, but i do have it regardless.

 

[tlpeter]

Then recreate the button
If that does not help
you can export the config and default the system and import it back in


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[BetterWithAV]

Still no joy. I defaulted both systems, redownloaded 4.2 from the Avaya site, and reprogrammed both systems (it was a fun weekend) from the ground up. I still have the same problem.

Is anyone else running SCN that could test this? My systems can't be the only ones that are having these problems but i'm guessing very few other people are putting huntgroups out of service from the other side of a SCN.

 

[3Sixty]

Can I ask can you see the huntgroup at the remote IP office to set as the Out Of Service Group. Can you also test if you can overflow to this group to confirm your SCN setup is working still. I am guessing you have enabled the check box that says publish this hunt group or something like that.

 

[piethief]

Try a short code that dials across the network to a shortcode at the other site. The button won't show status but it might get the job done.

 

[Notsetinstone]

post both configs

http://www.nu-tel.com