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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

J179 PPM

Status
Not open for further replies.

iggy1952

IS-IT--Management
Feb 2, 2006
172
US
We are programming a J179 to our SM and cannot get the CM features to download via PPM. We have checked our utility server settings are they appear correct and cannot get the PPM to pushing call features from CM.

We are running SM 7.1.3 and programmed the J179 as a 9608 set, Any suggestions?

iggy1952
 
I assume you mean 9608SIP. If you clear a 9608, let it register, and log in to the same extension, does it work?
 
gwebster

Do you mean change the set type from 9608SIP to 9608?



iggy1952
 
Set type should be 9608SIP. I was asking if a real 9608G works.
 
gwebster,

When I go into SMGR and try to allow the endpoint for dual registration as a SIP and H.323 it does not allow me to make the change in the checkbox.

iggy1952
 
Let me try again. Do you have an extension programmed as a 9608SIP? Do you have a 9608G with SIP firmware? If yes, when you log it into the extension, does it register and download configuration from PPM.
 
gwebster,

X 5511 is programmed as a 9608SIP with SIP firmware. When I log the phone in I see message downloading configuration but the phone only shows 3 call appearances, Redial and New Call buttons. SAC and bridged appearance buttons are not showing up.

iggy1952
 
If you perform a traceSM with PPM enabled, do you see the phone doing the phone PPM download?

If you "display sta 5511" does it show a 9608 or 9608SIP as the phone type?

 
randycaroll,

X 5511 shows as 9608SIP phone type.

We just upgraded our Session Manager to 7.1 and I cannot get the TraceSM to work after logging into the CLI. I get no such directory error message when entering traceSM command.



iggy1952
 
Iggy-

I'm struggling with these new J-series phones too.
Unlike the 9608s (running sip), the J-series phones require TLS certificates on the phone. This took me quite a bit to figure out and get going.
Once I had a certificate on the phone, then PPM worked.

Now that I have PPM working, I'm stumped trying to figure out how to actually program buttons on the phone.
The screens on the phone apparently worked differently. ALSO --- take note, the software version 2.0 (which you need) - does not support busy-indicators any more! -sigh

Hope this helps,

john-
 
My understanding is that you also will need to be using the new 46xxsettings.txt file that Avaya put out in April of this year. It has the model options for the J-series sets.

For my part I can wait for the day someone in management sees a J-series set and wants one right away. It all sounds so painful and I'm glad y'all are pioneering it for us :)
 
jomontoya/Wanebo,

Thank you for the information particularly that you need a certificate to get PPM working on the J-179.

SIP sure has a feature deficiency.

I will keep you updated on my progress.

iggy1952
 
J179 update

SM user registration shows event package dialog, reg, ccs-profile,cm features, message summary on the J-179 set with CM features such SAC, EC 500 not appearing. All I get is standard three call appearances, Redial and New Call soft keys.

I also running latest firmware version 3.0.0.0.20 does not have Bluetooth firmware option.

Set is working like our Polycom Soundstation 7000's with basic SIP endpoint functionality.



iggy1952
 
Iffy-

I’m on a train to Sacramento, but I’ll try to respond with more detail tonight.

Button programming on these phones is completely different than any other avaya phone. Plus, no busy indicators buttons (it looks like they want you to have a presence server instead).

I was in exactly the same boat as you are.

I’ll get back on later, when I can pull my laptop out.

John-
 
jomontoya,

Look forward to your reply.

Thank you.

iggy1952
 
Iggy-

It's been confirmed by a few Avaya people-

In response to the lack of busy-indicators on the new j-series SIP phones.
"I use Presence on my phones and can see the status (available/busy/away/do-not-disturb/out-of-office/offline) of others as well as advertise their presence. This actually provides a much higher granularity that the simple “on the phone” of Busy Indicator. When you add a Contact to your personal contact list, looking at the Contact on your phone automatically shows there presence. You can then assign those contacts to any buttons – including the JBM24 – to easily see their status" --- hence, you need to run a presence server.

To make something like a busy indicator function without a presence server - "team buttons" are programable (but apparently there are a lot of gotchas with team buttons).

The rest of the buttons get programed like this. You add all the feature buttons you want to the phone. Then, you have two options to access them. 1. At the telephone, you press the menu button, then press the features button and this displays all of the features that you have programed on the telephone. 2. AT the phone itself - you scroll to an unused button, the label changes to "custom", then you press add and features, find the feature you want (thats already been programed and available in #1) and save it. You can do the same thing to move buttons too.

All of this is ONLY for SIP, I haven't tried to configure the phone as h.323.


I hope this helps,

john-
 
jomontoya,

When I go to the features option from the main menu I get message "No features configured for this extension". I have programmed features SAC and EC500 from CM. Additionally if I try to customize the label I get message "Customization not available at this time".

You think it is a firmware issue?

iggy1952
 
Iggy-

I'm using firmware 3.0
For the SIP phones, I use 'user-management' in system manager to configure and add features (not sure if there is a difference using CM to configure SIP phones).
Also, mechanically (with no regards to buttons) is the phone registered and working properly?

john-
 
jomontoya,

I am using firmware 3.0.

Phone was programmed as a SIP endpoint in user management in System Manager. I added feature buttons in Communications Manager expecting PPM to push features to the SIP endpoint from the CM origination and termination application sequences.



iggy1952
 
iggy1952 - do you have any other SIP endpoints configured and working? If the features are not showing under Menu -> Features, then something is not configured correctly.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top