IP Office SCN Short Code 41 problem. 2

[TBITservices]

I have 2 IPOs configured in a SCN. Site A (IP 500 V2 7.0)is the main site Site B is a new site. Site A has a VMPro server (Version 7.0) locally. I have site B (IP 500 V2 8.1)configured as Centerlized Voicemail. Everything works great except running site B's shortcode *41 (contact Closure) from Site A. Why I need this is because Site B has a Door Phone that autodials an Auto Attendant. The Auto Attendant in being done on the VMPro server at Site A. So when you configure the Auto Attendant to Open the door (Contact Closure *41 IPO Site B), it opens the door at Site A.

I have tried:
1. Creating a new shortcode *338 in Site A where it pluses relay ONE using Line Group ID 20 (an H323 line to Site B in the SCN).
2. Creating a user EXT 277 on Site B that has an unconditional forward to shortcode *41
3. Created a shortcode on site A using feature BREAK OUT using the telephone number as the IP address of Site B like this 192*186*1*12 and Line Group ID 20 and tried Line Group ID 0
4. I also tried creating a new shortcode *337 the does the same thing as shortcode *41.

The above resulted as:
In trial 1. I hit *338 and it still tries to open the door at Site A
In trial 2. If you type in the user's extension number it works fine from site B, but from site A it want to go to the user's Voicemail. I then turned off the user's Voicemail and now site A "Number Busy." From site B there was no change except after the system opens the door the extension rings busy (which is not a big deal).
In trial 3. Nothing happens, like the system is waiting for more numbers, I then press # and it says "Incompatible Disc."
In trial 4. was the same result as using the original *41 shortcode.


Any thoughts would be greatly appreciated!

 

[Gunnaro]

That's because you have virtual Essential license
I'll take a look at it as soon as I can.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

Thank you Gunnaro, please take your time! You are going way beyond, helpful!!

 

[Gunnaro]

No problem, I'll dig in when I'm home from work in 1 hour.

I had a quick look at lunch.

- SCN lines numbered the same (17)on both systems, that's bad config in SCN
- IP Route MASK 255.255.255.255 -> try 255.255.255.0
- LAN1 IP on "Tampa" system is 0.0.0.0 (That's a real show stopper), and has DCHP server activated...
- Some line numbering missing on the POTS as you call it.

Did you change that LAN1 IP before saving it as binary? (I would prefer you put it up again as CFG)


Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

Gunnaro,

I did notice that the export striped IP address, and some other things that I did not intend it to do. The LAN1 IP address should be 172.80.10.3. I think the export was not successful I will post again as a CFG

As for the SCN lines. I was trying 17 on both sides just before I exported the file. I forgot to change it back (thanks for reminding me). I had Tampa using high numbers which I thought might be a problem. Tampa line number was was 200 and outgoing group ID 201 while site B was 202 and outgoing group ID 203.

"Some line numbering missing on the POTS as you call it."
I added the DIGSTA8/ATM4 back, did restored from my original config file. and no errors and everything is working except the 41 short code. I would like to work from the config file if possible. But I was worried, like you were, about the Small 8.1 upgrade. The Avaya salesman told me that as long as there was less then 32 users or extension on that IPO I will be fine. That was the reason for removing the DIGSTA8/ATM4 card, I was not using it.

This time I saved it like I did for site B, looks like it kept the IP's.

I hope you enjoyed your lunch!!

 

[intrigrant]

I have tested it on our two systems and it works without a problem:
site A shortcode SC=*98/TN=*44/Action=Dial/Line ID = SCN line to site B
site B default shortcode SC=*44/TN=2/Action = Relay pulse/Line ID = 0

I can dial *98 on site A and the relay 2 on site B latches for 5 seconds, after dialling *98 it take a few ( dial delay timeout on SCN line A) seconds for I get the double confirmation beeps.

 

[TBITservices]

Thanks intrigrant for testing.

I am getting "incompatible" when I created the same short code as you used.

Maybe this weekend I can take site B IPO to site A (take the VPN connection out of the mess) and see if that helps any. I don't think it will help but it might be worth a try. I just don't think moving the IPO would make 1 short code start working.

 

[TBITservices]

Just as a test i changed intrigrant suggection to:

site A shortcode SC=*98/TN=*44/Action=Dial/Line ID = SCN line to site B
site B default shortcode SC=*44/TN=2/Action = Hold Music/Line ID = 0

And that works, I can hear our hold music when I dial *98 from site A

 

[Gunnaro]

File came to late, had to go for a workout...lunch was huge

I've put the first cfg in, connected it to one of my own configs and the relays work fine on puls.
Gonna try the other one you just uploaded this evening.
I'm pretty sure it works too

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

Thanks Gunnaro, I am glad you were able to finish lunch, just about to eat mine!!

Please take your time, don't waste your weekend on this!!

 

[intrigrant]

Are you sure it is the holdmusic of the remote site? Check with system status, last time I tried that I got the local MOH.
I tested the relay option by connacting a beeperto relay 2 of the remote site and then dialled the shortcode from site one.
Then I get a call from the remote site that they hearded a annoying beep several times for 5 seconds but they could not locate the source, so I kept on dialling the code until they finnally found it

 

[TBITservices]

Yeah, I did notice that the MOH were different. Site B is the Avaya default while site A is a custom WAV file. So I am sure that it is site B's MOH that I hear.

I love your beeper idea. I thought about doing the same thing, except hook up a horn on relay 2 and setting my extension as an unconditional forward to relay 2. I wonder how long before they stop trying to contact me.

 

[intrigrant]

Put the shortcode as the target in mobile twinning

 

[TBITservices]

Gunnaro or intrigrant,

Any additional thoughts? Any ideas, even remote, are always appreciated.

Thanks again guys!!

 

[Gunnaro]

Well, it worked just fine on my systems, but I did some changes to make it fit my network.

One thing though, on Tampa system> Short Code: #22#/Dial/#22#/17 -> #22#/Dial/#22#/201
(that might just fix it for you)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam