-
4
- #1
Richard10d
Systems Engineer
Had a customer who had 9608 phones registering as 4624's in System Status (running 11.0.4 if you care). Noticed a few threads that were related to older releases and issues with firmware.
In this case the problem was the customers network. When the PBX fails to receive the ident from the handset for whatever reason, it assumes it is a 4624. So if you have this issues, where a 9608 or ANY H323 phone, appears as a 4624, know that that is the default model when the PBX fails to receive that information from the handset. Here is the corresponding record from Monitor which helped:
" 15:12:54 181944mS PRN: GetIdent timed-out. Use default ident (4624 IP)"
In summary, the problem was the customers network (I think they had a bad switch, which they swapped out and they stopped having issues). 1 symptom was 9608 phones appearing as 4624s (among a myriad of other problems).
Avaya did confirm that analysis through my SR as well.
In this case the problem was the customers network. When the PBX fails to receive the ident from the handset for whatever reason, it assumes it is a 4624. So if you have this issues, where a 9608 or ANY H323 phone, appears as a 4624, know that that is the default model when the PBX fails to receive that information from the handset. Here is the corresponding record from Monitor which helped:
" 15:12:54 181944mS PRN: GetIdent timed-out. Use default ident (4624 IP)"
In summary, the problem was the customers network (I think they had a bad switch, which they swapped out and they stopped having issues). 1 symptom was 9608 phones appearing as 4624s (among a myriad of other problems).
Avaya did confirm that analysis through my SR as well.
