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!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Retiring Avaya CM - Session Manager - AAM - all of it

Status
Not open for further replies.
learningSkype

learningSkype

IS-IT--Management
Jun 6, 2016
213
US
morning all, we're retiring Avaya this year, it's been in the planning for a long time.

something we've discovered is that we need a new SIP Registrar. in the past H.323 phones would register to CM and SIP phones would register to ASM. but since we're turning those servers down, we need something to take its place.

we have Ribbon SBC 5400 models but have been told they can't provide SIP registration.

we need this for multiple reasons, phones, audio gear, other 3rd part vendors.

any thoughts? have you decomm'd your Avaya PBX? where do you register your SIP endpoints now?
 
Sort by date Sort by votes
When you say retiring Avaya do you meet moving off your current release to upgrade/going to OneCloud or switching vendors all together?
 
Upvote 0 Downvote
migrating to TEAMS phone system completely. all our users w/be deleted from Avaya.
 
Upvote 0 Downvote
Are you going fully soft client or going to be using hard phones? None of the Avaya phones are teams certified or compatible currently so you would have to get phones if you were wanting handsets. Also are you going direct routing? If so, that Ribbon SBC is certified so you can point your trunks into that and connect SBC to teams.

One of the big things with Teams, people usually don't do extension dialing really (can be done with normalization rules but most dial by name) so that is one thing that is nice not having to worry about if you choose to tell users you have to dial by name.
 
Upvote 0 Downvote
Direct Routing and we're testing Poly CCX phones that would register to TEAMS. we're not deploying a ton of hard phones, maybe just a few hundred. everyone else would just use the TEAMs client on their PC/laptop/smartphone.

Back to my original question, what system/platform can be used as a SIP registrar since Avaya is going away?
 
Upvote 0 Downvote
You have not stated what model of SIP phones you are using.
 
Upvote 0 Downvote
yes I did. we're testing CCX 600 phones and may deploy the 400 and 500 models.
 
Upvote 0 Downvote
I misinterpreted that you already were using SIP phones on the Aura system.
 
Upvote 0 Downvote
I apologize, I am not understanding question. Are you asking where do you register the Poly CCX Phones after you move from Avaya to Teams? The Teams certified phones would be registered to teams. If you had paging, fax and other stuff, to my understanding they would hang off of the SBC.
 
Upvote 0 Downvote
yes that's what I'm asking. if Avaya goes away, where do you register SIP devices to, the SBC or some other appliance?

I know that some SBC's can act as a registrar, but not everything can register to TEAMS. something like a fax machine would not be able to register to TEAMS. yes, some people still use faxes, I don't know why :)
 
Upvote 0 Downvote
Analog lines, Fax and paging would be off of the SBC either on the physical SBC or if you had an ATA, that would point to the SBC. All Certified IP Phones and Conference phone/room systems would register to teams and users would sign in with AAD credentials.

Some SIP and Dect devices can hang off of a SIP Gateway (not a physical gateway but one in the cloud) MSFT offers for older SIP devices and DECT devices. Here is a link to all the compatible devices:
I am not sure if you can hang a normal SIP Phone off the SBC, has anyone attempted that before? If it is possible, I assume features would be limited
 
Upvote 0 Downvote
learningskype said:
yes that's what I'm asking. if Avaya goes away, where do you register SIP devices to, the SBC or some other appliance?

I know that some SBC's can act as a registrar, but not everything can register to TEAMS. something like a fax machine would not be able to register to TEAMS. yes, some people still use faxes, I don't know why :)
Click to expand...

SBCs are not a registrar they act as a proxy for a SIP server. You need to understand what is and isn't SIP (google it), analogue endpoints need an ATA to convert the analog signal to SIP messaging and media.

MS Teams supports ATAs via an SBC but they don't "register" they convert the analogue to SIP and proxy it to Teams (as an endpoint or trunk)
 
Upvote 0 Downvote
What are you trying to keep?

OOOOh..

This relates to your post about subscription licenses expiring, huh? :p

You need to get rid of Avaya licensing but aren't ready to replace the handsets. Do I read you right?
 
Upvote 0 Downvote
Why not just keep System and Session Manager? It will add value to your new design.
 
Upvote 0 Downvote
we've been having internal discussions and are looking to see what is truly needed in terms of the Aura Suite. so far we'll be keeping AES, ASM, CM and SMGR. we don't really need AAM so that pool of servers is not an issue.

back to my original question, I need a SIP registrar that replaces my ASM. as some of you may know, H.323 phones register to Avaya CM while your SIP phones register to Avaya Session Manager (ASM).

so I need something that can act the same as ASM and allows phone registrations.

and I'm familiar w/ATA's and gateways, that's not the issue.

one more thing. when I say we're keeping the servers above, that's only temporary. we would keep them for another 6 months tops.
 
Upvote 0 Downvote
From a technology perspective, you need a license to run SM/SMGR. You can add all the SIP users you want to it.

They only get features from CM via the application sequence, and a CM station needs a user-level license.

I don't think you're in license violation to keep a system with 1 Aura user that drives entitlements to have all the Avaya products and to have several instances of them and to have 10K users with Session Manager profiles but no app sequence or CM.

Ask your lawyer or Avaya rep :)

With an empty system and nothing but user accounts with no CM, registered SIP phones should be able to call each other.
Have a dial pattern of x go to the direct routing SBC.

What exactly is the integration and functionality you're trying to achieve? Keep Avaya phones as SIP registered to...something...for what purpose exactly?

 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

hcmbmt
  • Locked
  • Question
Empty MTA trace for Avaya CM 1
Replies
9
Views
683
hcmbmt
hcmbmt
hcmbmt
  • Locked
  • Question
Avaya Session Manager CLI login password
Replies
0
Views
143
hcmbmt
hcmbmt
BlackCuervo
  • Locked
  • Question
Polycom SoundStation IP 7000 connected to Avaya Aura Session Manager 8.1 issue
Replies
0
Views
126
BlackCuervo
BlackCuervo
DTGMI
  • Locked
  • Question
Avaya Aura - CM and J100 Wireless Module
Replies
1
Views
338
madwok
madwok
hebegb41
  • Question
Avaya SM/CM 8.1 J139 SIP phones and "bridged Appearances"
Replies
4
Views
310
hebegb41
hebegb41

Part and Inventory Search

Sponsor

Back
Top