Unity unified system installed connecting to Call Manager 3.3 all components working O.K.
Unity working to Avaya Definity via dialogic cards everthing works O.K. except when call transfer is enabled on a call handler.
When the incoming call from the Definity arrives at the Unity voice port the greeting is played.If you require the call to be transferred ,to say a mobile, the outgoing call is sent down the same port as the incoming call. The caller hears the dial pulses outgoing then the call is dropped.
Has the Unity the option to dial-out on a different port or send a transfer code to the definity.
The sequence Unity uses to initiate a transfer is defined in the switch file, found in the \commserver\intlib\ directory. Your probably using one of the avaya000X.ini files. The parameter your looking for is TransferInitiate=. It can be edited using any text editor or I believe it is exposed through Unity's Switch Edit Utility. The default value for all three avaya switch files is
This tells Unity to perform a hookflash, pause, then dial the extension of the transfer target. What sequence does your definity expect for performing a transfer on an analog line? From your description it sounds like this might be the right sequence but your definity isn't recognizing the hookflash. We can probably tweak this a bit also. Which of the three avaya switch files are you using?
Thanks for replying to my problem. You are correct the file we are using is the avaya0003.ini file and the TransferInitiate is set as &,
The ports on from the Definity to the Unity are set vmi.
Ok, the default HookFlashDuration in that switch file is 500ms. It seems unlikely that your PBX would "miss" a half-second hookflash. The best way to narrow down the problem is by attempting the transfer manually. Here's what I have in mind...
First, unplug on of the lines from the Unity box (maybe remove it from the hunt group first if this is a live system). Connect the line to a standard analog phone. Then call this phone directly. When you answer you should get a burst of DTMF in your ear. That's just the normal mode-code data being sent. Now, attempt to perform the transfer manually by performing a hookflash and dialing the target extension. Try this a few times to get a feel for any timing thresholds that might be needed for the hookflash. If you can't get it to transfer at all then you'll need to turn to your PBX and figure out why it won't let you transfer. If you can do these manual transfers fine then we'll turn to Unity and figure out what it is doing different.
Already attached a phone to the one of the lines and yes you do get the normal mode-code being sent, but the hookflash didn't seem to work and even pressing the transfer button didn't work when the definity port was set to vmi.
But now I know I'm on the right track I will give it another go in the morning and let you know.
Tried all of the lines with phone attached.Unable to get hookflash to work when the port was set as vmi, even though the port settings show the hookflash option is enabled.
Flagged this problem to the PBX suppliers to investigate.
Will let you know the outcome.
Interesting. Are you saying that hookflash transfers work fine if you simply change the station type from VMI to 2500? I'd be curious to hear how this gets resolved. On the Definity in our testing lab we flop lines between VMI and 2500 set quite a lot. The only immediately noticable difference is the Mode-Codes.
This is the latest reponse from Avaya on the porblem:
The response from Avaya regarding the tests they have carried out is that
Unity4 in not sending a "switch hook flash" to the Definity rather it is
sending a "Recall Prompt".
They have also asked can Cisco confirm the extent of Interoperability
testing that has been done and have Cisco any documentation for Integration
to Definity available?
Not exactly helpful. Any ideas?
Avaya have now fixed the "switch hook flash" from the analogue phone when the port is configured as vmi.
The call transfer from Unity still does not work and as last message they say we are sending a "recall prompt".
Changed the hookflash delay parameter but still no joy.
Is there anyway that the PBX support folks can describe the difference between a "recall prompt" and a hookflash? Is it the duration of the open loop?
Also earlier in the thread, this was mentioned, "The caller hears the dial pulses outgoing then the call is dropped. "
By "dial pulses", do you mean DTMF tones or actually the dial pulses you would hear while dialing on an old rotary phone?
The caller hears DTMF tones then the call is dropped.Putting a phone into the cable presentation on the rear of Unity and pressing switch hooks the caller hears on- hold tone.
When that phone is plugged in back there, I think what we would want to do is call that phone from another phone. Answer the phone that's plugged in and then hit the switch-hook. Or, is that what you did? There's a difference b/w going off-hook and pressing the switch hook, and pressing the switch-hook after you've answered an incoming call.
I'd also be real curious to see what's the difference b/w the "recall prompt" that the PBX folks referred to and a hook-flash.
The test you mentioned is the exactly as performed.The called number on the back of Unity when answering the call hears the mode-code then is able to speak to the caller,if the switch-hooks are then pressed he receives dial tone.
FYI, this is now fixed and working well. The primary resolution was to change the analogue signalling in the dialogic configuration manager (DCM) under country settings. The default "euro" setting (as recommended in the install docs) had analogue signalling set to ER (Earth recall) rather than the correct HF (Hook Flash).