Hi,
What is is the difference between static patch and dynamic patch , included in ALU OXE R9.1 software. And how far the pathes are important to the OXE system?
Regards,
Zoheb
Alcatel Patches Information
the main difference is Static patches can only be loaded to the inactive partioion or a shutdown system (tel not running) but dynamic patches can be loaded to the system while running.
All patches contain either bug fixes or new features.
depending on your requirements the patches may be needed or not.
in each patch ther are release notes with details of fixes. check the readme in the patch for details.
All patches contain either bug fixes or new features.
depending on your requirements the patches may be needed or not.
in each patch ther are release notes with details of fixes. check the readme in the patch for details.
Best Regards
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
Tnks for the information. So u mean to say that dynamic patches are loaded for fixing some specific issues when the system is running. And static patches are reqd for fixing critical issues , after stoping the telephony application.
But let me ask u , How will I put these patches the system? Is it using PC installer software ?And also at the time of new installation should I need to install the following software for realese 9.1 ?
Regards,
Zoheb Hussain
"OXE R9.1 Software - I1.605.16.c version (including complete version, static and dynamic patch)"
But let me ask u , How will I put these patches the system? Is it using PC installer software ?And also at the time of new installation should I need to install the following software for realese 9.1 ?
Regards,
Zoheb Hussain
"OXE R9.1 Software - I1.605.16.c version (including complete version, static and dynamic patch)"
IP phone redundancy
One of my customer's IP phone (4028 series) is registered with local site Common Hardware CS. They have one more system located in remote location. They want geographical type redundancy , suppose if the local site CS fail , IP phones will get registered with the remote one. So is it feasible ?
Any help will be appreciated .......
Regards,
Zoheb Hussain
Any help will be appreciated .......
Regards,
Zoheb Hussain
Is the second site a remote shelf or a second node? if it is a remote shelf the best may be a redundant cs located at the remote location. this is called spatial redundancy. If it is a seperate node then maybe you look into ip centerliasion to achive this. another option could be to set up th e ipp's with sip fallback and setup sip extn's at the second site for them.
Whenever I install a new system I always put the latest version on prior to go live testing.
Whenever I install a new system I always put the latest version on prior to go live testing.
Best Regards
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
As the ipp registers to only one node I don't know how you would get it to resgister to the second if the first site goes down.
The ony way I see it working is..
1: in the 1st site set up the ip domain with the ipp's as sip survivabilty.
2: set the second node address as the sip gateway.
3: in the second site create sip extns for each ipp in the 1st site (these extns are completly seperate from their normal ones) you could make some relationship like normal extn 8xxx sip extn 98xxx.
you will of course need sip licenses in the second system for this.
how I think it would work.
ipp powers up on site 1. settings set from domain sent to ipp containing sip backup address details of site 2.
if site 1 goes down ipp reboots and cant see site 1 so goes into backup mode (sip) and registers to site 2.
ipp can call users on site 2, dial out from site 2 trunks. normal users on site 2 can ring ipp's by dialing 9 then the normal number (if the extns above are used).
could be interesting if anyone wants to try it.
2nd option could be to get your presales guys to look at ip centerliastion. (join 2 nodes into 1). if both systems have say 1 cs you could configure them as spatial redundancy so 1 cs is kept at each site.
why this option?
1: if wan down both sites work stand alone
2: either cs fails both sites work as normal (no issues seen by customer).
take your pick but at least there is options.
The ony way I see it working is..
1: in the 1st site set up the ip domain with the ipp's as sip survivabilty.
2: set the second node address as the sip gateway.
3: in the second site create sip extns for each ipp in the 1st site (these extns are completly seperate from their normal ones) you could make some relationship like normal extn 8xxx sip extn 98xxx.
you will of course need sip licenses in the second system for this.
how I think it would work.
ipp powers up on site 1. settings set from domain sent to ipp containing sip backup address details of site 2.
if site 1 goes down ipp reboots and cant see site 1 so goes into backup mode (sip) and registers to site 2.
ipp can call users on site 2, dial out from site 2 trunks. normal users on site 2 can ring ipp's by dialing 9 then the normal number (if the extns above are used).
could be interesting if anyone wants to try it.
2nd option could be to get your presales guys to look at ip centerliastion. (join 2 nodes into 1). if both systems have say 1 cs you could configure them as spatial redundancy so 1 cs is kept at each site.
why this option?
1: if wan down both sites work stand alone
2: either cs fails both sites work as normal (no issues seen by customer).
take your pick but at least there is options.
Best Regards
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data
Murray
ACSE 10.0 corporate
ACSE 6.x IPT data