Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: genesysnoob on May 01, 2015, 12:53:32 PM
-
Hello Folks
We do import data into the calling lists ( database). all the contact numbers look correct but some where ocs is deciding numbers as bad/invalid numbers and replacing them with all 9's
any one have any idea which step does it, is it the stored procedure or something else
i look into the ocs deployment guide and they haven't mentioned anything about wrong numbers or invalid numbers
-
Impossible... OCS doesn't do that. OCS asks your pbx to dial. It is your pbx who dials and makes the call or not. If not then your pbx via link informs why couldn't dial.
Maybe a sql treatment? Which could update the phone number.
-
I have experienced this before. Definitely your PBX. Lots of call policies to consider - check the DN (Directory Numbers) being used to dial out. You will probably find that one (or more of them) has either a vector or some pre-call checks which do not allow dialing out. Best way to check is to manually dial out through each DN in your Outbound configuration - use the same number to dial out to and one (or more) will not dial - then look at the PBX policies for that number.
Another way to think about it is; if you have a block of 20 numbers you are dialing out FROM, OCS will use them sequentially. If [b]two [/b]of them have a PBX policy, rule or vector applied, they may not dial out. For example - if it is the 6th and 12th number in the sequence then it'will occur twice in a 20 time cycle - sequentially;
12345[b][color=red]6[/color][/b]7891011[b][color=red]12[/color][/b]131415161718192012345[b][color=red]6[/color][/b]7891011[b][color=red]12[/color][/b]131415161718192012345[b][color=red]6[/color][/b]7891011[b][color=red]12[/color][/b]1314151617181920
It might seem random, but there will be a pattern!
Good luck finding it/them!