cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
422
Views
0
Helpful
6
Replies

Transfer not always happening

admin_2
Level 3
Level 3

I have CM 3.0.11, TSP 10.0.036, Unity 2.4.6.126. Now that Cisco fixed my port problem I am back to the original problem. When the TSP is registered with the Publisher CM in a cluster, I get NO release transfers from the Unity system back to another phone. If I register the TSP with a subscriber then it works, but off and on, It will work one second then not, I get hold tones and stay on hold.<br><br>I understand there is a bug trac that 3.1 should fix, but I do not want to upgrade to 3.1 unless I have to, I just hate going to new code shortly after it has been released 8-).<br><br>Other than the transfers, Unity seems to be working fine. Anyone have any clues as to what I can do to check on the problem. I NEED these menu's soon and I have to have the transfer working reliably in order to use it.<br><br>Should I upgrade the TSP to 10.0.0.7 and install CCM 3.1?<br><br>------------------------------<br>Michael Perbix<br>Lower Merion School District<br>Telecommunicatons Specialist

6 Replies 6

Not applicable

Interesting....Where are the phones that Unity is trying to release transfer to registered? Also on the Subscriber? We did see a transfer problem when Unity was registered with one CM and phones were registered to another CM, but I can't remember if this was the exact problem. I'm thinking it was actually with supervised transfers.

Just for grins, try inserting a comma into the transfer string, so when transferring to 1234, the Unity SA would have <,1234>. See if that makes a difference.

Steve Olivier
Software Engineer
Cisco Systems

Not applicable

Okay that worked, now WHY does it work, and does that mean I need to do that for EVERYONE or can I somehow add that globally. The Unity box WAS registered to my publisher and my phones were registered to 2 other subscribers. Should this work then back in that configuration? And when 3.0 comes out, am I going to have to change that? And if I upgrade to CCM 3.1 will I need to change that?

------------------------------
Michael Perbix
Lower Merion School District
Telecommunicatons Specialist

Not applicable

It probably has something to do with the speed of the TSP transferring to a phone registered with a separate CallManager.

Well, let's just thank Steve for insisting for configurable timing parameters to take care of this stuff! What version of TSP are you running? Try editing/adding the following DWORD value in the registry...

HKLM\SOFTWARE\Active Voice\AvSkinny\InterDigit Send Delay = 300.

Take the comma out of the dial string and give that a shot. If that doesn't work, we might have to go to a TSP that supports the pre and post dial delays we got in.

Steve Olivier
Software Engineer
Cisco Systems

Not applicable

300 is the default value already in there, since the comma adds 1000 should I make it 1300?

-Mike

------------------------------
Michael Perbix
Lower Merion School District
Telecommunicatons Specialist

Not applicable

I wouldn't. The reg delay setting gets inserted in between and after a dial string. If you made it 1300, a 4 digit blind transfer would take over 5 seconds to complete. It sill might not even help. You need the pre-dial delay setting, but I'll need your TSP version to know if it can support it or not.

Steve Olivier
Software Engineer
Cisco Systems

Not applicable

Sorry, I saw earlier that you already gave me the TSP version. Let me check on a few things and I'll post the setting if it is supported in ver 36.

Steve Olivier
Software Engineer
Cisco Systems

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: