cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
409
Views
0
Helpful
8
Replies

TSP 8.0(1b) install gave new issue

patiwaq
Level 1
Level 1

Hello, I installed TSP 8.0(1b) after having issues with digit input being recognised. That fixed that however gave us a new issue. When a phone is set to "forward all calls to VM" and an external call comes in for that extension, the call dies. Internal calls to that extension have no issue. Anyone seen this before?

Thanks again for all your help.

8 Replies 8

mrmccann
Cisco Employee
Cisco Employee

Can you be more specific about what happens when the call dies? What does the caller hear? Dead air? Reorder?

We are running TSP 8.0(1b) here, and external calls to an extension set to forward all to voicemail seem to work OK. So there may be something particular about your environment that is causing problems. What version of CallManager are you running? Also, do call-forward on busy and ring no answer seem to work OK for external calls?

Call mgr 4.1.3.1

Caller hears dead air. You look at your display and the phone appears to never have made a call.

External calls to busy/no answer is fine..its just when calls are set to fwd to vm.

We installed TSP 8.0(1b) last night to fix another issue. This new issue started after the (1b) applied.

Can you call the VM Pilot # directly and get into unity fine?

Are any other calls getting to unity (auto attendants, etc)?

IE: Are forwarded phones only calls having problem?

What does port status monitor say while watching it while you try to call a phone that fwds to phone? do you see a call listed here? how about call viewer app?

On the call manager, go under feature -> voice mail port and see if the voice mail ports are registered. I had a dead air issue and the vm ports were registered but to 127.0.0.1 (loopback) for some reason instead of unity server IP and stopping/starting unity via unity system tray icon fixed that up. this was on 7.04 TSP though and not 8.01b.

Did you reboot your unity server after applying 8.01b?

Yup all other calls are fine. I can call the vm port with out issue.

The port monitor shows the call...and watches it drop. And all vm ports are registered to 10.10.x.x

Unity was rebooted after the install, plus several times there after.

We have only had our system since 12/04 with the final office install 04/05. We were great up until we upgraded call mgr to 4.1.3.1 in early June. Then since, Unity has these lil annoyances ( call pickup groups that goes through a handler fails but successfull if points to a DID, digit input isnt recognized before or after working hours, but during time of business works just fine- the reason we applied TSP (1b), and now this. Crazy huh??

As far as Unity is concerned, there is not any difference between a call forwarded to Unity from a phone set to call-fwd all, and a call forwarded to Unity from a phone set to forward on RNA. So it is odd that a call from the same external source would behave differently depending on the forwarding settings on the internal phone.

Looking at Unity TSP traces could probably tell you why the call is hanging up, however you may need to contact TAC to get help with this.

What version of Unity is this?

Resolved our issue by rolling back to TSP 7.0(4b)

Thanks all for trying to help.

There was a new defect logged, CSCsb27128 (Unity Disconnects Blind Transers To Devices Forwarded to Voicemail), which describes the behavior you're seeing.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: