[darkmas]

Is there a way to have VG for Dialogic recognize a DTMF tone during call transfer? My PBX sends a DTMF "A" when the party picks up the phone.... I've tried a path such as:
on {a} [....] but that doesn't work.

112544.30 1 LsXfer_2_onendHook1PlayDestNbr 9030,EV_TIMEOUT_Transfer_Prefix_PauseAfter,0,0,0,,,
112544.30 1 Dial(178, cp on) call
112544.55 1 Dial(178) ok
112544.57 1 timer set 30 EV_TIMEOUT_ANNOUNCED_TRANSFER_ATTEMPT_TOOK_TOO_LONG
112548.34 1 tw dtmf a (1,97,97)
112548.34 1 event a, iCode=97 state=1903
112548.35 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 97,a,0,0,0,,,
112548.85 1 tw DialogicEvent 133,TDX_CALLP,10,3,0,TDX_CALLP,CR_CNCT,CON_PVD
112548.86 1 event VOICE, iCode=133 state=1903
112548.86 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,VOICE,10,3,0,CR_CNCT,CON_PVD,
112548.87 1 event CONNECT, iCode=133 state=1903
112548.87 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,CONNECT,10,3,0,CR_CNCT,CON_PVD,
112548.88 1 event CON_PVD, iCode=133 state=1903
112548.88 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,CON_PVD,10,3,0,CR_CNCT,CON_PVD,
112548.89 1 event CR_CNCT, iCode=133 state=1903
112548.89 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,CR_CNCT,10,3,0,CR_CNCT,CON_PVD,
112548.90 1 event TDX_CALLP, iCode=133 state=1903
112548.90 1 LsXfer_3_AfterDialDestNbrWaitForCallProgInfo 133,TDX_CALLP,10,3,0,CR_CNCT,CON_PVD,
112548.91 1 LsXfer_3 CR_CNCT on an XT_3WAY_MONITORED
112548.91 1 xfer dial

[SupportTeam]

try using:

on {success} goto [...]

or

on {voice} goto [...]

What is the transfer type used? 3-way monitored conference?

[darkmas]

Well, I'm using monitored PBX transfer. I can't actually use a 3-way transfer because the PBX won't let me complete the conference call UNTIL the called party answers the phone (silly pbx). On {success} works, but it waits until perfect call hears the voice on the other end. I'm trying to eliminate the extra second or so that it takes. The customer isn't thrilled with that little delay (silly customers) - normally there's nothing much one can even do but in this (rare) case the PBX is actually doing something helpful by signalling.

I was going to try a combination of blind transfer and/or play to do the transfers since, in this atypical case I actually don't need PerfectCall - GTD is fine for detecting busy and ring cadences and the happy little dtmf "A" upon answer is all that's needed.

Thanks again.

PS the PBX is a Telrad keybx 2464 in case anybody cares....... BTW, I think VoiceGuide is a great product... analog PBX integration is always a challenge if you really want to get it dialed in as best as possible. Here's a suggestion - why not create a section under your boards here broken down by PBX manufacturer/model. I've spent lots of time on this one and would love to post the results and save the next poor guy from hours of head scratching, hair pulling, etc....

-Darkmas

[SupportTeam]

We'll add functionality into the Transfer Call module to react to DTMF tones as well when doing monitored transfers. We should be able to post an updated version of VG which can do this within the next couple of days.

[darkmas]

Unless you were already planning to do it I don't think I need it. I have it working perfectly now by just doing the transfer with Play/Hangup. I've defined all my tones as GTD tones (ring, disconnect, busy, answer) and they all are detected perfectly by the HW and SW. Using the answer tone dtmf{A} saves .5 to 1 second over voice detection and everyone seems happy without the little "delay".

Now if I can just get the PBX to somehow pass the caller id data through to the vm ports on an incoming CO call, all will be well. :-)

BTW, I also am not using the inband signaling stuff because it seems to take 5 seconds to stop waiting for a key. I tried changing the setting in the VG.INI but I couldn't seem to get that to make any difference. This PBX sends the initial '*' (yes, '*' not '#') well within the first second after the call is answered. But it was quite simple to just use a couple of getnumber's to deal with that as well - it's always *DD - no other patterns.

FYI I'm replacing an old self contained voicemail/ivr box (ironically called "VoiceWorks") with your software and a dialogic card and I must say that it is like crawling vs. drving a car. The end client is thrilled, and I haven't even done anything fancy with it yet. No more 5 minute dialtone or "please hang up" messages. Gone are the days whereby they pick up the phone to answer a call only to hear the caller being told "that extension is busy" followed by their own voicemail greeting. No more lines left off the hook all night long.

VoiceWorks barely worked :-) but the Dialogic/VoiceGuide combo is unbeatable.

[SupportTeam]

BTW, I also am not using the inband signaling stuff because it seems to take 5 seconds to stop waiting for a key.

Could you post a log capturing this? It should be stopping waiting within a fraction of a second - if some tones are sent and any of the Inband Signalling patterns is matched. Maybe the pattern templates have not been defined? (see the help file section on Inband Signalling: http://www.voiceguid...dSignaling.htm)

it's always *DD - no other patterns.

For straightforward cases like that using the Get Numbers is an easier approach then defining templates in the "Inband Signaling Definition File".

the Dialogic/VoiceGuide combo is unbeatable.

Thanks :)

[SupportTeam]

In the next release of VG for Dialogic it will be possible to set the DTMF signal which will be interpreted by VG as transfer destination pickup.

The setting will be made in VG.INI, section: [PBX], entry name: TransferDestExtPickupDtmf

eg:

[PBX]

TransferDestExtPickupDtmf=A