cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Outbound Campaign - Call Result - Wrong number

sarda_sanjay
Explorer
0 Likes
294

Hi Gurus,

I created a sample preview Campaign with customer number as my phone number. I was able to start campaign from CDT but as soon I hit call button in campaign view, the results in wrong number. The same number works fine when I call from CDT stand alone. Can you please suggest what could be missed? Here are the logs from Call Dispatcher.

10:34:32.580 (24312/cmdThread ) TRC> <My number> matched pattern +* with value 99

10:34:32.580 (24312/cmdThread ) TRC> No destinations for a route

10:34:32.580 (24312/cmdThread ) TRC> Cem< [vambcmqcore] CALL_REJECTED {279EC03379F8E81181430050569F046D} _EVT=CALL_REJECTED;CALL_ID=279EC03379F8E81181430050569F046D;MODE=BADADDRESS;

I checked Switching route & Trunk. All look fine.

Thanks,
Sanjay

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Likes

Hi Sanjay,

I saw that you raised and customer incident from this case and there is already a colleague helping you. I kindly ask you to share final resolution with the community once we reach that point.

Typically in this kind of situation it's best to compare with working scenario like we are doing in the incident.

The log snip you have provided here already tells quite a lot. The key print is "No destinations for a route" which indicates that there is a route in the system without a phone gateway. In general next thing to investigate is the route configuration and maybe doing the same test with higher CD loglevel. That should provide more details about call routing and the root cause.

BR,
Jukka