Hello all,
An odd problem that I've been discussing with a member on the Mitel forum who helped a great deal but we're a little stuck and could use some help.
We are using the ucadialler.exe programme in UCA 5.1 and associating it via a gp reg entry with callto: and tel: html tags. This is working fine but...
This is primarily because we have a crm system that has a phone book which presents all numbers in whatever format we want. It (by default) uses a bespoke TAPI interface which we now have working thanks to another member here (and a bit of fiddling) however as it turns out it is clunky and very Windows 95. We then turned to the ucadialler.exe programme which, when used via command line:
> ucadialler.exe 07770123456
works perfectly.
When used with a callto: tag the window comes up asking if it should (with a check box to never ask again) and says the following:
From: webpage
Program: ucadialler.exe
Address: callto:07770123456
which we thought BINGO, done.
However when it dials it then ends up dialling the following:
92255861110123456
which baffled us for a while, until I realised that the 225586 was the numbers on the digits C, A, L, L, T and O.
Mystery over, but problem remains.
I was advised to do the following in MCD:
Add an "ARS Digits Dialed" in the 3300:
Digits Dialed: 8225586 < we added a 9 at the beginning as they're all external calls
# of digits to follow: 10 < we have used 'Unknown' as we're dialling external numbers of varying length
Route < we changed this to list, the same as for '9'
Termination: 15 < we used 5, the same as for '9'
Sadly this has not worked.
Apparently this wasn't an issue in UCA < 5.1, but in 5.1 the ucadialler.exe sees letters and translates them to numbers! (a practice that is prevalent in the States, but one we don't use in the UK)
Any ideas? It's SO CLOSE to working!
An odd problem that I've been discussing with a member on the Mitel forum who helped a great deal but we're a little stuck and could use some help.
We are using the ucadialler.exe programme in UCA 5.1 and associating it via a gp reg entry with callto: and tel: html tags. This is working fine but...
This is primarily because we have a crm system that has a phone book which presents all numbers in whatever format we want. It (by default) uses a bespoke TAPI interface which we now have working thanks to another member here (and a bit of fiddling) however as it turns out it is clunky and very Windows 95. We then turned to the ucadialler.exe programme which, when used via command line:
> ucadialler.exe 07770123456
works perfectly.
When used with a callto: tag the window comes up asking if it should (with a check box to never ask again) and says the following:
From: webpage
Program: ucadialler.exe
Address: callto:07770123456
which we thought BINGO, done.
However when it dials it then ends up dialling the following:
92255861110123456
which baffled us for a while, until I realised that the 225586 was the numbers on the digits C, A, L, L, T and O.
Mystery over, but problem remains.
I was advised to do the following in MCD:
Add an "ARS Digits Dialed" in the 3300:
Digits Dialed: 8225586 < we added a 9 at the beginning as they're all external calls
# of digits to follow: 10 < we have used 'Unknown' as we're dialling external numbers of varying length
Route < we changed this to list, the same as for '9'
Termination: 15 < we used 5, the same as for '9'
Sadly this has not worked.
Apparently this wasn't an issue in UCA < 5.1, but in 5.1 the ucadialler.exe sees letters and translates them to numbers! (a practice that is prevalent in the States, but one we don't use in the UK)
Any ideas? It's SO CLOSE to working!