Is Session Manager Required??

[SS67]

I have a customer that wants to test drive 2 SIP 1140 sets and needs me to configure the CS1000-MG 7.5. They have unistim sets now but I realize they will need a third CPDC that will be dedicated to SIP Line Gateway.

The 64 Thousnad dollar question is do I need Session Manager? AVAYA says if you have SIP period you need Session Manager.

NCSS, NCDS, for CS1000 and BCM

 

[KCFLHRC]

That is what I have been told also. SIP in 7.5 requires session manager. H323 is still supported without it but I do know for a fact that SIP trunking requires it. I haven't done any SIP phones yet. Just SIP trunking to Aura Messaging.

 

[janaya]

at 7.5 you do not need a session manager or system manager for SIP. You do need licensing and NRS to build the SIP trunks. I have a customer that is running SIP trunks without a deployed Session Manager and System Manager.

7.7 that's coming out, big difference. then you need the System Manager (which replaces the Primary UCM) and Session Manager (which replaces the NRS)

Avaya will tell you "You have to have System Manager and Session Manager for SIP", but it's not HAVE TO right now.

 

[SS67]

Thanks for the help so far. So am I correct to say for SIP End Points (Nortel, AVAYA, or 3rd party SIP Phones)I just need the Sets, SIPN Licenses, and the CPDC configured as a SIP line gateway?

NCSS, NCDS, for CS1000 and BCM

 

[biv343]

You can have SIP line on the same server that is serving LTPS and VTRK in 7.0 and later. No explicit need for a separate SS for SIPL anymore, just need licenses.

 

[SS67]

The EC tool provisioned another Sig Server in my quote for 2 phones and two licenses. That tells me from an AVAYA support standpoint i have to have it. I realize things will sometimes work but I have to stay with what AVAYA will support. Getting a straigh answer from my regional rep is like pulling teeth.

NCSS, NCDS, for CS1000 and BCM

 

[biv343]

I've done it and it works fine. Check page 21 of doc NN43001-508 for release 7.5.

You can enable standalone SIP Line or you can enable SIP Line co-resident with the Call Server and other Signaling Server applications. Table 2: Platform support for SIP Line on
page 21 provides information about hardware platform support for standalone SIP Line and co-resident SIP Line.

The only platforms that can't have co-res SIPL are the HP320G4 and IBM x306M. CPPM/CPDC work fine co-res.

 

[SS67]

Biv343 and everyone else,

Thank for pointing me to the doc, Under hardware and software requirements there is no mention of Session Manager. Bugs me that we are having session manager pushed down our throat by AVAYA when it is not needed. I show them docs like this and the response is "Ok but you really should have session manager going forward". And they wonder why we sell way more ShoreTel than AVAYA???

NCSS, NCDS, for CS1000 and BCM

 

[KCFLHRC]

Bugs me too. I just installed System/Session Manager at a site that needed SIP trunks for Aura Messaging and I was told you had to have these 2 servers. Seems like configurator puts it in there as soon as you say I need SIP anything. Just another point of failure in my eyes. I sure wish I didn't have them in there because I have had lots of problems. I don't even think Avaya knows for sure.

 

[allenmac]

You do not need to install System and Session Manager if you have any H.323 virtual trunks on your system.

In order to be considered a 'Supported Configuration' Avaya requires System and Session Manager in 7.5 and above if you only have SIP virtual trunks.

I currently have 10 CS1000E's all running 7.5 with all SIP trunking running NRS. We purchased System and Session Manager but have not implemented them yet, and everything is working properly.

 

[KCFLHRC]

Key statement, " Not being a supported configuration" That's where you get into trouble if you need support. Probably why my support says you have to have it. We don't do unsupported configurations. Smaller companies may be able to get away with that, not us.

 

[allenmac]

As long as you have a single H.323 virtual trunk license on each system at 7.5+ in your enterprise, then you can run NRS and be in compliance with Avaya as a 'Supported Configuration'.

I don't know how long this loophole will exist though...

 

[biv343]

Tell Avaya you have IPV6 deployed. Then you can keep NRS forever.

I heard that the only requirement for SM in 7.5 was when running SIP trunks to the PSTN. I'm not 100% certain anyone at Avaya really knows when you need it. It's pretty expensive considering it doesn't do a whole lot more than NRS, at least today.