bankingguy
IS-IT--Management
What is the best alias type for J169/J179 SIP Phones?
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Alias Type for J169/J179
- Thread starter bankingguy
- Start date
- Status
- Thread starter
- #4
bankingguy
IS-IT--Management
Got it.
J129/J139/J169/J179 - Aliasing
Avaya Aura® Communication Manager 7.1 and below does not provide native support of the J129/J139/J169/J179 IP Phones. The J129 should be administered as a “9608SIP”, the J139 as a “9608SIP”, the J169 as a “9611SIP” or “9611SIPCC” and the J179 as a “9611SIP” or “9611SIPCC”.
Until Avaya Aura® Communication Manager provides native support of the J169/J179 IP Phones, there are JBM24 feature administration limitations. To preserve existing settings for a user, feature buttons will be ported the first time they login to the phone. This allows an existing user with a 9608/9608G/9611G/9641/9641G IP Phone and BM12/SBM24 to upgrade their phone to a J169/J179 with JBM24 and preserve their BM feature buttons. Any further changes via System Manager after the initial login will not be seen until Avaya Aura® Communication Manager provides native support of the J169/J179 IP Phones and coresponding JBM24 button module.
J129/J139/J169/J179 - Aliasing
Avaya Aura® Communication Manager 7.1 and below does not provide native support of the J129/J139/J169/J179 IP Phones. The J129 should be administered as a “9608SIP”, the J139 as a “9608SIP”, the J169 as a “9611SIP” or “9611SIPCC” and the J179 as a “9611SIP” or “9611SIPCC”.
Until Avaya Aura® Communication Manager provides native support of the J169/J179 IP Phones, there are JBM24 feature administration limitations. To preserve existing settings for a user, feature buttons will be ported the first time they login to the phone. This allows an existing user with a 9608/9608G/9611G/9641/9641G IP Phone and BM12/SBM24 to upgrade their phone to a J169/J179 with JBM24 and preserve their BM feature buttons. Any further changes via System Manager after the initial login will not be seen until Avaya Aura® Communication Manager provides native support of the J169/J179 IP Phones and coresponding JBM24 button module.
There's a few PSNs and release notes about it.
Short version is that it's a first class citizen on SMGR/SM/CM 8.0 and kinda kludged into R7. Even though a CM alias station will work, SMGR/SM don't know about that model.
There's a patch for SM I think. What it does is "when SM sees a J phone register, it rejigs the PPM profile data to appear right on a J phone and it does it once and it's automatic in the background and there's no going back"
In practice, what that means is once a J phone registers to an account, if you ever swap back for a 9600, it'll act weird, so delete the profile/set and recreate it.
Short version is that it's a first class citizen on SMGR/SM/CM 8.0 and kinda kludged into R7. Even though a CM alias station will work, SMGR/SM don't know about that model.
There's a patch for SM I think. What it does is "when SM sees a J phone register, it rejigs the PPM profile data to appear right on a J phone and it does it once and it's automatic in the background and there's no going back"
In practice, what that means is once a J phone registers to an account, if you ever swap back for a 9600, it'll act weird, so delete the profile/set and recreate it.
- Thread starter
- #6
bankingguy
IS-IT--Management
@kyle555 - would you mind sharing me what version are you talking about so I can take a look? I'm running 7.1.3.2 SM/SMGR.
- Status
Similar threads
