I have not seen those.
Are these possibly the IP's assigned to the sets during configuration?
This could be giving us a clue to the problem for sure!
I did a quick search of the Nortel Knowledge Base, but only found this.
Are you using NAT?
No speech path on VoIP telephones behind a "port restricting" NAT device.
--------------------------------------------------------------------------------
Problem Description
Deployment of VoIP telephones behind third-party NAT devices, even though not an officially supported configuration, can result in no speech path issues . The unidirectional streams feature breaks compatibility with a specific type of NAT device commonly called "port restricting" NATs. Such devices filter packets flowing from public into private domains and only allow packets from Y:y IP-address

ort combinations into the private domain destined to X:x internal addresses if they have seen recently (within 60 sec) at least one packet flowing from X:x to Y:y. Such a packet is said to create a pinhole in the NAT.
With bidirectional streams, when an incoming IP telephone stream is set up by UTPS, the corresponding outgoing RTP stream is always set up by the UTPS on request from MPS. Both streams have matching IP addressing information. The first packet of an outgoing stream generates a pinhole in the NAT. With the introduction of unidirectional streams, this is no longer the case, so when a unidirectional stream is set up, the NAT filters the packets out in multiple scenarios. One such case is a telephone going off hook. A unidirectional stream is open to produce dial tone from the BCM. The NAT does not let the dial tone through. In the case of an outgoing call, the ring back tones are also delivered by means of unidirectional streams. There are perhaps other examples of such issues with background music and music on hold that have not yet been seen in the field, but would most likely exhibit similar behavior.
-SD-