Lumenvox Not Working

[a_jam_sandwich]

Hi we have purchased a licence for LumenVox but can't get it to work. I have read the following thread http://voiceguide.com/forums/index.php?sho...amp;hl=LumenVox and seem to have simular problems with the CSP not working.

 

I have set

 

CSP_Enabled to true and i'm using the firmware to D41JCSP.FWL but have the following using your modified CSPLive.exe

 

Test Mode = INTERACTIVE

Number of Channels = 1

Starting CSP Channel = 1

Speech Threshold = -40 dB

Stream Type = ec_stream

 

 

-----------------------------------

Modified by www.VoiceGuide.com v1.0

-----------------------------------

 

[12:49:23.510]: Opened prompt file Welcome.pcm.

 

[12:49:23.510]initialize_channels call

[12:49:23.510]gc_Start call

[12:49:26.619]gc_Start returned

opening device 1

[12:49:26.635][001]: Opened dxxxB1C1 on a Springware Analog device.

[12:49:26.635]Error: gc_Open failed on device [_pdk_na_an_io:V_dxxxB1C1]. Erro

rValue: 142 (Invalid device name).

Error in ec_setparm(1, DXCH_EC_TAP_LENGTH). Err Msg = Invalid, Lasterror = -1.

 

Please check if the current board and channel are CSP enabled.

 

Error in ec_setparm(ECCH_NLP). Err Msg = Invalid, Lasterror = -1.

Error in ec_setparm(ECCH_VADINITIATED). Err Msg = Invalid, Lasterror = -1.

Error in ec_setparm(DXCH_BARGEIN). Err Msg = Invalid, Lasterror = -1.

Error in ec_setparm(DXCH_BARGEINONLY). Err Msg = Invalid, Lasterror = -1.

Error in ec_setparm(DXCH_SPEECHPLAYTHRESH). Err Msg = Invalid, Lasterror = -1.

Error in ec_setparm(DXCH_SPEECHPLAYTRIGG). Err Msg = Invalid, Lasterror = -1.

Error in ec_setparm(ECCH_XFERBUFFERSIZE). Err Msg = Invalid, Lasterror = -1.

[12:49:26.744]wait_for_events call

 

[12:50:17.873]: No calls or events were received in the last 45 seconds. Existin

g the program.Error in ec_setparm(DXCH_EC_TAP_LENGTH). Err Msg = Invalid, Laster

ror = -1.

 

Please check if the current board and channel are CSP enabled.

 

Error in ec_setparm(DXCH_BARGEIN). Err Msg = Invalid, Lasterror = -1.

 

[12:50:17.873]: Stopping board.

[12:50:17.873]: Closing all file handles.

 

Have you any ideas?

 

 

Thanks

 

Andy

[SupportTeam]

The Dialogic card/drivers are replying that they cannot open the first port on the card:

 

[12:49:26.635]Error: gc_Open failed on device [_pdk_na_an_io:V_dxxxB1C1]. ErrorValue: 142 (Invalid device name).

 

Which version of Dialogic's System Release drivers are you using? Have you tried using Dialogic's own CSPLive.exe to confirm if that fails to open the ports as well?

 

[a_jam_sandwich]

QUOTE

The Dialogic card/drivers are replying that they cannot open the first port on the card:

[12:49:26.635]Error: gc_Open failed on device [_pdk_na_an_io:V_dxxxB1C1]. ErrorValue: 142 (Invalid device name).

Which version of Dialogic's System Release drivers are you using? Have you tried using Dialogic's own CSPLive.exe to confirm if that fails to open the ports as well?

Hi as you can see below the CSPlive is now functioning, all I did was reinstall the SR drivers, but its still not working in VoiceGuide YesNo demo.

Logs are as attached.

Test Mode = INTERACTIVE
Number of Channels = 1
Starting CSP Channel = 1
Speech Threshold = -40 dB
Stream Type = ec_stream


-----------------------------------
Modified by www.VoiceGuide.com v1.0
-----------------------------------

[16:37:14.832]: Opened prompt file Welcome.pcm.

[16:37:14.832]initialize_channels call
[16:37:14.832]gc_Start call
[16:37:16.457]gc_Start returned
opening device 1
[16:37:16.473][001]: Opened dxxxB1C1 on a Springware Analog device.
[16:37:16.520][001]: gc_Open passed for [_pdk_na_an_io:V_dxxxB1C1].
[16:37:16.848]wait_for_events call
[16:37:16.848][001]: gc_WaitCall passed. Waiting for unblocked event.
[16:37:16.848][001]: GCEV_UNBLOCKED event received. GlobalCall channel is waitin
g to receive a call.

