The limitation of the wake up call of eZ32-2 board.

Post Reply
User avatar
wolfgar
Member
Posts: 59
Joined: 19 Jul 2007 21:08

The limitation of the wake up call of eZ32-2 board.

Post by wolfgar »

Hi

We have an issue of the wake up call on our customer due to the limitation of the eZ32 board.
This is hotel customer and they have over 1000 guest rooms in their hotel.

We been completed to install OmniPCX Enterprise with R12 to this hotel with an external voice mail via SIP.
An external voice mail is provided by FCS. Its FCS Phoenix.
And the wake up call is done by FCS Phoenix not by OXE. We have the license about 32ch for the connection between FCS Phoenix.
We confirmed it works good on our test. But the issue is happened when we set the wake up call more than 8 guest rooms on the same eZ32-2.

For example, if there are guest room ext68800 to 68815 on the same eZ32-2 board and then we set the wake up call on the same time, only 1st 8 extensions will have the wake up all, and other 8 extensions don't have it.

But it shows "answered" on the report of FCS. It seems that OXE has been sent same reply to FCS Phoenix in the case of OK or NOK scenario.

My question is,
1. Is it possible to ring wake up call more than 8 ports simultaneously by using anyway?
2. If its not possible, how we let FCS know it had been failed due to the limitation of eZ32-2 board?

I know it should be difficult. But I really don't understand why eZ32-2 has such a stupid limitation. It doesn't make sense..
If it has such a stupid system limitation, we can not sell OXE to big hotel at all..

Best Regards,
User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7014
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:

Re: The limitation of the wake up call of eZ32-2 board.

Post by cavagnaro »

I would rise that question to your pre-sales guys...and also open an eSR if such limitation exists or is a problem...

Your question is about a specific integration. Hopefully someone will have some idea

Enviado de meu E6633 usando Tapatalk


Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
User avatar
alex
Senior Member
Posts: 1457
Joined: 06 Jul 2004 07:27
Contact:

Re: The limitation of the wake up call of eZ32-2 board.

Post by alex »

Actually it's all written in "product limits document"

Code: Select all

3.1.2.1. STANDARD FEATURES											
	Simultaneous ringing on Z interfaces per :										
		S rack in eMG			6	6	6	6	6	6	6
		L rack in eMG			20	20	20	20	20	20	20
		Z board in ACT			8	8	8	8	8	8	8
	Simultaneous ringing on UA interfaces				NL	NL	NL	NL	NL	NL	NL
	Ringing hierarchy levels				254	254	254	254	254	254	254
Clearly a board's power supply can't provide a current required for simultaneous ringing on all interfaces of the board.
Also< from the System docs:
Wake-up and analog lines
To avoid overloading analog boards, the system does not ring more than n sets
simultaneously (in the case of group wake-up). Wake-up for the other sets is then deferred by
1 min.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Post Reply

Return to “Application”