You can set MRCP parameters either globally in the MRCP profile with the <recogparams> tag or on a specific request by prefixing {param="val"} to the grammar.<br><br>Read the MRCP RFCs and the Nuance documentation for all available parameters and their default values.<br>
<br>For MRCPv1 (RFC 4463):<br><pre class="newpage"><span class="h4"><h4><a name="section-8.4.5">8.4.5</a>. No Input Timeout</h4></span>
When recognition is started and there is no speech detected for a
certain period of time, the recognizer can send a RECOGNITION-
COMPLETE event to the client and terminate the recognition operation.
The no-input-timeout header field can set this timeout value. The
value is in milliseconds. This header field MAY occur in RECOGNIZE,
<span class="grey">Shanmugham, et al. Informational [Page 45]</span>
</pre><pre class="newpage"><a name="page-46" id="page-46" href="http://tools.ietf.org/html/rfc4463#page-46" class="invisible"> </a>
<span class="grey"><a href="http://tools.ietf.org/html/rfc4463">RFC 4463</a> MRCP by Cisco, Nuance, and Speechworks April 2006</span>
SET-PARAMS, or GET-PARAMS. The value for this field ranges from 0 to
MAXTIMEOUT, where MAXTIMEOUT is platform specific. The default value
for this field is platform specific.
no-input-timeout = "No-Input-Timeout" ":" 1*DIGIT CRLF
<span class="h4"><h4><a name="section-8.4.6">8.4.6</a>. Recognition Timeout</h4></span>
When recognition is started and there is no match for a certain
period of time, the recognizer can send a RECOGNITION-COMPLETE event
to the client and terminate the recognition operation. The
recognition-timeout parameter field sets this timeout value. The
value is in milliseconds. The value for this field ranges from 0 to
MAXTIMEOUT, where MAXTIMEOUT is platform specific. The default value
is 10 seconds. This header field MAY occur in RECOGNIZE, SET-PARAMS
or GET-PARAMS.
recognition-timeout = "Recognition-Timeout" ":" 1*DIGIT CRLF<br><br></pre><pre class="newpage"><span class="h4"><h4><a name="section-8.4.10">8.4.10</a>. Recognition Start Timers</h4></span>
This parameter MAY BE sent as part of the RECOGNIZE request. A value
of false tells the recognizer to start recognition, but not to start
the no-input timer yet. The recognizer should not start the timers
until the client sends a RECOGNITION-START-TIMERS request to the
recognizer. This is useful in the scenario when the recognizer and
synthesizer engines are not part of the same session. Here, when a
kill-on-barge-in prompt is being played, you want the RECOGNIZE
request to be simultaneously active so that it can detect and
implement kill-on-barge-in. But at the same time, you don't want the
recognizer to start the no-input timers until the prompt is finished.
The default value is "true".
recognizer-start-timers = "Recognizer-Start-Timers" ":"
boolean-value CRLF</pre><br><pre class="newpage"><span class="h4"><h4><a name="section-8.4.12">8.4.12</a>. Speech Complete Timeout</h4></span>
This header field specifies the length of silence required following
user speech before the speech recognizer finalizes a result (either
accepting it or throwing a nomatch event). The speech-complete-
timeout value is used when the recognizer currently has a complete
match of an active grammar, and specifies how long it should wait for
more input before declaring a match. By contrast, the incomplete
timeout is used when the speech is an incomplete match to an active
grammar. The value is in milliseconds.
speech-complete-timeout = "Speech-Complete-Timeout" ":"
1*DIGIT CRLF
<span class="grey">Shanmugham, et al. Informational [Page 48]</span>
</pre><pre class="newpage"><a name="page-49" id="page-49" href="http://tools.ietf.org/html/rfc4463#page-49" class="invisible"> </a>
<span class="grey"><a href="http://tools.ietf.org/html/rfc4463">RFC 4463</a> MRCP by Cisco, Nuance, and Speechworks April 2006</span>
A long speech-complete-timeout value delays the result completion
and, therefore, makes the computer's response slow. A short speech-
complete-timeout may lead to an utterance being broken up
inappropriately. Reasonable complete timeout values are typically in
the range of 0.3 seconds to 1.0 seconds. The value for this field
ranges from 0 to MAXTIMEOUT, where MAXTIMEOUT is platform specific.
The default value for this field is platform specific. This header
field MAY occur in RECOGNIZE, SET-PARAMS, or GET-PARAMS.
<span class="h4"><h4><a name="section-8.4.13">8.4.13</a>. Speech Incomplete Timeout</h4></span>
This header field specifies the required length of silence following
user speech, after which a recognizer finalizes a result. The
incomplete timeout applies when the speech prior to the silence is an
incomplete match of all active grammars. In this case, once the
timeout is triggered, the partial result is rejected (with a nomatch
event). The value is in milliseconds. The value for this field
ranges from 0 to MAXTIMEOUT, where MAXTIMEOUT is platform specific.
The default value for this field is platform specific.
speech-incomplete-timeout = "Speech-Incomplete-Timeout" ":"
1*DIGIT CRLF
The speech-incomplete-timeout also applies when the speech prior to
the silence is a complete match of an active grammar, but where it is
possible to speak further and still match the grammar. By contrast,
the complete timeout is used when the speech is a complete match to
an active grammar and no further words can be spoken.
A long speech-incomplete-timeout value delays the result completion
and, therefore, makes the computer's response slow. A short speech-
incomplete-timeout may lead to an utterance being broken up
inappropriately.
The speech-incomplete-timeout is usually longer than the speech-
complete-timeout to allow users to pause mid-utterance (for example,
to breathe). This header field MAY occur in RECOGNIZE, SET-PARAMS,
or GET-PARAMS.</pre><br><br><br><br>For MRCPv2:<br><br><pre class="newpage"><span class="h4"><h4><a name="section-9.4.6">9.4.6</a>. No Input Timeout</h4></span>
When recognition is started and there is no speech detected for a
certain period of time, the recognizer can send a RECOGNITION-
COMPLETE event to the client with a Completion-Cause of "no-input-
timeout" and terminate the recognition operation. The client can use
the no-input-timeout header field to set this timeout. The value is
in milliseconds and may range from 0 to an implementation specific
maximum value. This header field MAY occur in RECOGNIZE,
"SET-PARAMS" or "GET-PARAMS". The default value is implementation
specific.
no-input-timeout = "No-Input-Timeout" ":" 1*19DIGIT CRLF
<span class="h4"><h4><a name="section-9.4.7">9.4.7</a>. Recognition Timeout</h4></span>
When recognition is started and there is no match for a certain
period of time, the recognizer can send a RECOGNITION-COMPLETE event
to the client and terminate the recognition operation. The
Recognition-Timeout header field allows the client to set this
timeout value. The value is in milliseconds. The value for this
header field ranges from 0 to an implementation specific maximum
value. The default value is 10 seconds. This header field MAY occur
in RECOGNIZE, SET-PARAMS or GET-PARAMS.
recognition-timeout = "Recognition-Timeout" ":" 1*19DIGIT CRLF</pre><br><pre class="newpage"><span class="h4"><h4><a name="section-9.4.14">9.4.14</a>. Start Input Timers</h4></span>
This header field MAY be sent as part of the RECOGNIZE request. A
value of false tells the recognizer to start recognition, but not to
start the no-input timer yet. The recognizer MUST NOT start the
timers until the client sends a START-INPUT-TIMERS request to the
recognizer. This is useful in the scenario when the recognizer and
synthesizer engines are not part of the same session. In such
configurations, when a kill-on-barge-in prompt is being played (see
<a href="http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-25#section-8.4.2">Section 8.4.2</a>), the client wants the RECOGNIZE request to be
simultaneously active so that it can detect and implement kill-on-
barge-in. However, the recognizer SHOULD NOT start the no-input
timers until the prompt is finished. The default value is "true".
start-input-timers = "Start-Input-Timers" ":" BOOLEAN CRLF
<span class="grey">Burnett & Shanmugham Expires January 12, 2012 [Page 86]</span>
</pre><pre class="newpage"><a name="page-87" id="page-87" href="http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-25#page-87" class="invisible"> </a>
<span class="grey">Internet-Draft MRCPv2 July 2011</span>
<span class="h4"><h4><a name="section-9.4.15">9.4.15</a>. Speech Complete Timeout</h4></span>
This header field specifies the length of silence required following
user speech before the speech recognizer finalizes a result (either
accepting it or generating a nomatch event). The speech-complete-
timeout value applies when the recognizer currently has a complete
match against an active grammar, and specifies how long the
recognizer MUST wait for more input before declaring a match. By
contrast, the incomplete timeout is used when the speech is an
incomplete match to an active grammar. The value is in milliseconds.
speech-complete-timeout = "Speech-Complete-Timeout" ":" 1*19DIGIT CRLF
A long speech-complete-timeout value delays the result to the client
and therefore makes the application's response to a user slow. A
short speech-complete-timeout may lead to an utterance being broken
up inappropriately. Reasonable speech complete timeout values are
typically in the range of 0.3 seconds to 1.0 seconds. The value for
this header field ranges from 0 to an implementation specific maximum
value. The default value for this header field is implementation
specific. This header field MAY occur in RECOGNIZE, "SET-PARAMS" or
"GET-PARAMS".
<span class="h4"><h4><a name="section-9.4.16">9.4.16</a>. Speech Incomplete Timeout</h4></span>
This header field specifies the required length of silence following
user speech after which a recognizer finalizes a result. The
incomplete timeout applies when the speech prior to the silence is an
incomplete match of all active grammars. In this case, once the
timeout is triggered, the partial result is rejected (with a
Completion-Cause of "partial-match"). The value is in milliseconds.
The value for this header field ranges from 0 to an implementation
specific maximum value. The default value for this header field is
implementation specific.
speech-incomplete-timeout = "Speech-Incomplete-Timeout" ":" 1*19DIGIT
CRLF
The speech-incomplete-timeout also applies when the speech prior to
the silence is a complete match of an active grammar, but where it is
possible to speak further and still match the grammar. By contrast,
the complete timeout is used when the speech is a complete match to
an active grammar and no further spoken words can continue to
represent a match.
A long speech-incomplete-timeout value delays the result to the
client and therefore makes the application's response to a user slow.
A short speech-incomplete-timeout may lead to an utterance being
<span class="grey">Burnett & Shanmugham Expires January 12, 2012 [Page 87]</span>
</pre><pre class="newpage"><a name="page-88" id="page-88" href="http://tools.ietf.org/html/draft-ietf-speechsc-mrcpv2-25#page-88" class="invisible"> </a>
<span class="grey">Internet-Draft MRCPv2 July 2011</span>
broken up inappropriately.
The speech-incomplete-timeout is usually longer than the speech-
complete-timeout to allow users to pause mid-utterance (for example,
to breathe). This header field MAY occur in RECOGNIZE, "SET-PARAMS"
or "GET-PARAMS".<br><br><br></pre><br><br><div class="gmail_quote">On Wed, Sep 14, 2011 at 6:04 AM, grmt <span dir="ltr"><<a href="mailto:garmt.noname@gmail.com">garmt.noname@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="color:#1F497D">Hi, <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal"><span style="color:#1F497D">Not that I have any experience with UniMRCP in combination with Nuance ASR, however it seems to me that the MRCP server (i.e. Nuance) tells you that it did not receive any input. I believe having read somewhere that the default no-input-timeout on Nuance is 8 (s). <u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1F497D">If you want to manipulate the no-input-timeout on a MRCP request basis, I think you will have to change mod_unimrcp.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1F497D">You may also manipulate the global request-timout which by default is 10 (s).<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1F497D">I bet that if you set this lower than 8(s), it is FS that will timeout …<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Now why Nuance is not receiving any input (rtp) I don’t know.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1F497D"><u></u> <u></u></span></p><p class="MsoNormal">
<span style="color:#1F497D">If I understand correctly from the log below you play a wav file and you want that to be recognized?<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1F497D">Maybe you need a little bit more time between triggering the recognizer and playing the wav file?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="color:#1F497D">You may want to use wireshark to capture the RTP stream between FS and NUANCE.<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1F497D"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Garmt<u></u><u></u></span></p><p class="MsoNormal"><span style="color:#1F497D"><u></u> <u></u></span></p><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:freeswitch-users-bounces@lists.freeswitch.org" target="_blank">freeswitch-users-bounces@lists.freeswitch.org</a> [mailto:<a href="mailto:freeswitch-users-bounces@lists.freeswitch.org" target="_blank">freeswitch-users-bounces@lists.freeswitch.org</a>] <b>On Behalf Of </b>Glen Ganderton<br>
<b>Sent:</b> Wednesday, September 14, 2011 08:04<br><b>To:</b> <a href="mailto:freeswitch-users@lists.freeswitch.org" target="_blank">freeswitch-users@lists.freeswitch.org</a><br><b>Subject:</b> [Freeswitch-users] Where to set parameter for input timeout<u></u><u></u></span></p>
</div></div><div><div></div><div class="h5"><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><span lang="EN-AU">Hey Guys,<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">Im trying to find where I would set the parameter for input timeout. Im using FreeSWITCH as an MRCP client to my Nuance server and what is happening is if FreeSWITCH doesn’t detect any speech in around 8-10 seconds I get an input-timeout, any idea’s?<u></u><u></u></span></p>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in"><p class="MsoNormal"><span lang="EN-AU"><u></u> <u></u></span></p></div><p class="MsoNormal"><span lang="EN-AU">MRCP/2.0 158 RECOGNIZE 2<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">Channel-Identifier: 40@speechrecog<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">Cancel-If-Queue: false<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">Content-Type: text/uri-list<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">Content-Length: 21<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-AU">session:nuance5-mrcp2<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.728662 [INFO] mpf_rtp_stream.c:1092 Generate RTCP SR [ssrc:<a href="tel:2706393383" value="+12706393383" target="_blank">2706393383</a> s:12 o:1920 ts:2160]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.728662 [INFO] mpf_rtp_stream.c:1279 Send Compound RTCP Packet [BYE] [72 bytes] <a href="http://10.3.5.80:4017" target="_blank">10.3.5.80:4017</a> -> <a href="http://10.3.15.180:7971" target="_blank">10.3.15.180:7971</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [INFO] mrcp_client_connection.c:525 Receive MRCPv2 Stream <a href="http://10.3.5.80:40061" target="_blank">10.3.5.80:40061</a> <-> <a href="http://10.3.15.180:6075" target="_blank">10.3.15.180:6075</a> [69 bytes]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">MRCP/2.0 69 2 200 IN-PROGRESS<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">Channel-Identifier: 40@speechrecog<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] mrcp_stream.c:382 Parsed MRCP Message [69]<u></u><u></u></span></p><p class="MsoNormal">
<span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] mrcp_client.c:1104 Signal Connection Task Message<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] mrcp_client.c:974 Receive Connection Task Message [3]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [INFO] mrcp_client_session.c:504 Raise App MRCP Response 0xb7191d88 <40><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] mod_unimrcp.c:3094 (ASR-8) RECOGNIZE IN PROGRESS<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] mod_unimrcp.c:1488 (ASR-8) READY ==> PROCESSING<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] apt_consumer_task.c:90 Wait for Task Messages [MRCP Client]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.752156 [DEBUG] switch_core_media_bug.c:360 Attaching BUG to <a href="mailto:sofia/internal/1000@10.3.5.80" target="_blank">sofia/internal/1000@10.3.5.80</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:12.756369 [DEBUG] switch_ivr_play_say.c:1236 Codec Activated L16@8000hz 1 channels 20ms<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:13.388227 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [1000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:13.388227 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [2000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:14.388378 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [2000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:14.388378 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [3000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:14.976914 [DEBUG] switch_ivr_play_say.c:1573 done playing file<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:15.387961 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [3000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:15.387961 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [4000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:16.388597 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [4000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:16.388597 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [5000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:17.387667 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192310 [5000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:17.387667 [INFO] mpf_rtp_stream.c:1092 Generate RTCP SR [ssrc:<a href="tel:2706393383" value="+12706393383" target="_blank">2706393383</a> s:244 o:39040 ts:39440]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:17.387667 [INFO] mpf_rtp_stream.c:1230 Send Compound RTCP Packet [48 bytes] <a href="http://10.3.5.80:4017" target="_blank">10.3.5.80:4017</a> -> <a href="http://10.3.15.180:7971" target="_blank">10.3.15.180:7971</a><u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:17.387667 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192310 [10000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:17.387667 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [5000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:17.387667 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [6000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:18.388818 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [6000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:18.388818 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [7000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:19.387895 [DEBUG] mpf_timer_manager.c:180 Timer Elapsed 0xb7192328 [7000]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:19.387895 [DEBUG] mpf_timer_manager.c:111 Set Timer 0xb7192328 [8000]<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">2011-09-12 10:30:19.906918 [INFO] mrcp_client_connection.c:525 Receive MRCPv2 Stream <a href="http://10.3.5.80:40061" target="_blank">10.3.5.80:40061</a> <-> <a href="http://10.3.15.180:6075" target="_blank">10.3.15.180:6075</a> [140 bytes]<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-AU">MRCP/2.0 140 RECOGNITION-COMPLETE 2 COMPLETE<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">Channel-Identifier: 40@speechrecog<u></u><u></u></span></p><p class="MsoNormal">
<span lang="EN-AU">Waveform-URI:<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">Completion-Cause: 002 no-input-timeout<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-AU">--------------------------------------------------------------------------------------------------------------------------------<u></u><u></u></span></p>
</div></div></div></div><br><br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<br></blockquote></div><br>