After upgrading CCM from 3.1(1) to 3.1(2c), SP-B, transfers from Unity to one of three locations consistently fail (Unity appears to hand the call off to CCM, but the target phone does not ring and the call times out). Upgraded the tsp from 220.127.116.11 to 18.104.22.168 but no change in Xfer behavior. All VM ports and phones are registered to the same CCM.<br><br>
What type of transfers are happening? Release or Supervised? What does the caller that Unity attempted to transfer here when this failure occurs. Are there any MIU errors or TSP warnings in the app event log?
The transfers are Release To Switch. Callers hear silence and then are disconnected after about 20 seconds,the IOS on the remote site gateways does not support ring tone on transfers. There are no MIU errors or TSP warnings in the app event log for this site, however, there are some this morning for a remote site which had previously not been experiencing this problem.
If release transfers are consistently failing, and there are no MIU errors or TSP warnings in the event log, we'd need to take a look at TSP traces (and probably CCM traces as well) to make sure the TSP isn't misbehaving. There were changes made to TSP 3.0.3 in regards to release transfers, but it should be an overall improvement in how release transfers are handled from Unity (and it sounded like from the first post that the change that made this not work was a change in CCM version). Is there a TAC case open on this? There probably should be since we'll need to dive into the traces. If it does fail all the time, that's actually a good thing. We should be able to figure out what's going wrong easier.
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...