MitelInMyBlood
Technical User
Over the past couple years I've had infrequent reports about YA (3.09) client sometimes being unable to communicate with the local instrument (the one to which YA is associated), but never been able to find it & the user says it usually fixes itself in a day or so. As most of us know phantom problems like this are a bad thing that will eventually bite you with the CEO's phone someday. (be careful about bells & whistles you give the CEO)
I think today we discovered the dupe scenario for this YA problem, strange one that it is.
The setup: 3300 (rls 8 UR 5), Teleworker 4.5, YA (Lite) 3.09 and two 5340s with Multicall. The local installation at the office where the YA client is running has a 5340 with 2 multicall appearances of the prime ext. (ext 4321) The TW remote is another 5340 with a multicall non-prime appearance of 4321 along with keyline MWI of 4321. The user does not have YA at home.
As it turns out, the local office YA client is sympathetic to the status of the companion non-prime companion multicall line appearance of the TW remote instrument. If the TW remote ext goes down for any reason (phone reboots, internet connection dies, etc) then the local (office) YA Client reports loss of connectivity to the local ext to which it is associated and absolutely will not reassociate... even tried reinstalling.
In the above scenario even tho YA reports no connectivity, incoming calls to the associated instrument still cause an incoming call popup to be displayed on the local PC's YA window, but you can't answer via YA, nor can you initiate a call from YA.
The very instant the remote TW set with the non-prime line appearance of 4321 comes back up, then YA starts working again.
Anyone else ever experienced this?
I think today we discovered the dupe scenario for this YA problem, strange one that it is.
The setup: 3300 (rls 8 UR 5), Teleworker 4.5, YA (Lite) 3.09 and two 5340s with Multicall. The local installation at the office where the YA client is running has a 5340 with 2 multicall appearances of the prime ext. (ext 4321) The TW remote is another 5340 with a multicall non-prime appearance of 4321 along with keyline MWI of 4321. The user does not have YA at home.
As it turns out, the local office YA client is sympathetic to the status of the companion non-prime companion multicall line appearance of the TW remote instrument. If the TW remote ext goes down for any reason (phone reboots, internet connection dies, etc) then the local (office) YA Client reports loss of connectivity to the local ext to which it is associated and absolutely will not reassociate... even tried reinstalling.
In the above scenario even tho YA reports no connectivity, incoming calls to the associated instrument still cause an incoming call popup to be displayed on the local PC's YA window, but you can't answer via YA, nor can you initiate a call from YA.
The very instant the remote TW set with the non-prime line appearance of 4321 comes back up, then YA starts working again.
Anyone else ever experienced this?