[16:37:21.973][001]: GCEV_OFFERED event received crn=4010007(Opened file Rec001.
pcm) Accepting call.
[16:37:21.973][001]: GCEV_ACCEPT event received. Answering call.
[16:37:23.520][001]: GCEV_ANSWERED event received. ec_stream called. Prompt begi
ns. Please barge-in.
[16:37:23.520][001]: calling ec_stream ec_dev=5
[16:37:23.973][001]: TEC_VAD event received. Recording begins.
[16:37:23.988][001]: TDX_BARGEIN event received. Prompt is stopped.
[16:37:23.988][001]: TDX_PLAY event received. Play finished. Termination Reason:
BARGEIN.
[16:37:24.051][001]: stream_cb rx 2048 bytes chDev=5
[16:37:24.301][001]: stream_cb rx 2048 bytes chDev=5
[16:37:24.551][001]: stream_cb rx 2048 bytes chDev=5
[16:37:24.817][001]: stream_cb rx 2048 bytes chDev=5
[16:37:25.067][001]: stream_cb rx 2048 bytes chDev=5
[16:37:25.317][001]: stream_cb rx 2048 bytes chDev=5
[16:37:25.582][001]: stream_cb rx 2048 bytes chDev=5
[16:37:25.832][001]: stream_cb rx 2048 bytes chDev=5
[16:37:26.082][001]: stream_cb rx 2048 bytes chDev=5
[16:37:26.348][001]: stream_cb rx 2048 bytes chDev=5
[16:37:26.598][001]: stream_cb rx 2048 bytes chDev=5
[16:37:26.848][001]: stream_cb rx 2048 bytes chDev=5
[16:37:27.113][001]: stream_cb rx 2048 bytes chDev=5
[16:37:27.379][001]: stream_cb rx 2048 bytes chDev=5
[16:37:27.629][001]: stream_cb rx 2048 bytes chDev=5
[16:37:27.895][001]: stream_cb rx 2048 bytes chDev=5
[16:37:28.145][001]: stream_cb rx 2048 bytes chDev=5
[16:37:28.395][001]: stream_cb rx 2048 bytes chDev=5
[16:37:28.660][001]: stream_cb rx 2048 bytes chDev=5
[16:37:28.910][001]: stream_cb rx 2048 bytes chDev=5
[16:37:29.160][001]: stream_cb rx 2048 bytes chDev=5
[16:37:29.426][001]: stream_cb rx 2048 bytes chDev=5
[16:37:29.676][001]: stream_cb rx 2048 bytes chDev=5
[16:37:29.926][001]: stream_cb rx 2048 bytes chDev=5
[16:37:30.192][001]: stream_cb rx 2048 bytes chDev=5
[16:37:30.442][001]: stream_cb rx 2048 bytes chDev=5
[16:37:30.692][001]: stream_cb rx 2048 bytes chDev=5
[16:37:30.957][001]: stream_cb rx 2048 bytes chDev=5
[16:37:31.207][001]: stream_cb rx 2048 bytes chDev=5
[16:37:31.457][001]: stream_cb rx 2048 bytes chDev=5
[16:37:31.723][001]: stream_cb rx 2048 bytes chDev=5
[16:37:31.973][001]: stream_cb rx 2048 bytes chDev=5
[16:37:32.238][001]: stream_cb rx 2048 bytes chDev=5
[16:37:32.488][001]: stream_cb rx 2048 bytes chDev=5
[16:37:32.754][001]: stream_cb rx 2048 bytes chDev=5
[16:37:33.004][001]: stream_cb rx 2048 bytes chDev=5
[16:37:33.270][001]: stream_cb rx 2048 bytes chDev=5
[16:37:33.520][001]: stream_cb rx 2048 bytes chDev=5
[16:37:33.770][001]: stream_cb rx 2048 bytes chDev=5
[16:37:34.035][001]: stream_cb rx 2048 bytes chDev=5
[16:37:34.285][001]: stream_cb rx 2048 bytes chDev=5
[16:37:34.535][001]: stream_cb rx 2048 bytes chDev=5
[16:37:34.801][001]: stream_cb rx 2048 bytes chDev=5
[16:37:35.051][001]: stream_cb rx 2048 bytes chDev=5
[16:37:35.301][001]: stream_cb rx 2048 bytes chDev=5
[16:37:35.567][001]: stream_cb rx 2048 bytes chDev=5
[16:37:35.817][001]: stream_cb rx 2048 bytes chDev=5
[16:37:35.973][001]: stream_cb rx 1536 bytes chDev=5
[16:37:35.973][001]: TEC_STREAM event received. Recording finished. Termination
Reason: Normal Termination
[16:37:35.973][001]: Playing back recorded prompt. Hang up after play completes.

[16:37:48.270][001]: TDX_PLAY event received. Play finished. Termination Reason:
END OF DATA.

Logs.zip

[SupportTeam]

We will need to see the WireShark traces to see the MRCPv2 communication between VoiceGuide and LumenVox.

 

Please make a test call while doing the WireShark traces and post the WireShark traces and the VoiceGuide traces of the same call here and we can then see what happened.

[a_jam_sandwich]

Right looking into this more i've used Wireshark and no packets are going on ports 8060 or 8062. Using netstat only on server looks to be running .

 

Proto Local Address Foreign Address State

TCP rftas1:1030 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:1031 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:1032 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1033 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:activesync rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1035 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1036 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1037 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1038 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1039 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1040 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1041 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1068 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1069 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1070 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1071 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1079 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:1080 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:1081 rftas1.reactfast.co.uk:12004 ESTABLISHED

TCP rftas1:1082 rftas1.reactfast.co.uk:12004 ESTABLISHED

TCP rftas1:1083 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1084 rftas1.reactfast.co.uk:12002 ESTABLISHED

TCP rftas1:1087 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:1088 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:4642 rftas1.reactfast.co.uk:4644 ESTABLISHED

TCP rftas1:4644 rftas1.reactfast.co.uk:4642 ESTABLISHED

TCP rftas1:4647 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:4648 rftas1.reactfast.co.uk:12001 ESTABLISHED

TCP rftas1:8062 rftas1.reactfast.co.uk:4661 CLOSE_WAIT

TCP rftas1:12001 rftas1.reactfast.co.uk:1030 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:1031 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:1079 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:1080 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:1087 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:1088 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:4647 ESTABLISHED

TCP rftas1:12001 rftas1.reactfast.co.uk:4648 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1032 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1033 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:activesync ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1035 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1036 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1037 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1038 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1039 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1040 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1041 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1068 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1069 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1070 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1071 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1083 ESTABLISHED

TCP rftas1:12002 rftas1.reactfast.co.uk:1084 ESTABLISHED

TCP rftas1:12004 rftas1.reactfast.co.uk:1081 ESTABLISHED

TCP rftas1:12004 rftas1.reactfast.co.uk:1082 ESTABLISHED

TCP rftas1:ms-wbt-server reactw2k001.reactfast.co.uk:3546 ESTABLISHED

TCP rftas1:4702 rfcomms1.reactfast.co.uk:microsoft-ds TIME_WAIT

 

