GVP Obn Problem or OCS Problem...

Hi guyz, i have this proactive dialing ok, BUt today i realized that when the register has user-defined columns and them have a letter Ñ the call is not dialed, and teh call_result is updated in this way: OK.

So i do not know, where is teh problem, OCS? OBN? where…

some tip?

Hi,

It’s hard to say… I would recommend you to check logs and find out what has happened with the call. Post the logs here (debug level pls) if you need help.

R.

1 Like

Hi Rene, by looking logs seams that the URL is “malformed” when a world that has an “Ñ” is attached in teh user Data.

See the logs please.

1 Like

Instead of Ñ you need to add the HTML representation for it, like for á é í ó or ú…or ü

Hi Cav, friend, very sorry but ur recommendation it is not clear
Let me provide u further information.

I have a calling List. 4 Example this..
ID/Phone/Name. ok? so the values can be like this
01/123456789/Javier
02/345678912/Jorge

The problem apears when i have thsi register
02/345678912/Ñ or í,á,é, etc. <=only in thsi case teh call_result appears like OK.

HAve u deal with sth similar?

Hi,

It seems that OCS/OBN is not able to convert non-ASCII characters correctly so XML file sent to CFA becomes corrupted. I think you have just one option to make it working - remove non-ASCII characters from calling list.

Of course, you can try to raise ticket with Genesys but I would expect the answer will be “international characters are not supported”.

R.

1 Like

We decided to manage teh issue by the DB…

However i opened a SR, if i get a positive response, or solution i will posting it, if not ur prediction becomes true.

Thank u very much all of u guyz

2 Likes