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!

 

[amriddle01]

Sounds like you may have a corrupt config(s), that often accounts for such oddities

 

[Gunnaro]

Let me see..
- A phone located at site B (logged in to Site A) can't trigger the relay, but a phone locally can?

I don't think the configuration on the SCN is incorrect because I can run other short codes over the SCN and I can't even get a DID with a call route to a user with unconditional forward to work

- Contradictory statement.

I'd say there's something fundamentally wrong with the setup or firmware.

Put the config up here, let's have a look at it.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[Gunnaro]

Oh, wait a minute..."Site A has a VMPro server (Version 7.0) locally. I have site B (IP 500 V2 8.1)"

Did you try lowering the R8.1 to same level as the Main system?
This might be the issue, even though Avaya says they are supporting 1 major release difference.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[tlpeter]

Gunnar, 7.0 and 8.1 are two major releases so this is not supported anyways.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Gunnaro]

Not according to the Avaya docs

"In order to understand which product releases will be supported, it is important to understand the numbering scheme for Avaya products.
A product release is generally represented in the following manner:
<Name of the Solution> followed by N.Y(Z), where N= Major Release, Y= Minor, and Z= Update."


IP Office N.Y.(Z)
IP Office 7.0.(5)
IP Office 8.1.(85)

So it should work, but I wouldn't be surprised if OP's feature is not working due to inter-release issues.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[tlpeter]

7.0 is a major release and 8.0 too.
But you are right .1 should be a minor release.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Gunnaro]

The docs also say this about SCN in inter-release config:

"This option is intended mainly to allow the phased upgrading of sites within a Small Community Network. It is still recommended that all systems within a network are upgraded to the same level where possible. Within a Small Community Network including differing levels of software, the network features and capacity will be based on the lowest level of software within the network."


The last part is important. for instance VMPro has to be R7.0.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

First, thank you for being persistence!! Second I forgot to mention I bought an upgrade license (small 8.1 and I think the last one Avaya sold!!). Avaya no longer sells them as of 2 weeks ago. So both site A and site B are running V8.1(85). I drew a picture (attaching), hard for me to explain without a drawing.

Only the IP Phone (licensed at site A) and any stations at site A, can open the door at site A.
Same hold true about site B, only the stations at site B can open the door at site B.

This is my ultimate goal: as shown in the picture (at site B) there is a “door phone” and when someone walks up to the door phone it auto calls a Auto-attendant (?D/dial) (which works great) and asks the call to type in extension or press “0” for an operator. But I would like to add is the ability for a tenant to enter a code that opens the door in case they locked out themselves out.
Now here comes the issue. Because I am running a SCN only one VM Pro server is allowed (which I am fine with) so the auto attendant lives at site A (where the voicemail pro server is located), so when to tell the voicemail pro server to open the door it actually opens the door at site A. That one took me a while to figure out. I was standing outside at the door phone (at site B) and entering my code to unlock the door. Nothing was happening, I tried 30 times. Then someone from site A called and said there was a problem with their door, it keeps buzzing on its own.
So I want to add a user (or something) that the voicemail pro at site A can use to open the door at site B.

Update:

Both units were downgraded back to 7.0 and then defaulted. I applied all the licenses, made a few call then upgraded to 8.1, then finally up to 8.1(85). I am still having the same problem as before.

Here is another thing I tried (mention in my last post). I changed a user on site A that unconditionally forward to *41, and created an incoming call route to that user. When I dial the number, the extension does NOT ring, but will go to the user’s voicemail. If I call the user from another extension, (just hitting the users extension) the door starts the buzz. I tried this at site B as well, but I get the exact same results.

Not sure if PDF is attaching correctly. So here is another link to the PDF file

http://www.tbitservices.com/IPO_Help.pdf

Thanks again everyone!!

 

[Gunnaro]

Small upgr R8.1? Then you're fu@@ed.
Can't use that for SCN systems.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

Both sites A and B combined I don't have more than 32 users or extensions.

 

[Gunnaro]

Then take a look at the doc's.
SCN needs Large upgr lic's, even if you have only 2 users combined.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

I don’t have a problem buying a 9.1 large upgrade, but I feel it will not help.

Correct me if I am wrong but:

Reason 1:
My configuration WAS as followed:
Site A had:
7.0(69)
Site B had:
8.1(85) with a large upgrade.
The short code 41 did not work, all other short codes did.

The systems are NOW as:
Site A has:
8.1(85) with small upgrade
Site B has:
8.1(85) with a large upgrade.
The short code 41 still does not work, all other short codes do.

Reason 2:
All other functions (transfer, incoming calls routing through the SCN, and ARC rules to use remote IPO’s lines trunk lines for outside calls, hunt groups that include member from both location, paging, hot desking, etc) and all other short codes work except *41

Reason 3:
Even after Site B (with large 8.1 upgrade) was defaulted and then upgraded back to 8.1 and for now not included into the SCN, I created an incoming call route to a user that had unconditional forward to *41, but that didn't even work. Other extension from site B that dial the user (that is forwarded) would open the door. I then added site B back into the SCN and all short codes across the SCN as described above work except 41.

So again, correct me if I am wrong, but I don’t think upgrading Site A to a large would help.

Thanks again!!

 

[Gunnaro]

Post the configs, I'll replicate it in my lab. Let's get this settled once and for all

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[amriddle01]

It's either the licence or you're doing something wrong or corrupt config(s), post your config(s) with sensitive data changed and that will narrow it down to 2 or it'll be fixed

 

[TBITservices]

sensitive data" No name are in the config, but do you want me to remove the dongle serial number and licenses?

 

[Gunnaro]

Dongle number is not sensitve, can't do any harm with that

No full names, pwds, public IP (if you're that insane running free on the internet) or mobile numbers (especially not twinned mobile numbers)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[TBITservices]

Sounds good to me.. Thanks Gunnaro I have attached my Site B config

 

[TBITservices]

I will post site A soon

 

[TBITservices]

This is site A config file. I save this one as a Binary.

Thanks again!

 

[TBITservices]

When you import the file (site A) you will get "Essential License is not present" (at least I did) but the IPO does show the license.