TCP rftas1:4704 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4705 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4706 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4707 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4708 rfcomms1.reactfast.co.uk:microsoft-ds TIME_WAIT

 

TCP rftas1:4710 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4711 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4712 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4713 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4714 rfcomms1.reactfast.co.uk:microsoft-ds TIME_WAIT

TCP rftas1:4716 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4717 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4718 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4719 reactfastsc.reactfast.co.uk:ldap TIME_WAIT

TCP rftas1:4720 rfcomms1.reactfast.co.uk:microsoft-ds TIME_WAIT

 

Im assuming that its VoiceGuide listening on port 8062 which would mean the MRCP isn't listening?

 

The MRCP server config file is as following and the MRCP server version is MRCPv2 1.0.0b Inital Beta Release

 

#-----------------------------------------------------------------

# this is the config file used by the Lumenvox Mrcpv2 Server.

# the format is very simple.

#

# lines starting with '#' are comments and are ignored.

# blank lines are also ignored.

#

# valid lines have the format 'param = value'.

# spaces are stripped from beginning of the line and

# from around the equal sign.

#

# PLEASE NOTE that the parameter names are case-sensitive.

#-----------------------------------------------------------------

 

#-----------------------------------------------------------------

#

# custom Log file name for the mrcp server

#-----------------------------------------------------------------

mrcp_server_log = MRCPv2_Log.txt

 

#-----------------------------------------------------------------

# this parameter sets the port on which the server will listen

# for incoming SIP messages.

#-----------------------------------------------------------------

sip_port = 5060

 

#-----------------------------------------------------------------

# this parameter is the lowest numbered port that will be used

# for RTP/RTCP and MRCP. two sequentially numbered ports will be

# used per RTP resource (one for RTP and the next for RTCP) and

# one port will be used for MRCP resource.

#-----------------------------------------------------------------

mrcp_server_port_base = 49922

 

#-----------------------------------------------------------------

# the maximum number of concurrent resources.

# practically speaking, this number can not be greater than the

# number of port licenses you have for your SRE.

#-----------------------------------------------------------------

mrcp_server_resmax = 200

 

#-----------------------------------------------------------------

# if you are running the MrcpServer and SRE on different machines,

# set this value to the IP address of the machine that is running

# the SRE.

#-----------------------------------------------------------------

sre_ip = 127.0.0.1

 

#-----------------------------------------------------------------

# enable_logging = 1 or 0 (default)

#-----------------------------------------------------------------

enable_logging = 1

 

#-----------------------------------------------------------------

# enable_sre_logging = 1 or 0 (default)

# enable or disable logging of response files in the Lang\Responses

# Directory of of the Speech Recognition Engine

#-----------------------------------------------------------------

enable_sre_logging = 0

 

#-----------------------------------------------------------------

# Vendor Specific parameters

#-----------------------------------------------------------------

 

choose_model =1

enable_lattice_scoring =1

initial_audio_time =100

wind_back_time =1000

barge_in_timeout =15000

end_of_speech_timeout =20000

snr_sensitivity_lvl =50

 

#-----------------------------------------------------------------

# MRCPv2 Standard parameters

#-----------------------------------------------------------------

 

sensitivity_lvl = 0.5

nbest_length =1

confidence_thrsld =0.45

no_input_timeout =10000

dtmf_termination_timeout =5000

recognizer_start_timers =true

recognition_timeout =10000

speech_complete_timeout =800

dtmf_inter_digit_timeout =5000

dtmf_buffer_time =5000

dtmf_term_char =#

save_waveform =false

waveform_url_location =

 

Many thanks

 

Andy

[a_jam_sandwich]

Sorry the executable version is LumenVox MRCPv2 Server80105.msi

[SupportTeam]

Is the LumenVox MRCPv2 service running?

 

You should at least see VoiceGuide's outgoing SIP calls to the LumenVox machine, regardless of whether the LumenVox is running or not.

 

If VoiceGuide is not establishing a SIP call to LumenVox then VoiceGuide itself is not properly configured.

[a_jam_sandwich]

QUOTE

Is the LumenVox MRCPv2 service running?

You should at least see VoiceGuide's outgoing SIP calls to the LumenVox machine, regardless of whether the LumenVox is running or not.

If VoiceGuide is not establishing a SIP call to LumenVox then VoiceGuide itself is not properly configured.

The MRCPv2 server is running and in services is listed as started . The UDP port for sip is OPEN on 5060 as shown in netstat -a the voiceguide config is

<?xml version="1.0"?>

<VoiceGuideConfig>

<Devices_ASR>
<Server_MRCPv2>
<ResourceType>speechrecog</ResourceType>
<ClientIP>127.0.0.1</ClientIP>
<ClientPort>8062</ClientPort>
<ServerIP>127.0.0.1</ServerIP>
<ServerPort>8060</ServerPort>
<RtpMin>49200</RtpMin>
<RtpMax>65300</RtpMax>
</Server_MRCPv2>
</Devices_ASR>

<Devices_Dialogic>

<Channels>

<Channel>
<Name>dxxxB1C1</Name>
<NetworkIf>dxxxB1C1</NetworkIf>
<Protocol>pdk_na_an_io</Protocol>
<RingsBeforeAnswer>0</RingsBeforeAnswer>
<script>C:\VoiceGuide\Scripts\SpeechRecogScripts\SpeechRecog_YesNo\SpeechRecognitionDemo_YesNo.vgs</Script>
<ConfigLine></ConfigLine>
<AllowDialOut>1</AllowDialOut>
<PopupCallerId>0</PopupCallerId>
<RV></RV>
</Channel>


<Channel>
<Name>dxxxB1C2</Name>
<NetworkIf>dxxxB1C2</NetworkIf>
<Protocol>pdk_na_an_io</Protocol>
<RingsBeforeAnswer>0</RingsBeforeAnswer>
<script>C:\VoiceGuide\Scripts\SpeechRecogScripts\SpeechRecog_YesNo\SpeechRecognitionDemo_YesNo.vgs</Script>
<ConfigLine></ConfigLine>
<AllowDialOut>1</AllowDialOut>
<PopupCallerId>0</PopupCallerId>
<RV></RV>
</Channel>


