Trying To Add Outbound

[yanky]

Dear Support,

The inbound has been working great for us. Both systems have been working fine for over 1 year. We now have been asked to do outbound on these 2 VG ivrs. VG states that it is 'Dialing...', the telco does not see anything coming in from us, so there must be an issue with the Dialogic cfg file? We are using the pdk_us_mf_io.cfg with minor adjustments. Can you let me know where to start trouble shooting this? The logs give us 'Timeout' message.

 

Thanks,

yanky

[SupportTeam]

Could you please post a copy of VoiceGuide's Trace Logs which captures the problem, this will allow us to see what happened.

 

Enable logging by setting the log levels to 10 in VG.INI as per below:

[Log]

 

VoiceGuide=10

CallLoader=0

VoicemailManager=0

EmailSender=0

ktTel=10

ktTts=0

Then restart VG and make a test call which demonstrates the problem.

 

Trace files will be created in VG's \log\ subdirectory.

 

Please post the traces.

 

When posting traces/scripts please .ZIP them up and post them as attachments.

[SupportTeam]

Please also .ZIP up and post your pdk_us_mf_io.cfg file.

[yanky]

Here they are.... THANKS VERY MUCH!

Let me know what you see.

1118tw.zip

1118vgm.zip

pdk_us_mf_io.zip

[SupportTeam]

Trace shows that The Dialogic card/drivers just report a 'disconnect due to timeout' 1 minute after making the call.

 

You mention that "telco does not see anything coming in from us".

 

How has the Telco configured those T1 lines? Do you have a detailed description of the specs of how the T1 lines are set up from the Telco's side?

 

 

152748.251 006 gc gc_MakeCall(819203802380) call

152748.251 006 gc gc_MakeCall(6, [819203802380], 60) ok

152748.251 006 call progress detection not enabled. We'll wait till after connect

152848.250 006 gc_GetMetaEvent returned. iDev=0, lEvtType=6, pEvtData=0x826, lEvtDataLen=84491600

152848.250 006 ev metaevent: cclibid=0x4, crn=0x4010006, evtdatap=0x5093d50, evtdev=0x6, evtlen=0x8, evttype=0x826, extevtdatap=0x0, flags=0x1, linedev=0x6, magicno=0xbad012fb, rfu1=0x2, usrattr=0x1be3e0 (usrattr=hli)

152848.250 006 ev GCEV_DISCONNECTED

152848.250 006 gc GCST_DISCONNECTED status gc:0:[success], cc_err=0 cclibid=0

152848.265 006 ResultInfo gcValue=1282(0x502) gcMsg=[Event caused by time-out] ccLibId=4 ccLibName=[GC_PDKRT_LIB] ccValue=[0x7de|GCRV_TIMEOUT|event caused by timeout ] ccMsg=[Timeout] additionalinfo=

[yanky]

I hope this helps.... We needed to may some wink options changes for the inbound.... and has been working for 1 plus years. This is the first time trying outbound on these circuits... If we get this to work... we will be adding the dial option to all 96 lines....

 

D4 AMI requested aka SF/AMI

jam bit 7

wink start

 

E&M Signaling Types

E&M (Ear & Mouth) signaling is typically used for trunks. Originally these were 8-wire circuits which interconnected different Central Offices. Using digital E&M signalling, there are only two physical states: busy (off-hook) and idle (on-hook).

SIGNAL FORWARD BACKWARD

DIRECTION (to system) (to CO)

IDLE / ON HOOK AB(CD) = 00(00) AB(CD) = 00(00)

BUSY / OFF HOOK AB(CD) = 11(11) AB(CD) = 11(11)

 

[SupportTeam]

Is the telco detecting that the channel is 'Seized' when VoiceGuide starts an outgoing call (ie. detects that the channel is taken 'off-hook')?

 

This is the first thing that needs to happen, the Telco must detect the channel as being 'seized' - which as per the telco supplied specs means that Dialogic should set bits AB to 11. The pdk_us_mf_io file you uploaded is specifying exactly that.

 

Once the telco detects the line seize we can move onto sorting out what winks are needed etc.

 

If the telco is detecting that the channel is 'Seized' then are they issuing a Wink in return? If yes then ask them how long their Wink is (in milliseconds).

 

 

If the telco is detecting that the channel is 'Seized' and is issuing a 'Wink' in return then you could try doing this:

 

Change:

 

All BOOLEAN_t CDP_OUT_DNIS_WINK_Needed = 1

 

to

 

All BOOLEAN_t CDP_OUT_DNIS_WINK_Needed = 0

 

and change:

 

All BOOLEAN_t CDP_OUT_ANI_WINK_Needed = 1

 

to

 

All BOOLEAN_t CDP_OUT_ANI_WINK_Needed = 0

 

 

 

Some questions:

 

Are you currently receiving both ANI and DNIS on the incoming calls on these lines?

 

Which Dialogic System Release drivers are used on this system?

[SupportTeam]

This application can be used to monitor the status of AB bits to confirm whether they are set to 11 by the Dialogic card when the outgoing call is placed:

 

http://resource.dialogic.com/telecom/suppo...itset/index.htm

 

 

Also enabling the Dialogic PDK log would let us see what is happening in the Dialogic card itself and what exactly it is doing when instructed to place the outgoing call:

 

http://www.dialogic.com/support/helpweb/dx...winnt/tn416.htm

[yanky]

THANKS!!!

Between these recommendations and 3 hours on the phone with our telco... We got it. They trapped what I was sending and then seeing what there switch was getting.

There were some ST and KPs that were not needed... we just needed to send the 1+10... total of 11 digits.

 

Should be good to go....

 

THANKS!

[SupportTeam]

Good to hear its working. Can you just tell us what do the acronyms "ST" and "KPs" stand for?

[yanky]

ST is for STart digit and by default was on and sending *,

KP, ?, but was also sending by default on that cfg file. The KP is/was used for sending special feature codes(per the telco tech). He couldn't remember what the KP actually stood for...

 

Thanks again.