I'm just testing the outbound dialing feature in a lab, and have run into the following problem:
I have following:
Customer dialing time: start (9:00) end (21:00)
dialing prefix - 9
international prefix - 00
Local Area Code: 44
44 -> Europe/London
34 -> Europe/Madrid
86 -> GMT-10 (for testing purposes, does not correspond to real China time).
Then, I upload a .CSV file into a campaign with the following information:
The dialing works, the agent receives the call, accepts it, and then the call is made.
if anyone is interested, although it has nothing to do with the question itself, the calls are translated to other extension on CUCM to be able to make a call.
The problem is that, they are all treated as in the same AREA CODE, although I have clearly defined area codes for each of those countries.
when the call appears it shows on the CAD as BAAreaCode: +00060
Therefore the calls are made through to China even when it's midnight there!!!???
I know I must be doing something wrong, but I don't know what?
Many thanks for your help,
Certainly looks like a bug - I have to say I've hit a lot of defects with the new subsystems on 7.x (Outbound/Agent Mail).
One thing I would try is using the 'named' zones (i.e. like Europe/Madrid rather than Etc/GMT+1), though either should work of course.
I'd probably raise a case at this point...