The way that button data makes it to the phones on J-series devices is by using PPM. PPM is a "magical" setup where that extra avaya-specific data (like button data, contacts, etc) is sent via HTTPS calls instead of SIP calls. Under the hood, the phone polls Session Manager every so often to see if it needs to have this data refreshed -- and updates it at that time.
H.323 phones, because they emulate the old DCP protocol get out of band data within the signaling socket already open so they get this data usually between a few seconds and a few minutes (depending on how busy the system is, since only one phone can be updated at a time).
If you want the phone to update faster, you can make the change using System Manager (not ASA), then go to the User Registrations section of the Session Manager element. Find the registration of the phone you want to update in the list, and check the box. Then go to the "Reload" then "Reload Complete" to force the phone to poll for this updated info immediately. The phone should show the updated button data in about 10 seconds from that reload request.
------------------------------
Nick Kwiatkowski
Director of Design and Engineering
Michigan State University
East Lansing MI
------------------------------
Original Message:
Sent: 01-20-2022 06:54 AM
From: Todd Stone
Subject: SIP J179
Good Morning All,
I have just deployed several J179 and J189 phones. I have them all up and they seem to working as all features are working seamlessly. My question is, how long is supposed to take from the time you make button changes either by Manage endpoints or CM for the changes to show on the phone? Unlike H.323 where it instant, It sometimes take 4 or 5 minutes before the changes are visual.
Thanks,
------------------------------
Todd Stone
Telecommunications Adminstrator
St Johns County Schools
------------------------------