<Channel>
<Name>dxxxB1C3</Name>
<NetworkIf>dxxxB1C3</NetworkIf>
<Protocol>pdk_na_an_io</Protocol>
<RingsBeforeAnswer>0</RingsBeforeAnswer>
<script>C:\VoiceGuide\Scripts\SpeechRecogScripts\SpeechRecog_YesNo\SpeechRecognitionDemo_YesNo.vgs</Script>
<ConfigLine></ConfigLine>
<AllowDialOut>1</AllowDialOut>
<PopupCallerId>0</PopupCallerId>
<RV></RV>
</Channel>


<Channel>
<Name>dxxxB1C4</Name>
<NetworkIf>dxxxB1C4</NetworkIf>
<Protocol>pdk_na_an_io</Protocol>
<RingsBeforeAnswer>0</RingsBeforeAnswer>
<script>C:\VoiceGuide\Scripts\SpeechRecogScripts\SpeechRecog_YesNo\SpeechRecognitionDemo_YesNo.vgs</Script>
<ConfigLine></ConfigLine>
<AllowDialOut>1</AllowDialOut>
<PopupCallerId>0</PopupCallerId>
<RV></RV>
</Channel>

</Channels>



<Parameters_DxBd>

<Notes>
********************************************************************************
*************************
********************************************************************************
*************************

DXBD_ (voice board) parameters

Parameters specified here will be set for every DX (voice)
board found to be started by the DCM in the system.

********************************************************************************
*************************
********************************************************************************
*************************
</Notes>


<Parameter>
<Description>Flash time during dialing (10ms units)</Description>
<Key>DXBD_FLASHTM</Key>
<Value>10</Value>
<Default>10</Default>
</Parameter>

<NotUsedByDefault>

<Notes>
MF param setting causes long delays on some boards.
Remove NotUsedByDefault tags if the MF param setting is desired.
</Notes>

<Parameter>
<Description>MF Interdigit Delay (10 ms units)</Description>
<Key>DXBD_MFDELAY</Key>
<Value>6</Value>
<Default>6</Default>
</Parameter>

<Parameter>
<Description>MF Length of LKP Tone Maximum value: 15 (10 ms units)</Description>
<Key>DXBD_MFLKPTONE</Key>
<Value>10</Value>
<Default>10</Default>
</Parameter>

<Parameter>
<Description>Minimum MF On. Added to the standard MF tone duration before the tone is detected. (10 ms units)
The minimum detection duration is 65 ms for KP tones and 40 ms for all other tones.</Description>
<Key>DXBD_MFMINON</Key>
<Value>0</Value>
<Default>0</Default>
</Parameter>

<Parameter>
<Description>MF Minimum Tone Duration (10 ms units)</Description>
<Key>DXBD_MFTONE</Key>
<Value>6</Value>
<Default>6</Default>
</Parameter>

</NotUsedByDefault>


<Parameter>
<Description>Minimum Loop Current off time before it is reported</Description>
<Key>DXBD_MINLCOFF</Key>
<Value>50</Value>
<Default>50</Default>
</Parameter>


<Parameter>
<Description>Minimum offhook time</Description>
<Key>DXBD_MINOFFHKTM</Key>
<Value>250</Value>
<Default>250</Default>
</Parameter>

<Parameter>
<Description>Minimum Silence Off</Description>
<Key>DXBD_MINSLOFF</Key>
<Value>2</Value>
<Default>2</Default>
</Parameter>

<Parameter>
<Description>Minimum Silence On</Description>
<Key>DXBD_MINSLON</Key>
<Value>1</Value>
<Default>1</Default>
</Parameter>

<Parameter>
<Description>Minimum DTI Off - minimum time required between rings-received events</Description>
<Key>DXBD_MINTIOFF</Key>
<Value>5</Value>
<Default>5</Default>
</Parameter>

<Parameter>
<Description>Minimum DTI On - minimum time required for rings received event</Description>
<Key>DXBD_MINTION</Key>
<Value>5</Value>
<Default>5</Default>
</Parameter>

<Parameter>
<Description>Offhook Delay - period after offhook, during which no events are generated
e.g., no DTMF digits will be detected during this period.</Description>
<Key>DXBD_OFFHDLY</Key>
<Value>50</Value>
<Default>50</Default>
</Parameter>

<Parameter>
<Description>Pause Time. Delay caused by a comma in the dialing string (10ms units)</Description>
<Key>DXBD_PAUSETM</Key>
<Value>100</Value>
<Default>100</Default>
</Parameter>

<Parameter>
<Description>Silence and Non-silence Debounce</Description>
<Key>DXBD_S_BNC</Key>
<Value>4</Value>
<Default>4</Default>
</Parameter>

<Parameter>
<Description>DTMF Interdigit Delay. Time between digits in DTMF dialing (10ms units)</Description>
<Key>DXBD_T_IDD</Key>
<Value>15</Value>
<Default>10</Default>
</Parameter>

<Parameter>
<Description>DTMF length (duration) for dialing (10ms units)</Description>
<Key>DXBD_TTDATA</Key>
<Value>10</Value>
<Default>10</Default>
</Parameter>

<Parameter>
<Description>Silence on and off debounce time (10ms units)</Description>
<Notes>debunce length should be really small so that
we can easily tell when the transition happens</Notes>
<Key>DXBD_S_BNC</Key>
<Value>4</Value>
<Default>4</Default>
</Parameter>

</Parameters_DxBd>

</Devices_Dialogic>



<Notes>
********************************************************************************
*************************
********************************************************************************
*************************

CTI Devices

********************************************************************************
*************************
********************************************************************************
*************************
</Notes>


<Devices_CTI>
<CtiLink>

