Inband Signalling File Error.

[Guest grzegorzj]

Hello

 

Inband signalling file works correct in VG6 but in VG7 doesn`t.

 

From log:

 

144800.506 5 [PBX]:InbandSignalConfig = C:\Program Files\VoiceGuide\conf\InbandSignaling_SiemensHiPath4000.txt

144800.522 5 ERROR v7.1.3615.29799 (2009-11-24 16:33:18.41) mainLoad INI Config : Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.

 

w .[1].()

w ..(String sAppPath)

 

 

Best Regards,

Grzesiek

[SupportTeam]

Please update system to this version of VG v7: [old link removed]
and post traces from this version if you still encounter any issues with the Inband Signaling.

[Guest grzegorzj]

 

 

Please update system to this version of VG v7: [old link removed]
and post traces from this version if you still encounter any issues with the Inband Signaling.

Now seems to be good. I will check this. Thank You.

[Guest grzegorzj]

Hello,

 

Inband signalling file is read by system but there is another error:

 

093053.180 6 3 2 Inband [*2011111524***] matched by pattern [[*][1-4]?????????[*][*][*]]

093053.180 6 3 2 Inband [inband_TOC] = [2]

093053.182 6 3 2 ERROR v7.1.3617.26571 (2009-11-26 14:45:42.40) Error_ScriptEventCode : Odwołanie do obiektu nie zostało ustawione na wystąpienie obiektu.

 

w vgEngine.ScriptRunsStateMachine.‘(Int32 iLineId, Int32 iCode, String sCode, Int32 lParam1, Int32 lParam2, Int32 lParam3, String sParam1, String sParam2, String sParam3)

w vgEngine.ScriptRunsStateMachine.(Int32 iLineId, Int32 crn, Int32 lCode, String sCode, Int32 lParam1, Int32 lParam2, Int32 lParam3, String sParam1, String sParam2, String sParam3)

093053.184 6 3 2 HangupCall, source=Error_ScriptEventCode, WorkModeScript=Running_Normal, yLineStateAppPov=[Connected], lPlayId=0, lRecId=0

093053.184 6 3 2 ScriptWorkingMode set Stopping, (called from HangupCall)

 

Please give me some advice with it.

 

Best Regards,

Grzegorz

[SupportTeam]

Please update system to this version of VG v7: [old link removed]
and post traces from this version if you still encounter any issues with the Inband Signaling.

[Guest grzegorzj]

Hi,

 

In attachment there is log from VG7.

1126_1129_vgEngine.zip

[SupportTeam]

Could you please .ZIP up and post the InbandSignaling_SiemensHiPath3000.txt file.

It loos like one of the definitions in it (specifically the pattern [*][*]?*****????[*][1-4]) is incorrect and that is causing errors when trying to interpret the inband signaling data.

[Guest grzegorzj]

Hi,

 

Ok, zip with 2 files attached (I want to use 3000 or 4000 in some cases).

InbandSignaling_SiemensHiPath3000.zip

[SupportTeam]

in InbandSignaling_SiemensHiPath3000.txt file.

 

change:

 

;3 digit station numbers, forwarded call - bluemedia zewnêtrznie 1

Pattern=[*][*][*]?*****????[*][1-4]

RV=Inband_TOC,4,1,Inband_Calling,7,3,Inband_Called,10,4,Inband_Info,17,1

 

;3 digit station numbers, forwarded call - bluemedia zewnêtrznie 2

Pattern=[*][*]?*****????[*][1-4]

RV=Inband_TOC,3,1,Inband_Calling,6,3,Inband_Called,9,4,Inband_Info,17,1

 

to:

 

 

;3 digit station numbers, forwarded call - bluemedia zewnêtrznie 1

Pattern=[*][*][*]?*****????[*][1-4]

RV=Inband_TOC,4,1,Inband_Calling,7,3,Inband_Called,10,4,Inband_Info,15,1

 

;3 digit station numbers, forwarded call - bluemedia zewnêtrznie 2

Pattern=[*][*]?*****????[*][1-4]

RV=Inband_TOC,3,1,Inband_Calling,6,3,Inband_Called,9,4,Inband_Info,14,1

 

Changes in Bold.

The values of '17' are more then the length of the pattern...

[Guest grzegorzj]

I changed this. Better this time. I will test it better.

[SupportTeam]

Future releases of v7 will flag instances of inband definition errors in the logs, but will continue on with the call.