Transparency For Calling Number

[invoso.com]

Hi,

 

Is possible to transfer call with calling number?

If I'm using PRI ISDN with DIALOGIC card is possible to send calling number to dialed out number as calling number?

I identify now with my ISDN DDI number. I want to be transparent for transfered calls.

[SupportTeam]

If I'm using PRI ISDN with DIALOGIC card is possible to send calling number to dialed out number as calling number?

Yes.

 

From http://www.voiceguide.com/vghelp/source/html/modxfer.htm :

 

The Options field can be used to specify the outgoing CallerID used for the call by using the XML syntax. eg: specifying <CallerId>5551234</CallerId> would result in CallerId to be set to 5551234 on outgoing calls. Note that the CallerID settings in Config.xml can be used to override the settings made here as the Config.xml CallerId settings would take precedence.

 

So you just need to specify:

 

<CallerId>$RV_CIDNUMBER</CallerId>

 

in the 'Options' text box.

[invoso.com]

It doesn't working.

Other way?

[SupportTeam]

It should work. Can you post traces capturing the call? (both vgEngine and ktTel).

[invoso.com]

Our Telecom provider says that we are presenting us with 525611900 number

 

in script (moh_test.vgs) I setted

1st - <CallerId>525611999</CallerId>

2nd - <CallerId>99</CallerId>

3rd - empty OPTIONS window

 

 

Maybe I should to setting something in DIALOGIC CONFIGURATION MANAGER (DCM 6.0. PCI Build Number: 250)

 

We tested on other card (eicon diva server) this same PRI ISDN line and identification each ddi working properly, on D/600 JCT with VG don't.

log.zip

[SupportTeam]

Our Telecom provider says that we are presenting us with 525611900 number

Are you saying that telco says that when you place the outbound call the CallerID is always set to 525611900?

 

If the telco sees the same CallerID number regardless of what is set by VG (or if nothing is set by VG) then this suggests that the telco's switch may be setting the CallerID for this trunk regardless of what is set.

 

To confirm what is sent in actual ISDN messages you can do an ISDN trace using the isdiag.exe tool.

From http://www.voiceguide.com/vghelp/source/html/configisdnsetup.htm :

isdiag can be used to capture traces of the ISDN messages as well. The log files produced by isdiag need to be converted into human-readable form by using the isdtrace.exe application. Note that isdtrace.exe application is different to the isdntrace.exe application.

 

 

We tested on other card (eicon diva server) this same PRI ISDN line and identification each ddi working properly,

DDI (direct dial-in) usually relates to what numbers the inbound calls arrive on. Were you referring to inbound calls, or were you referring to setting CallerID on outbound calls?

 

 

100110.593 5812 13 fn LineMakeCall(iLineId=13, iCallRequestId=0 (ignored), strNumberToCall=[502131658], callprog=CONNECT_IMMEDIATELY, timeout=60, params:0,2,cid=[(null)],opt=[<calltype>DialAndConf</calltype><CallerId>525611999</CallerId>])

100110.609 5812 13 makecall protocol is: ISDN

100110.609 5812 CleanDialString [502131658]=>[502131658]

100110.609 5812 13 TelDriver_LineMakeCall hli->Dial_zsOtherCallProgressSettings=[<calltype>DialAndConf</calltype><CallerId>525611999</CallerId>]

100110.609 5812 13 Set_DX_CAP_ca_intflg zDial_DxCap.ca_intflg=DX_OPTDIS (CONNECT_IMMEDIATELY case)

100110.609 5812 13 CallProgressOption=[CONNECT_IMMEDIATELY] ca_intflg=265282336

100110.609 5812 MakeCall select driver. strDti=[dtiB1T5]

100110.609 5812 MakeCall driver non-HMP version used strDti=[dtiB1T5]

100110.609 5812 13 gc_MakeCall initialisation (SR)

100110.609 5812 13 set outgoing cid(13, []) ok

100110.609 5812 13 makecall defsrc none ()

100110.609 5812 13 gc_MakeCall [502131658] call (SR60)

100110.609 5812 13 gc_MakeCall ok. crn=280001f

[invoso.com]

Even we make transfer call TELCO see that we presenting 525611900 (leading DDI number) and no other.

We wrote in OPTIONS other numbers but it don't working.

what need I to setting in isdiag to be sure that <CallerId>$RV_CIDNUMBER</CallerId> working.

[SupportTeam]

Isdiag.exe is a Dialogic test application that you can use to capture a trace of the actual ISDN messages transmitted/received on the E1.

 

Start the trace just before the test outbound call and you will then be able to capture what ISDN SETUP message contains (which would include the CallerID setting on the outgoing SETUP message).

 

When you start ISDIAG (start it in DOS Command Window) you can see the option menu and one of them is used to start the ISDN trace.

 

Please see ISDIAG section of http://www.voiceguide.com/vghelp/source/html/configisdnsetup.htm for more information on starting ISDIAG.

[SupportTeam]

Looks like you are using a version that was provided in another thread (MOH Message related).

Looks like the changes made in those version introduced a bug that affected the outbound CallerID sending.

Please update system to the version below:

[old link removed]

This should fix the CallerID bug that you have encountered.

[invoso.com]

Hi!

 

Now working properly.

 

Thanks for a help!