<CommsLink>
<Target></Target>
<Notes></Notes>
<IP></IP>
<Port></Port>
<Params></Params>
</CommsLink>

<MonitoredDevices>
<Ext></Ext>
<Ext></Ext>
</MonitoredDevices>

</CtiLink>
</Devices_CTI>


</VoiceGuideConfig>

Thanks

Andy

[a_jam_sandwich]

Also attached is the Wireshark packet log

[SupportTeam]

Please post VoiceGuide's Config.xml file

[a_jam_sandwich]

Please post VoiceGuide's Config.xml file

 

As attached

Configs.zip

[SupportTeam]

Do you have LumenVox installed on the same machine as VoiceGuide? LumenVox needs to be installed on a separate machine, only then can the communications between the two systems be debugged using WireShark.

[a_jam_sandwich]

I have now transfer the LumenVox on another server and have installed licences MRCPv2 and it is still not working.

 

I have setup the config as described in

 

http://www.voiceguide.com/vghelp/source/ht...onfig_intro.htm

 

I'm assuming that MRCPv2 is a SIP server and therefore inital authentication should take place on port 5060? yet the config on the page linked shows the port 8060 for setup.

 

Either way I have tried both ports 5060 and 8060 and have attached the logs, configs and packets for both ports in the attached file. Hopefully you will have some insite into whats happening.

 

 

Many thanks

 

Andy

Packets_Logs_Configs.zip

[a_jam_sandwich]

Have you any more news on this as we need it sorting urgently

 

Thanks

 

Andy

[SupportTeam]

The SIP port on the LumenVox's MRCPv2 server should be left at 8060.

 

You can use the TCPView.exe program from the Sysinternals suite to check on what port the LumenVox MrcpV2Server.exe task is listening to.

 

I suspect that you changed LumenVox's setting to 5060, as in the '8060' traces we see the 172.16.35.235 server responding with the ICMP 'Port Unreachable' message.

 

In the 5060 traces we see in the ktMrcp log that the MRCPv2 connection was established and that the LumenVox server returned a "nomatch" result after 10 seconds as no voice data was ever received by it:

 

<?xml version="1.0"?><result grammar=""><interpretation confidence="0"> <instance></instance> <input mode="speech"><nomatch/></input></interpretation></result>

 

Could you please try setting the system back to using the 8060 port for LumenVox communication and for now please try using a ULaw format sound files in the module [OurStartModule], instead of using TTS as you are doing right now.

 

Which Dialogic card are you using on this system?

 

For reference here are the traces created during a small test here in our lab setup. A D/41JCT card was used. Trace shows a call answered, 1.wav being played then recording a few seconds of callers speech and playing it back to them and then starting the module [OurStartModule] which has speech recognition grammar associated with it. Caller speaks 123 a few seconds after the sound file (VmbAccessGetVmbId.wav) started playing and LumenVox returns the correctly recognized words, which VG then plays back to caller in module [RepeatNumber].

 

It may be a good idea to download v7.0.6 from our WWW so that you have the latest released version and the tracing from our current testing and your system are similar.

log.zip

[a_jam_sandwich]

The SIP port on the LumenVox's MRCPv2 server should be left at 8060.

 

Ill try what you have suggested, All installs are default and the settings have not been changed in any way, apart from VoiceGuide which in the config the Device for MRCPv2 was added and the channels setup with the correct scripts, Everything else is as default.

 

using TCPmon which looks like a gloryfied version of netstat - a the results for the MRCPv2 server are as follows

 

MrcpV2Server.exe:3312 UDP rftas1:4748 *:*

MrcpV2Server.exe:3312 TCP rftas1:5060 rftas1:0 LISTENING

MrcpV2Server.exe:3312 UDP rftas1:5060 *:*

 

Please let me know what to change to get the server listening to the correct port from the default install?

 

 

Thanks

 

Andy

[SupportTeam]

The LumenVox MRCPv2 configuration file can be found at:

 

C:\Program Files\LumenVox\MRCPv2Server\config\mrcp.config

 

please set the sip_port setting to be 8060

 

I attach the mrcp.config file from our test LumenVox MRCPv2 server.

 

We'll have a second look at what LumenVox installs, our LumenVox test server had port set to 8060 for a long time now, would need to check how this was arrived at.

mrcp.config.zip

[a_jam_sandwich]

The LumenVox MRCPv2 configuration file can be found at:

 

C:\Program Files\LumenVox\MRCPv2Server\config\mrcp.config

 

please set the sip_port setting to be 8060

 

I attach the mrcp.config file from our test LumenVox MRCPv2 server.

 

We'll have a second look at what LumenVox installs, our LumenVox test server had port set to 8060 for a long time now, would need to check how this was arrived at.

 

Thank you. Ill use your confirm and install the test scripts again and let you know if its working.

 

Andy

[a_jam_sandwich]

I have change the port back in voiceguide, loaded you .ini file for LumenVox and reinstalled the example scripts ... and still it does not work?

 

Attached are the log files

 

Thanks

 

Andy

Logs.zip

[SupportTeam]

The ktMrcp trace shows the MRCPv2 server did not respond to the SIP INVITE request.

 

104554.074 1352 Process SIP Event [nua_i_state] Status 0 INVITE sent

104554.074 1352 SIP Call State [calling] (mrcp_sofia_on_state_changed client)

104554.074 1352 mrcp_sofia_on_state_changed end

104559.074 1352 mrcp_client_context_msg_process MRCP_CLIENT_SESSION_TERMINATE mrcp_client=07108F78, session=07186D90

 

A WireShark trace would be needed to confirm that the LumenVox did not respond.

 

Did you restart the LumenVox server after changing the mrcp.config file?

[a_jam_sandwich]

The ktMrcp trace shows the MRCPv2 server did not respond to the SIP INVITE request.

 

104554.074 1352 Process SIP Event [nua_i_state] Status 0 INVITE sent

