Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CM 3.0...What do I get above my G3si V.11? 3
- Thread starter NX01
- Start date
phoneguy55
Programmer
As far as I know a SI can not be upgraded to CM3.0. CM2.2 is the last upgrade for that processor and you have until Dec 15 to do that. After that date or if you want CM3.0 you are looking at purchasing a S8XX0 server.
- Thread starter
- #3
-
1
- #4
johnnydialtone
MIS
In my mind ESS is the biggest feature of 3.0. The new MedPros are better as well.
The increased meet me conferencing requires additional hardware.
The increased meet me conferencing requires additional hardware.
- Thread starter
- #5
johnnydialtone
MIS
An expanded meet-me conferencing S8500B server is required.
As well as potential additional DS1 cards, trunks......
As well as potential additional DS1 cards, trunks......
-
1
- #7
This is in line with the ESS, but its a new feature with 3.0
"as well as simplified administration capabilities that allow every gateway on a network to automatically fall back to a primary server when it is back online, without manual intervention"
and
I believe the 3.0 has an API so you can have your programmers set up programs to automatically add users and what not.
and
and
According to this you can go to specific steps in a vector.
Here is the Avaya sheet on it.
RTMCKEE
CM 2.1.1
Prologix R9.05
Modular Messaging 1.1
"as well as simplified administration capabilities that allow every gateway on a network to automatically fall back to a primary server when it is back online, without manual intervention"
and
I believe the 3.0 has an API so you can have your programmers set up programs to automatically add users and what not.
and
and
According to this you can go to specific steps in a vector.
Here is the Avaya sheet on it.
RTMCKEE
CM 2.1.1
Prologix R9.05
Modular Messaging 1.1
- Thread starter
- #8
-
1
- #9
NX01,
my two cents: from the security side, cm3 is a great leap forward. at last avaya turned its wheels and adopted ssh protocol which is available now for system administration instead of telnet, sftp for val boards instead of ftp, cms r13 now supports ssh and cti solution that is now called application enabling services also supports encryption between switch and aes server. on the voip side, encryption now supported not only for ip phones and trunks but also for media gateway signaling.
switch part: as it was said before, cm3 now supports auto fallback for h.248 media gateways without connection loss. very good one. also now it is possible to upgrade duplex (s8700) servers one after one without loss of connection. another one: locally sourced announcements and music. it means that you can use different announcements and music on the local media gateways with the same announcement extension number, switch will determine itself which one to use (you can override it, of course). ah, and now at last you can use announcement as a music on hold source! finally. another one: q.sig support for unicode. good for international use.
oh well, forgot the greatest one: mixed port network connectivity! it means that if you have s8700 multi-connect system, you can now add new epns over ip and you're not limited to fiber. very long-awaited one, that.
there are a lot of new hardware available for cm2 and cm3, especially good for remote locations, tiny to large. g150, g250 and g350 media gateways, new tn2602 medpro boards for up to 320 voip codecs, new tn793cp (programmable!) analog circuit pack, new tn2464cp ds1 circuit pack and more. can't remember it all just offhand.
by the way, trunk ports in cm3 are not counted at all. in cm2 their cost was $0.01 but customers were required to order them, in cm3 there is no part number for trunk port at all. neither for tdm nor ip. good for tandem switches, this one.
also starting with cm2 there are some features available at no cost comparing to cm1: tenant partitioning, for example, basic call center, universal license for tdm and ip users, multi-national locations and many more.
there are two long-awaited features scheduled for 3.0.1 that should be available in sep '05: ip phone signaling encryption and emergency calls from unregistered ip phones.
now to the call center part. the most visible changes in cc 3.0 are: 100 aux reason codes instead of 10 (requires cms r13 with specific software load) and more advanced variables in vectors.
huh. sorry, got tired. there are too many changes to describe in one post. life is going on and on, you know.
my two cents: from the security side, cm3 is a great leap forward. at last avaya turned its wheels and adopted ssh protocol which is available now for system administration instead of telnet, sftp for val boards instead of ftp, cms r13 now supports ssh and cti solution that is now called application enabling services also supports encryption between switch and aes server. on the voip side, encryption now supported not only for ip phones and trunks but also for media gateway signaling.
switch part: as it was said before, cm3 now supports auto fallback for h.248 media gateways without connection loss. very good one. also now it is possible to upgrade duplex (s8700) servers one after one without loss of connection. another one: locally sourced announcements and music. it means that you can use different announcements and music on the local media gateways with the same announcement extension number, switch will determine itself which one to use (you can override it, of course). ah, and now at last you can use announcement as a music on hold source! finally. another one: q.sig support for unicode. good for international use.
oh well, forgot the greatest one: mixed port network connectivity! it means that if you have s8700 multi-connect system, you can now add new epns over ip and you're not limited to fiber. very long-awaited one, that.
there are a lot of new hardware available for cm2 and cm3, especially good for remote locations, tiny to large. g150, g250 and g350 media gateways, new tn2602 medpro boards for up to 320 voip codecs, new tn793cp (programmable!) analog circuit pack, new tn2464cp ds1 circuit pack and more. can't remember it all just offhand.
by the way, trunk ports in cm3 are not counted at all. in cm2 their cost was $0.01 but customers were required to order them, in cm3 there is no part number for trunk port at all. neither for tdm nor ip. good for tandem switches, this one.
also starting with cm2 there are some features available at no cost comparing to cm1: tenant partitioning, for example, basic call center, universal license for tdm and ip users, multi-national locations and many more.there are two long-awaited features scheduled for 3.0.1 that should be available in sep '05: ip phone signaling encryption and emergency calls from unregistered ip phones.
now to the call center part. the most visible changes in cc 3.0 are: 100 aux reason codes instead of 10 (requires cms r13 with specific software load) and more advanced variables in vectors.
huh. sorry, got tired.
there are too many changes to describe in one post. life is going on and on, you know. - Thread starter
- #11
johnnydialtone
MIS
dwalin,
I was speaking of DS1 resources out to the PSTN.
I know that the expanded meet me doesn't "require" additional DS1 cards but if you are going to use your PBX as a conference bridge you might consider adding additional circuit resources unless you are severely overtrunked. Up to 300 simultaneous additional calls would cause a problem with our current trunking.
If I decided to use the expanded meet me there would be some traffic analysis before hand. I would be putting in more trunks and therefore more DS1 cards.
I was speaking of DS1 resources out to the PSTN.
I know that the expanded meet me doesn't "require" additional DS1 cards but if you are going to use your PBX as a conference bridge you might consider adding additional circuit resources unless you are severely overtrunked. Up to 300 simultaneous additional calls would cause a problem with our current trunking.
If I decided to use the expanded meet me there would be some traffic analysis before hand. I would be putting in more trunks and therefore more DS1 cards.
heathersue
Technical User
My question is related to upgrades as well, but not from an added feature standpoint. I am interested in system-critical reasons to upgrade only. For example I have a G1 from 1984. Very old, but it works. why upgrade? Is there some compelling reason to upgrade G1's, V4's etc; such as if a processor goes bad it vant be replaced, or if I need to add more RTU I can't? And where do I draw the line? At what release of definity can I sit back and say 'I'm covered until 2008'. Any opinions on this?
thanks, heather
thanks, heather
johnnydialtone,
if you plan to use your pbx as a conference bridge for external callers, of course you'd need additional ds1 resources. but in my experience, conferencing is mostly used for inside users, rarely connecting remote parties. anyway, if you're doing conferencing _now_ you're limited to 6 parties including remote ones. with expanded meet-me, you'd need the same ds1 resources but could add more internal parties.
if you plan to use your pbx as a conference bridge for external callers, of course you'd need additional ds1 resources. but in my experience, conferencing is mostly used for inside users, rarely connecting remote parties. anyway, if you're doing conferencing _now_ you're limited to 6 parties including remote ones. with expanded meet-me, you'd need the same ds1 resources but could add more internal parties.
NX01,
i'd recommend you to take a look at g250. if you have some small remote offices (4 to 16 men) g250 is more suited for this task than g150, imho. at least it is based on the same reliable s8300. though g150 is very very cheap, and that's its strongest side.
i'd recommend you to take a look at g250. if you have some small remote offices (4 to 16 men) g250 is more suited for this task than g150, imho. at least it is based on the same reliable s8300. though g150 is very very cheap, and that's its strongest side.
heathersue,
you would laugh, but the most often reason for upgrading v4s i've met was the lack of tapes for backup. the ones that came with the system are used up to the holes and you just can't purchase new ones, they're ten years as out of production.
now going serious. it is wonderful that you have still working g1, but consider the moment it breaks up? no replace, the system's twenty years old. and it's not only processor that could go south, all the hardware suffers from the old age, especially pieces that have moving parts. so frankly speaking, using a switch that old is like driving a twenty years old car without having a repair kit with you. yes it hums and it dribbles and it moves but if you're hit with some problem moving across mojave desert, it could be not a problem but a disaster.
now to the bright side. in all the modern technology (i mean voip of course there is more to see than just bells and whistles used to market and sell new products. believe me, voip literally opens the new horizons to all the communication world as a whole. you, for example, could benefit from the upgrade on your much-wanted system reliability. now you have a network of standalone switches, if one of them loses a processor, the switch is lost. how would you like a distributed switch with more than critical reliability, where every part could be not duplicated but multiplied? with newer techs you could reach anywhere, create huge telephony network and still manage it all as one switch. or two switches, just like you want it. nice, don't you think? and note that you could do this only with voip. because packet switched voice rocks. you couldn't reroute your voice channel on the fly if one of your ds1s goes down. you couldn't engineer your traffic precisely down to the byte. you couldn't this, you couldn't that, you couldn't anything just because you were limited to old technologies. now you don't have these limits.
and finally a bucket of cold water: don't fix it if it ain't broken.
you would laugh, but the most often reason for upgrading v4s i've met was the lack of tapes for backup.
the ones that came with the system are used up to the holes and you just can't purchase new ones, they're ten years as out of production. now going serious. it is wonderful that you have still working g1, but consider the moment it breaks up? no replace, the system's twenty years old. and it's not only processor that could go south, all the hardware suffers from the old age, especially pieces that have moving parts. so frankly speaking, using a switch that old is like driving a twenty years old car without having a repair kit with you. yes it hums and it dribbles and it moves but if you're hit with some problem moving across mojave desert, it could be not a problem but a disaster.
now to the bright side. in all the modern technology (i mean voip of course
there is more to see than just bells and whistles used to market and sell new products. believe me, voip literally opens the new horizons to all the communication world as a whole. you, for example, could benefit from the upgrade on your much-wanted system reliability. now you have a network of standalone switches, if one of them loses a processor, the switch is lost. how would you like a distributed switch with more than critical reliability, where every part could be not duplicated but multiplied? with newer techs you could reach anywhere, create huge telephony network and still manage it all as one switch. or two switches, just like you want it. nice, don't you think? and note that you could do this only with voip. because packet switched voice rocks. you couldn't reroute your voice channel on the fly if one of your ds1s goes down. you couldn't engineer your traffic precisely down to the byte. you couldn't this, you couldn't that, you couldn't anything just because you were limited to old technologies. now you don't have these limits.and finally a bucket of cold water: don't fix it if it ain't broken.
heathersue
Technical User
hi, dwalin,
Thank you so much for taking the time to respond to me. I agree, system reliability , servivable procesors, and ease of management are all great things to have and I'd love to get my hands on it. The problem is my my industry. I'm working for a chemical company who only wants dial tone - nothing more. the phone on their desk is the most unimportant item, so the justification for upgrading has to be for system critical reasons only.
My telling the powers that be that the justification is survivability would just result in them asking me 'if we didnt need it before why do I need it now'?
I still, however, think that they do need to be upgraded. I know its hard to get parts for a G1 and even harder if not impossible to get new maintenance on one. So that would be my justification on those. Your comment on the tape backups on the V4 is a good justification, without backups we'd be in big trouble and that is system critical. I know if I need to add RTU to a legacy item after December I wont be able to until I upgrade, but I dont know what release that goes up to...do you know?
Thanks!!
Thank you so much for taking the time to respond to me. I agree, system reliability , servivable procesors, and ease of management are all great things to have and I'd love to get my hands on it. The problem is my my industry. I'm working for a chemical company who only wants dial tone - nothing more. the phone on their desk is the most unimportant item, so the justification for upgrading has to be for system critical reasons only.
My telling the powers that be that the justification is survivability would just result in them asking me 'if we didnt need it before why do I need it now'?
I still, however, think that they do need to be upgraded. I know its hard to get parts for a G1 and even harder if not impossible to get new maintenance on one. So that would be my justification on those. Your comment on the tape backups on the V4 is a good justification, without backups we'd be in big trouble and that is system critical. I know if I need to add RTU to a legacy item after December I wont be able to until I upgrade, but I dont know what release that goes up to...do you know?
Thanks!!
heathersue,
the current release is cm3 (r13). previous r12 release is still sold though, its end-of-sale is scheduled for december 15. as for adding rtus, unfortunately i can't help you much with this because avaya's business rules for u.s. are somewhat different and i know only ones for emea region.
as for justification for upgrades, you can call on the idea that upgrade and get new maintenance contract on the latest release may be much cheaper than contract for older switch on the long run. it's inavoidable because old systems are getting scarcier and people that can maintain them are harder to find every year. this goes to supply and demand and results are ever-increasing cost for support. also consider newer systems hardware and software unification and ease of maintenance. for large enterprises, this may mean quite a lot.
the current release is cm3 (r13). previous r12 release is still sold though, its end-of-sale is scheduled for december 15. as for adding rtus, unfortunately i can't help you much with this because avaya's business rules for u.s. are somewhat different and i know only ones for emea region.
as for justification for upgrades, you can call on the idea that upgrade and get new maintenance contract on the latest release may be much cheaper than contract for older switch on the long run. it's inavoidable because old systems are getting scarcier and people that can maintain them are harder to find every year. this goes to supply and demand and results are ever-increasing cost for support. also consider newer systems hardware and software unification and ease of maintenance. for large enterprises, this may mean quite a lot.
98Converter
Technical User
If you "drop" the G1 in the middle of a production day, I think your justification will be there... Then they'll recognize the importance of the phones.
The most immediate notification tool to use when something is wrong is the phone.
Believe me, I worked in the Nuclear Industry for awhile (I know your battle) - where their core business in generating power. They have a LARGE dependancy on phones (for safety, etc..), but never recognized the importance of maintaining them. It took close to 3 years to convince them to upgrade from G3V6 to CM 1.x... Now they're preparing for CM3.0.
Thanks,
CJH
We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.
The most immediate notification tool to use when something is wrong is the phone.
Believe me, I worked in the Nuclear Industry for awhile (I know your battle) - where their core business in generating power. They have a LARGE dependancy on phones (for safety, etc..), but never recognized the importance of maintaining them. It took close to 3 years to convince them to upgrade from G3V6 to CM 1.x... Now they're preparing for CM3.0.
Thanks,
CJH
We are what we repeatedly do. Excellence, then, is not an act but a habit. ARISTOTLE 384-322 B.C.
SparkyDTMF
MIS
One of the key benefits of CM 3.0 is their new approach to licensing: you now buy XX for licensing of DCP phones, trunks, IP phones, etc. The new model of licensing combines trunks, DCP sets, IP sets from one pool; whereas before CM 3.0, Avaya would license these objects differently.
- Status
Similar threads
- Question