Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

ICM 7.5.6 Outbound - DialogicTest error

Hello All.

I have an outbound dialer with 4 ports, which registered and ready, everything seems fine.

As a part of the verification of my installation, I have used the DialogicTest tool as follows :.

  • I stopped the Dialer (the ports get un-registered)
  • I have started the Dialogictest tool (the ports get registered again)
  • When I try to dial a "station" I only hear a short ring on my phone, and the port is disconnected again.

Hopefully you guys can help me fix this problem.

It's the same problem with all 4 ports??

From the logs I receive this :

d 0 38993 #100

Dialing Succeeded...port: 3, phone: 38993

> 18:25:33 Trace: (CRMan) Dial, port: 003, phone 38993

18:25:33 Trace: (SP) Port: 003 Changing state from SP_STATE_READY to SP_STATE_DIALING_NUMBER

18:25:33 Trace: (SP) Line: 1: Changing state from SP_LINESTATE_IDLE to SP_LINESTATE_AWAITING_DIALTON

E

18:25:33 Trace: (SP) Line: 2: Changing state from SP_LINESTATE_IDLE to SP_LINESTATE_IDLE

18:25:33 Trace: (SP) port: 003 Received Receive Call State Msg - callstate=Off Hook, CRN=152837002

18:25:33 Trace: (TST) port: 003, event: [EVENT_DIALING_COMPLETE], result: [none]

18:25:33 Trace: (SP) port: 003 Received Display Text Msg: 38983

18:25:33 Trace: (SP) port: 003 Received Station Start Tone Msg - tone: InsideDialTone

18:25:33 Trace: (SP) Port: 003, dialing digits: [38993]

18:25:33 Trace: (SP) Line: 1: Changing state from SP_LINESTATE_AWAITING_DIALTONE to SP_LINESTATE_DIA

LING_NUMBER

18:25:33 Trace: (SP) port: 003 Received Station Stop Tone Msg

18:25:33 Trace: (SP) port: 003 Received Receive Call State Msg - callstate=Call Proceed, CRN=152837

002

18:25:33 Trace: (SP) port: 003 Received Station Call Info Msg. line=1 crn=152837002

18:25:33 Trace: (SP) port: 003 Received Station Start Tone Msg - tone: AlertingTone

18:25:33 Trace: (SP) port: 003 Received Receive Call State Msg - callstate=Ring Out, CRN=152837002

18:25:33 Trace: (TST) port: 003, event: [EVENT_DIALING_COMPLETE], result: [none]

18:25:33 Trace: (SP) port: 003 Received Station Call Info Msg. line=1 crn=152837002

18:25:34 Trace: (SP) No Answer TIMEOUT : currentTime=1263921934, starttime=1263921933, noanswer=0

18:25:34 Trace: (TST) port: 003, event: [EVENT_DIALING_COMPLETE], result: [eCONN_STATE_NOANSWER]

18:25:34 Trace: (SP) Port: 003 Changing state from SP_STATE_DIALING_NUMBER to SP_STATE_CALL_FAILED

18:25:34 Trace: (SP) Port: 003 Changing state from SP_STATE_CALL_FAILED to SP_STATE_DROPPING_LINE1

18:25:34 Trace: (SP) port: 003 Received Station Stop Tone Msg

18:25:34 Trace: (SP) port: 003 Received Receive Call State Msg - callstate=On Hook, CRN=152837002

18:25:34 Trace: (SP) port: 003 Primary line hangup

18:25:34 Trace: (SP) Line: 1: Changing state from SP_LINESTATE_DIALING_NUMBER to SP_LINESTATE_IDLE

18:25:34 Trace: (TST) port: 003, event: [EVENT_HANGUP], result: [none]

18:25:34 Trace: (SP) Port: 003 Changing state from SP_STATE_DROPPING_LINE1 to SP_STATE_READY

1 ACCEPTED SOLUTION

Accepted Solutions

Re: ICM 7.5.6 Outbound - DialogicTest error

Get rid of the pound sign:

d 0 38993 100

The dialer couldn't read "#100" so it was defaulting the timeout to 0 seconds.

2 REPLIES

Re: ICM 7.5.6 Outbound - DialogicTest error

Get rid of the pound sign:

d 0 38993 100

The dialer couldn't read "#100" so it was defaulting the timeout to 0 seconds.

Community Member

Re: ICM 7.5.6 Outbound - DialogicTest error

Thanks Ed for your answer. Now it works.

I think the line ">d 0 30" from the Outbound Option Guide for Cisco Unified Contact Center Enterprise and Hosted, Release 7.5(1) - page 78 must have confused me....?

Regards

slavr

307
Views
0
Helpful
2
Replies
CreatePlease to create content