104554.074 1352 SIP Call State [calling] (mrcp_sofia_on_state_changed client)

104554.074 1352 mrcp_sofia_on_state_changed end

104559.074 1352 mrcp_client_context_msg_process MRCP_CLIENT_SESSION_TERMINATE mrcp_client=07108F78, session=07186D90

 

A WireShark trace would be needed to confirm that the LumenVox did not respond.

 

Did you restart the LumenVox server after changing the mrcp.config file?

 

Right I've rebooted the MRCP server again and this time the session connected though the log file is still stating no confidence in the voice

 

134345.344 3556 003 raise generic mrcp|4313 RECOGNITION-COMPLETE|0 0 (0|0|0|<?xml version="1.0"?><result grammar=""><interpretation confidence="0"> <instance></instance> <input mode="speech"><nomatch/></input></interpretation></result>

|source:mrcp_on_channel_modify|)

 

No mater what I say its always 0 confidence, Im using "SpeechRecognitionDemo_YesNo.vgs" with none of the files modified or altered in any way downloaded off the examples page on this site.

 

Thanks

 

Andy

 

[SupportTeam]

We would need to see both the VoiceGuide traces and the WireShark trace to see what is happening.

 

Last WireShark trace from you (the 5060 trace) showed that the RTP was not sent to the LumenVox after the SIP connection was established, the traces would show if that is what’s happening again on your system or is it something else.

[a_jam_sandwich]

We would need to see both the VoiceGuide traces and the WireShark trace to see what is happening.

 

Last WireShark trace from you (the 5060 trace) showed that the RTP was not sent to the LumenVox after the SIP connection was established, the traces would show if that is what’s happening again on your system or is it something else.

 

As attached

Wireshark.zip

Logs.zip

[SupportTeam]

Could you please try selecting ULaw as VoiceGuide's default sound file format.

 

You will need to re-install VoiceGuide to make this change.

 

LumenVox only accepts ULaw connections.

 

The ALaw vs ULaw mismatch could be the reason why the RTP is not being sent to the LumenVox.

 

On analog systems it does not really matter whether you select ULaw or ALaw, regardless of what per of the world the system is deployed.

[a_jam_sandwich]

Could you please try selecting ULaw as VoiceGuide's default sound file format.

 

You will need to re-install VoiceGuide to make this change.

 

LumenVox only accepts ULaw connections.

 

The ALaw vs ULaw mismatch could be the reason why the RTP is not being sent to the LumenVox.

 

On analog systems it does not really matter whether you select ULaw or ALaw, regardless of what per of the world the system is deployed.

 

 

Still not working ... any more ideas as I'm losing my patience with it

 

Logs and packets attached

 

Thanks

 

Andy

Logs.zip

Wireshark.zip

[SupportTeam]

We can see in the traces that your LumenVox installation is responding with a "inactive" status in the SDP response"

 

 

150206.168 0700 Remote SDP

v=0

o=- 453148640740796436 5484117281818124331 IN IP4 172.16.35.235

s=-

c=IN IP4 172.16.35.235

t=0 0

m=application 49922 TCP/MRCPv2 9

a=resource:speechrecog

a=channel:6670635585727679908@speechrecog

a=setup:passive

a=connection:existing

a=cmid:1

m=audio 49924 RTP/AVP 0

a=rtpmap:0 PCMU/8000

a=inactive

a=mid:1

 

This is more then likely why the MRCPv2 clinet on VoiceGuide does not send any RTP to the LumenVox, because LumenVox says that it is inactive.

 

A correct response would look something like this:

 

181135.312 4124 Remote SDP

v=0

o=- 1838259746934141613 2813621613108501232 IN IP4 10.1.1.8

s=-

c=IN IP4 10.1.1.8

t=0 0

m=application 49922 TCP/MRCPv2 9

a=resource:speechrecog

a=channel:14594753493880321509@speechrecog

a=setup:passive

a=connection:existing

a=cmid:1

m=audio 49924 RTP/AVP 0

a=rtpmap:0 PCMU/8000

a=recvonly

a=mid:1

 

Which version of the LumenVox engine and MRCP server did you install? You would be able to see the version number as part of the filename (and the Engine and MRCPv2 server used should be from the same version).

 

[a_jam_sandwich]

Which version of the LumenVox engine and MRCP server did you install? You would be able to see the version number as part of the filename (and the Engine and MRCPv2 server used should be from the same version).

 

Engine8.0.305.exe

LVLicense8.0.305.exe

LumenVox MRCPv2 Server80105.msi

 

Thanks

 

Andy

 

[a_jam_sandwich]

Which version of the LumenVox engine and MRCP server did you install? You would be able to see the version number as part of the filename (and the Engine and MRCPv2 server used should be from the same version).

 

Engine8.0.305.exe

LVLicense8.0.305.exe

LumenVox MRCPv2 Server80105.msi

 

Thanks

 

Andy

 

Just to add these are my download options

 

 

Tuner 8.0.201 11/24/2007 Information Download Latest View Previous Versions

 

Windows Engine 8.0.305 2/13/2008 Information Download Latest View Previous Versions

 

Windows License Server 8.0.305 2/13/2008 Information Download Latest View Previous Versions

 

 

Also maybe an idea to reduce the forum flood control Im find 10minutes a long time to wait if I need to add something as you can't edit a post

 

 

Thanks

 

Andy

 

 

 

[a_jam_sandwich]

Have you any more information as I really need to get this sorted

 

Thanks

 

Andy

[a_jam_sandwich]

I am still waiting for a response on this?

 

Andy

[SupportTeam]

We are waiting for a response form LumenVox... we will try to get to you a version of the LumenVox engine which sends correct MRCPv2 responses.

[a_jam_sandwich]

We are waiting for a response form LumenVox... we will try to get to you a version of the LumenVox engine which sends correct MRCPv2 responses.

 

Greatly appreciated

 

Andy

[a_jam_sandwich]

Any news on a version I can try?

[a_jam_sandwich]

Any news on a version I can try?

 

I have now got all version the same 8.0.105 and have tried it again and again it it failing looking in the MRCPv2 log I notice this happening on every response

 

06/12/2008 16:25:01,064, INFO , MrcpV2RequestHandler.cpp:1365, Recognition Timeout 3539.734000 > 3539.656000!

06/12/2008 16:25:01,064, INFO , StreamRecognizer.cpp:57, Cancelling Decode

06/12/2008 16:25:01,064, INFO , StreamRecognizer.cpp:24, StreamRecognizer 01BF48B8 ,[PortLog:0][PortNum:14]Cancel Stream 9734

06/12/2008 16:25:01,064, INFO , StreamRecognizer.cpp:338, StreamRecognizer: 01BF48B8 port callback,stream status STREAM_STATUS_NOT_READY

 

I take it this is the reason no speech is being decoded? Any ideas what to do. I need to get this sort ASAP as this support request is now 20+ days old

[SupportTeam]

Could you please .ZIP and post all LumenVox log files (ie: entire contents in LumenVox's \Engine\Logs\ subdirectory).

 

Is it possible for us to have a look at both the VoiceGuide and LumenVox machines using www.logmein.com or VNC etc?

[SupportTeam]

Here is a patch provided by LumenVox:

 

Please do the following:

 

1. Go to your Control Panel >> Administrative Tools >> Services

2. Stop "LumenVox MRCPv2 Server" service

3. Go to C:\Program Files\Lumenvox\MRCPv2Server\bin

4. rename MrcpV2Server.exe to MrcpV2Server.exe.bak

5. Unzip the patch to this folder

6. Start "LumenVox MRCPv2 Server" service

 

Please post traces as before if you still have problems.

MrcpV2ServerPatchCRM00053075.zip

[a_jam_sandwich]

Could you please .ZIP and post all LumenVox log files (ie: entire contents in LumenVox's \Engine\Logs\ subdirectory).

 

Is it possible for us to have a look at both the VoiceGuide and LumenVox machines using www.logmein.com or VNC etc?

 

 

Here are all the log files and config files. The entire lumenvox directory is way to big to send (Some files were shrunk due to size).

 

Ill setup and PM you the details to remotely connect shortly

 

Andy

Lumonvox.zip

[SupportTeam]

Have you applied the patch from LumenVox?

[a_jam_sandwich]

What patch? so no

[a_jam_sandwich]

What patch? so no

 

Retrying with patch sorry doing 10 things at one will report back

[a_jam_sandwich]

What patch? so no

 

Retrying with patch sorry doing 10 things at one will report back

 

Still no dice. Logs are as attached, do you still want me to setup the remote connection?

 

Thanks

VoiceGuide.zip

LumenVox.zip

[SupportTeam]

do you still want me to setup the remote connection?

Yes. Please email connection details to support@voiceguide.com and include a link to this forum topic in the email.

[a_jam_sandwich]

do you still want me to setup the remote connection?

Yes. Please email connection details to support@voiceguide.com and include a link to this forum topic in the email.

 

E-mail is sent and servers standing by ...

[a_jam_sandwich]

do you still want me to setup the remote connection?

Yes. Please email connection details to support@voiceguide.com and include a link to this forum topic in the email.

 

E-mail is sent and servers standing by ...

 

NOTE: The vnc services have been removed until monday

[a_jam_sandwich]

You are now able to get onto these servers until 17:00 gmt. The email containing the passwords and IP was sent on friday please let me know if you require this information again.

 

Thanks

 

Andy

[SupportTeam]

Note to other readers of this thread:

 

When looking at the system we noticed that the Dialogic D/41JCT card did not have the "CSP Enabled" Firmware file specified as the firmware to use (this is done in the Dialogic Configuration Manager).

 

After selecting the d41jcsp.fwl file and restarting the Dialogic and VoiceGuide service the customer was able to confirm system operational, with the spoken digits correctly recognized (and spoken back to the caller by the SpeechRecog_Digits_Multiple.vgs demo script).

[a_jam_sandwich]

Seems that the fix was short lived. All of a sudden it has stopped working (not that it was to any great degree), I have attached all logs screen shots etc

 

It also seems that when the recognision was working it was unable to understand my common voice correctly. I would say the ratio of correct recognisions to incorrect was 4/9 (single numbers) which is unacceptable to say the least. We require this recognision to allow us to book jobs in a unmanned call centre by recognising the postcode allowing us to get an engineer within that area.

 

Thanks

 

Andy

Lumenvox___Logs.zip

Voiceguide___Logs.zip

packets.zip

[SupportTeam]

The traces show that you are asking for LumenVox to use the "US English" vocabulary. Are you based in US or in another country?

 

Does the postcode consist of just numbers or is it letters and numbers?

[a_jam_sandwich]

The traces show that you are asking for LumenVox to use the "US English" vocabulary. Are you based in US or in another country?

 

Does the postcode consist of just numbers or is it letters and numbers?

 

It consists on both numbers and letters and its using US English as I reinstalled Lumenvox when it stopped working along with reinstalls of the recognition examples. Before it was using en-GB

 

The problem now is when speaking it does nothing, before, it would stop talking at the prompt and come back with a recognition when you interrupted the prompt playing. Now nothing occurs.

 

I am also worried as this country has quite a varied array of people from different ethnic backgrounds that will be using the system.

 

 

Thanks

 

Andy

 

[SupportTeam]

There are a many calls in the supplied traces, but the speech recognition has only been attempted 3 times.

 

Which particular ASR attempt do you want us to look at? Please provide a timestamp.

 

From the traces we can see that the communication with LumenVox was correctly established each of those 3 times, but in all 3 cases the LumenVox responded after 10 seconds with a "no-match-maxtime" response.

 

The WireShark trace only has one connection captured. Was it one of the connections that is in the VoiceGuide trace as well? Which one?

 

Please restart VoiceGuide and LumenVox services and place just one call into the system, and use a script which just has one module - one that attempts to do Speech Recognition. The post the traces showing system startup and that one call, and the WireShark trace as well.

[a_jam_sandwich]

As requested

Lumenvox___Logs.zip

One_Call_Packets.zip

VoiceGuide___Logs.zip

[SupportTeam]

Traces show that for some reason VoiceGuide is not streaming the RTP data to the LumenVox. Not sure why this would be happening as looks like the connection was established fine and no errors can be seen in the trace.

 

I understand this setup was communicating with LumenVox before, so please let us know if you can think of anything that was changed on the system since the connection was working fine.

 

We have just checked same version on our test system here and the communication with LumenVox was established OK.

 

At this stage we'd recommend doing a reinstall of the software to make sure that all the DLLs are in place.

 

We are going to create a version which has some further debugging in the RTP stream setup routine and make it available on Monday, using that version on your system should give us more detailed information in where the problem lies.

[a_jam_sandwich]

Due to the fact that the recognition was so dire I upgraded our Lumenvox server to version 8.0.305 after this point the system stopped working altogether, as this looked like the causing factor I downgraded the server back to 8.0.105 but the problem still persisted.

 

Since then, Lumenvox has had a fresh install of 8.0.105 on a new server but the problem is still there, I taking it that it was coincidence that it stopped working on a Lumenvox upgrade.

 

I shall now reinstall the VoiceGuide software to see if that fixes it, I’m not here Monday so Ill report back Tuesday when the debug version of VoiceGuide is ready

 

 

Thanks

 

Andy

[a_jam_sandwich]

Found the SIP logs on the root of the HDD don't know if that will help?

0704_ktSip.zip

[a_jam_sandwich]

Reinstalling VoiceGuide has made no diffrence

[SupportTeam]

Did you install the MrcpV2ServerPatchCRM00053075.zip ?

 

Attached to post #36 of this thread.

[a_jam_sandwich]

Good point not since the reinstall I will get on that now

[a_jam_sandwich]

This has made no diffrence

[SupportTeam]

Please post traces from this debug version: [old link removed]

Hopefully the traces will give us more information on why the RTP channel is not being set up.

[a_jam_sandwich]

I installed the debug version, but this cause the the licence manager to stop work, the line status manager stopped working and dtmf recognision stopped working and since the was a live server we had no choice but to re install the production version fixing all the above.

 

We have a new server comming friday and will install VoiceGuide debug on it so it will not interfear with live operations, i'll report back then.

 

Thanks

 

Andy

[a_jam_sandwich]

Sorry that it has took me so long to get back to you but please find the attached log file and packets from your asr debug release.

 

Please let me know if you want to connected to our servers?

 

Thanks

 

Andy

log.zip

[SupportTeam]

From the MRCP v2 traces we can see that the MRCPv2 server (LumenVox) is not responding correctly to the connection setup request.

 

The correct SDP response at call setup time is (see our sample of working ASR as posted in previoulsy):

 

181135.312 4124 Remote SDP

[v=0

o=- 1838259746934141613 2813621613108501232 IN IP4 10.1.1.8

s=-

c=IN IP4 10.1.1.8

t=0 0

m=application 49922 TCP/MRCPv2 9

a=resource:speechrecog

a=channel:14594753493880321509@speechrecog

a=setup:passive

a=connection:existing

a=cmid:1

m=audio 49924 RTP/AVP 0

a=rtpmap:0 PCMU/8000

a=recvonly

a=mid:1

]

 

and on your system the reponse is:

 

150418.129 0200 Remote SDP

[v=0

o=- 6782532459847414030 5345053320815094113 IN IP4 172.16.32.80

s=-

c=IN IP4 172.16.32.80

t=0 0

m=application 4294967295 TCP/MRCPv2 9

a=resource:speechrecog

a=channel:12698309039270920547@speechrecog

a=setup:passive

a=connection:existing

a=cmid:1

m=audio 0 RTP/AVP 9

]

 

notice the rtpmap and audio fields are missing in response on your system, so the MRCPv2 stack does not know what sound format it should use in comunicating with LumenVox, and what port to send it to, hence it never establishes the RTP stream. ie. never sends any voice data.

 

The SDP issued by VoiceGuide to the MRCPv2 server looks OK:

 

150418.098 0200 Local SDP

[v=0

o=OpenMRCPClient 0 0 IN IP4 172.16.35.220

s=-

c=IN IP4 172.16.35.220

t=0 0

m=application 9 TCP/MRCPv2 1

a=setup:active

a=connection:existing

a=resource:speechrecog

a=cmid:1

m=audio 49200 RTP/AVP 0 8

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=sendonly

a=mid:1

]

 

which is same as on our test system:

 

181135.000 4124 Local SDP

[v=0

o=OpenMRCPClient 0 0 IN IP4 10.1.1.10

s=-

c=IN IP4 10.1.1.10

t=0 0

m=application 9 TCP/MRCPv2 1

a=setup:active

a=connection:existing

a=resource:speechrecog

a=cmid:1

m=audio 49200 RTP/AVP 0 8

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=sendonly

a=mid:1

]

 

 

So it looks like the LumenVox setup on your system is different to what we have on our test machine.

 

I attach the full DIR listing of LumenVox directory from our test LumenVox server. You can compare the dates/times/sizes of files to confirm what are the differences (you could do a DIR /S > mydir.txt and do a DIFF of your output and attached file).

 

 

Its probabaly not a good idea to just try to ignore lack of rtpmap in LumenVox response as most likely the lack of rtpmap field indicates a deeper problem in LumenVox install, and its that issue that should be resolved.

LumenVox_Dir_Listing.txt

[SupportTeam]

Maybe this is just a configuration problem?

 

Please go over the config files again to make sure that the port ranges that LumenVox MRCPv2 should be using are correctly set up.