Label |
Id |
Description |
appl_begin |
130 |
Application Begin
Logged when the VoiceXML application
begins.
The format is: appl_begin
[<name>=<value>[|<name>=<value>...]]
<name> |
The name of the parameter. This
name is either the name of a Call Manager variable that is sent to
the Interpreter when a session is created, INIT_URL (The initial
URL), or DEFAULTS (the default page that is
used). |
<value> |
The value of the
parameter. |
Constant: VGLOG_APPL_BEGIN
Example: appl_begin
INIT_URL=http://www.genesyslab.com/test.vxml|DEFAULTS=defaults.vxml|ANI=1234|DNIS=1234
|
appl_end |
36 |
Application End
Logged when the VoiceXML application comes to an end and
the session terminates.
Constant: VGLOG_APP_END
Example: appl_end
|
asr_close |
149 |
ASR Close
Logged on ASR close
The format is: asr_close
<session_id>
<session_id> |
The MRCP Session
ID. |
Constant: VGLOG_ASR_CLOSE
Example: asr_close
MRCP-ID
|
asr_open |
148 |
ASR Open
Logged on ASR open result
The format is: asr_open
<session_id>|<result_text>
<session_id> |
The MRCP Session
ID. |
<result_text> |
Human readable result. It can be one of:
|
Constant: VGLOG_ASR_OPEN
Example: asr_open
MRCP-ID|success
|
asr_trace |
26 |
ASR Trace
Gives information on ASR events.
The format is: asr_trace
<event>:<result>
<event> |
This specifies what recognition event has occured:
bargein |
Currently playing prompts were barged-in with
speech. |
ASR_DONE |
User utterance was successfully recognized. |
ASR_NOMATCH_WITH_NBEST |
N-best results were enabled but none of the results were
of sufficient confidence or there was an ambiguous
match. | |
<result> |
This gives
futher information depending on the event. For bargein, it's
always "_bargein_". For "ASR_DONE" and "ASR_NOMATCH_WITH_NBEST", it
will be the raw recognition results.
|
Notes: This metrics entry is
also logged by the CMGR and SRM. See the SRM System Reference for the
details.
Constant: VGLOG_ASR_TRACE
Examples: asr_trace
bargein:_bargein_ asr_trace
ASR_DONE:results:+<_gram1>Vancouver|98|<Vancouver> asr_trace
ASR_NOMATCH_WITH_NBEST:results:+<_gram1>cinq un|5|<cinq
un>
|
bridge_begin |
3 |
Bridge Call Begin
This marks the beginning of a 'bridged' call (resulting
from use of the transfer tag), recorded when the outbound call has been
connected. The data includes dialed number, ANI, UUI, and the owner
session (who initiated the call).
The format is: bridge_begin
<ANI>|<DNIS>|<parent>|<UU>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<parent> |
Call ID of the parent inbound
call. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
Constant: VGLOG_BRIDGE_BEGIN
Example: bridge_begin
4167366493|tel:4167366779;postd=970408|00020023-0C001B58|N/A
|
bridge_end |
4 |
Bridge Call End
This record marks the end of a bridged
call.
The format is: bridge_end
<reason>
<reason> |
Disconnection reason. It can be one of:
usrend |
Session ended because of user hangup |
aplend |
Session ended because of application hangup, including
<transfer> maxtime expires. |
syserr |
Session ended because of system error |
lmtexc |
Session ended because <transfer> maxtime
expires | |
Constant: VGLOG_BRIDGE_END
Example: bridge_end
usrend
|
bridge_initiated |
53 |
Bridge Call Initiated
This marks the initiation of a 'bridged' call (resulting
from use of the transfer tag).
The format is: bridge_initiated
<board ID>:<channel ID>
<board ID> |
PSTN board number where
incoming call is placed. For VoIP, it is always
zero. |
<channel ID> |
PSTN channel number where
incoming call is placed. For VoIP, it is always
zero. |
Constant: VGLOG_BRIDGE_INITIATED
Example: bridge_initiated
101:6
|
bridge_reject |
5 |
Bridge Call Rejected
This record is used to indicate that two-leg transfer was
initiated but rejected for some reason.
The format is: bridge_reject
<ANI>|<DNIS>|<parent>|<UU>|<reason>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<parent> |
Call ID of the parent inbound
call. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
<reason> |
Rejection reason. It can be one of:
badani |
Bad ANI |
baddest |
Call destination is invalid |
badie |
Bad IE element |
busy |
The called number is busy |
error |
Some error occurred |
fax |
The called number was to a fax machine (with call
analysis) |
glare |
Call glare (conflict with an inbound call) occurred |
hangup |
Associated inbound call hung up |
ineffectiveother |
SIT tone ineffectiveother was detected |
intercept |
SIT tone intercept was detected |
interrupt |
Call was interrupted by the user or platform |
networkbusy |
The network is busy |
noanswer |
Call was not answered or timed out |
noautho |
No authorization for the outbound call |
nocircuit |
SIT tone no circuit was detected |
nodialtone |
No dialtone was received (call analysis) |
noresource |
Minimum required resources are not available |
noringback |
No ringback error occurred (call analysis) |
operator |
Operator intercept happened (call analysis) |
reorder |
SIT tone reorder occurred |
unknown |
The attempt failed for an unknown reason |
unsupported |
The network replies unsupported for the request |
vacantcode |
SIT tone vacant code was detected |
unallocated |
SIT tone unallocated was detected |
notinservice |
SIT tone not in service was
detected | |
Constant: VGLOG_BRIDGE_REJECT
Example: bridge_reject
4167361234|tel:4167366465|00020023-0C00E41E|N/A|busy
|
call_appl |
12 |
Application Name
Logged whenever a <meta> tag with name
attribute set to "application" is encountered.
The format is: call_appl
<appl_name>
<appl_name> |
The arbitrary application
name as specified with the content attribute of the
<meta> tag. |
Constant: VGLOG_APP_NAME
Example: call_appl XML grammar
test
|
call_begin |
6 |
Call Begin
This marks an event that an outbound call initiated with a
<call> is connected.
The format is: call_begin
<ANI>|<DNIS>|<parent>|<UU>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<parent> |
Call ID of the parent inbound
call. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
Constant: VGLOG_CALL_BEGIN
Example: call_begin
4167379496|tel:4167379205|00020023-0C00E50B|N/A
|
call_end |
7 |
Call End
This record marks the end of an outbound call initiated by
<call> tag.
The format is: call_end
<reason>
<reason> |
Disconnection reason. It can be one of:
usrend |
Session ended because of user hangup |
aplend |
Session ended because of application hangup, including
<call> maxtime expires. |
syserr |
Session ended because of system error |
lmtexc |
Session ended because <transfer> maxtime
expires | |
Constant: VGLOG_CALL_END
Example: call_end
usrend
|
call_initiated |
54 |
Call Initiated
This marks the initiation of an outbound call by
<call> tag.
The format is: call_initiated
<board ID>:<channel ID>
<board ID> |
PSTN board number where
incoming call is placed. For VoIP, it is always
zero. |
<channel ID> |
PSTN channel number where
incoming call is placed. For VoIP, it is always
zero. |
Constant: VGLOG_CALL_INITIATED
Example: call_initiated
101:6
|
call_notes |
137 |
Call notes in VAR
Call notes logged in VAR
Constant: CALL_NOTES
Example: call_notes This is call
notes for this vxml application
|
call_reference |
56 |
Call Reference
This maps the association between SIP Call-ID,
GVP-SESSION-ID, GVP-Tenant-ID and IVRProfile Name
The format is: call_reference
<Network ID>
<Network ID> |
SIP Call-ID,
GVP-SESSION-ID,GVP-Tenant-ID, IVRProfile
Name |
Constant: VGLOG_CALL_REFERENCE
Examples: call_reference
NmRlODA5OWMwZWM2N2U0ZWQ0MzI4YmRlZmUzNTE4MGI.|F7966BC2-EA13-4829-7EB5-DF0BF04593D7|N/A|N/A call_reference
ZDc2ZDQ5ZjY0NTcxNDNiYzJiNjY3NGY4ZDAzMzcxMjQ.|21E26056-8F17-42F4-5A9A-4A47EB4F0D3C|tenant_B|IVRProfile_Y
|
call_reject |
8 |
Call Rejected
This record is used to indicate that outbound call was
initiated but rejected for some reason.
The format is: call_reject
<ANI>|<DNIS>|<parent>|<UU>|<reason>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<parent> |
Call ID of the parent inbound
call. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
<reason> |
Rejection reason. It can be one of:
aplend |
Session ended because of application hangup |
badani |
Bad ANI |
baddest |
Call destination is invalid |
badie |
Bad IE element |
busy |
The called number is busy |
error |
Some error occurred |
fax |
The called number was to a fax machine (with call
analysis) |
glare |
Call glare (conflict with an inbound call) occurred |
hangup |
Associated inbound call hung up |
ineffectiveother |
SIT tone ineffectiveother detected |
intercept |
SIT tone intercept detected |
interrupt |
Call was interrupted by the user or platform |
networkbusy |
The network is busy |
noanswer |
Call was not answered or timed out |
noautho |
No authorization for the outbound call |
nocircuit |
SIT tone no circuit detected |
nodialtone |
No dialtone was received (call analysis) |
noresource |
Minimum required resources are not available |
noringback |
No ringback error occurred (call analysis) |
operator |
Operator intercept happened (call analysis) |
reorder |
SIT tone reorder occurred |
unknown |
The attempt failed for an unknown reason |
unsupported |
The network replies unsupported for the request |
vacantcode |
SIT tone vacant code
detected | |
Constant: VGLOG_CALL_REJECT
Example: call_reject
4167361234|tel:4167366465|00020023-0C00E3DE|N/A|busy
|
call_result |
136 |
Call result in VAR
Call result logged in VAR
Constant: CALL_RESULT
Example: call_result SUCCESS|Call
result reason for the successful call
|
choice_select |
77 |
Choice Select
When a <choice> in a <menu> is selected, the
choice phrase and the choice action are logged. The choice action can be a
target URL (and possibly an anchor specifying a dialog on that page) of a
page that is being transitioned to or an event that is being
thrown.
The format is: choice_select
:[<DTMF_digits>]|[<PCDATA>]
[next=<target_URL>][event=<event>]
<DTMF_digits> |
The DTMF sequence
associated with this choice. |
<PCDATA> |
The PCDATA of the selected
choice. |
<target_URL> |
The target URL (and possibly an anchor specifying a dialog on
that page) of a page that is being transitioned to. It has the
following format:
[<URL>][#<dialog_ID>]
Where:
<URL> |
The URL of the target page. |
<dialog_ID> |
The ID of a <form> or
<menu>. | |
<event> |
The event that is being
thrown. |
Constant: VGLOG_CHOICE_SELECT
Examples: choice_select :3|three
next=http://host.com/page.vxml#address_form choice_select :1|one
event=one_selected_event
|
compile_done |
41 |
Compile Done
The compilation of a fetched VoiceXML page is
complete.
The format is: compile_done
:<URL>
<URL> |
The absolute URL of the
page. |
Constant: VGLOG_COMPILE_DONE
Example: compile_done
:http://test.genesyslab.com/test.vxml
|
cpa_configuration |
145 |
CPA Configuration Parameters
Logged when CPA logging is enabled.
The format is: cpa_configuration
[<name>=<value>[|<name>=<value>...]]
<name> |
The name of the tuning
parameter. |
<value> |
The value of the
parameter. |
Constant: VGLOG_CPA_CONFIGURATION
Example: cpa_configuration
max_preconnect_time=30000|max_postconnect_time=20000|max_beep_det_time=30000|no_limit_timeout=30000|chunks_not_flush_on_state_chg=90000|machine_greet_dur=1800|voice_pause_dur=1000|max_voice_signal_dur=800|fax_duration=160|voice_range_db=25|voice_level_db=17.5|max_ring_cnt=9|sil_before_beep=4500|preconnect_tone_det_mode=0|notime_ringback_match_percent=50|ontime_preconnect_match_percent=60
|
cpa_result |
147 |
CPA Result
Logged when CPA result returns
The format is: cpa_result
[<value>]
<value> |
CPA result. It can be one of:
Human |
Human voice detected |
Answering Machine |
Answering machine detected |
No Media |
Timeout occurred after call connected |
Answering Machine Beep |
Answering machine beep detected |
Answering Beep Long Silence |
Answering beep due to long silence |
No Beep Long Answering Machine |
No beep found due to long answering machine |
Fax |
Fax detected |
No Answer Max Ring |
Maximum rings occurred before call was answered |
No Answer Timeout |
Timeout occurred before call was answered |
Busy |
Busy tone detected |
Fast Busy |
Fast busy tone detected |
SIT No Circuit |
SIT special information tone no circuit |
SIT Vacant Circuit |
SIT special information tone vacant circuit |
SIT Operator Intercept |
SIT special information tone operator intercept |
SIT Reorder |
SIT special information tone recorder |
Custom1 |
Custom tone 1 detected |
Custom2 |
Custom tone 2 detected |
Custom3 |
Custom tone 3 detected |
Custom4 |
Custom tone 4 detected |
No Answer Buffer Limit |
Out of buffer during preconnect |
No Media Buffer Limit |
Out of buffer during postconnect |
Beep Detect Buffer Limit |
Out of buffer during beep detect |
Timeout |
Final result not determined within max time |
Stopped |
Stop called before final result reached |
Unknown |
Reported unknown
result | |
Constant: VGLOG_CPA_RESULT
Example: cpa_result Answering
Machine
|
cpa_tone_setting |
146 |
CPA Tone Setting
Logged when CPA is enabled.
The format is: cpa_tone_setting
[<tone_name>=<tone_value>[|segment=<>[,<name>=<value>...]...]]
<tone_name> |
The tone
name. |
<tone_value> |
The tone
description. |
<seg_value> |
The segment
value. |
<name> |
The name of the
parameter. |
<value> |
The value of the
parameter. |
Constant: VGLOG_CPA_TONE_SETTING
Example: cpa_tone_setting
ringbak=tone1|segment=1,f1min=0,f1max=0,f2min=0,f2max=0,ontimemin=20,ontimemax=20,offtimemin=0,offtimemax=0|segment=2,f1min=0,f1max=0,f2min=0,f2max=0,ontimemin=20,ontimemax=20,offtimemin=0,offtimemax=0|segment=3,f1min=0,f1max=0,f2min=0,f2max=0,ontimemin=20,ontimemax=20,offtimemin=0,offtimemax=0
|
custom_var |
141 |
Custom variables in VAR
Custom variables logged in VAR. Custom variables may be
specified at any point in a VoiceXML application. The reporting
infrastructure will allow a maximum of eight (8) custom variables to be
specified for a given call. Any variables logged beyond the maximum will
be ignored
Constant: CUSTOM_VAR
Example: custom_var FirstVar|one
|
dtmf |
27 |
DTMF Input
DTMF input was received.
The format is: dtmf
:<digits>
<digit> |
The sequence of DTMF digits
received. |
Constant: VGLOG_DTMF
Example: dtmf :9
|
dtmf_end |
128 |
DTMF End
The end of a DTMF signal has occurred
Constant: VGLOG_DTMF_END
Example: dtmf_end
|
eval_cond |
44 |
Condition Evaluated
The result of the evaluation of a
condition.
The format is: eval_cond
:{<condition>}=<result>
<condition> |
A Boolean ECMAScript
expression. |
<result> |
The evaluated result of the
expression ("true" or
"false"). |
Constant: VGLOG_EVAL_COND
Example: eval_cond :{reenter ==
true}=true
|
eval_expr |
47 |
Expression Attribute Evaluated
An ECMAScript expression specified in an element attribute
was evaluated.
The format is: eval_expr
<<element>>:<attr>={<expression>}=<value>
<element> |
The element that has the
attribute. This can be any element that has any attribute that is an
expression. Examples are: "FIELD", "AUDIO",
"GRAMMAR". |
<attribute> |
The attribute being
evaluated. |
<expression> |
The expression that is
specified with the attribute. |
<value> |
The evaluation result of the
expression. |
Constant: VGLOG_EVAL_EXPR
Example: eval_expr
<SCRIPT>:expr={'utils' + version + '.js'}=utils2.js
|
eval_script |
45 |
Script Executed
A <script> element was executed.
The format is: eval_script
<location>:[<size>][<src>]
[<outcome>]
<location> |
Where the script resides. This can be one of:
inline |
An inline script. |
external |
An external script specified by the src
attribute. | |
<size> |
The size in characters of the
inline script. |
<src> |
The src attribute of the
<script> element. Note that this does not have to be the
absolute URL. |
<outcome> |
Whether the execution of the script was successful or not.
done |
The script was executed without problems. |
error |
An error was encountered while executing the
script. | |
Constant: VGLOG_EVAL_SCRIPT
Examples: eval_script inline:21
done eval_script external:domutil.js done eval_script inline:142
error
|
eval_var |
46 |
Variable Declaration
A variable has been declared or assigned to using the
<var> or <assign> element.
The format is: eval_var
:<variable>[={<expression>}]=<value>
<variable> |
The name of the
variable. |
<expression> |
The expression that is
specified in the expr attribute. |
<value> |
The final value assigned to the
variable. The evaluation result of the expression if an expression
has been specified, or "undefined" if the variable has just been
declared without an expr
attribute. |
Constant: VGLOG_EVAL_VAR
Examples: eval_var :globalvar={41 +
1}=42 eval_var :justdeclared=undefined
|
event |
34 |
Event Thrown
An event has been thrown.
The format is: event
<event_name>:<count>|[<message>]
<event_name> |
The event that has been
thrown. |
<count> |
The event count associated with
this event. |
<message> |
The message associated with
this event. |
Constant: VGLOG_EVENT
Examples: event
connection.disconnect.hangup:1|Call hang up during FileWaiter event
myevent:2|
|
event_handler_enter |
80 |
Event Handler Enter
An event was caught by an event handler.
The format is: event_handler_enter
<event_name>|<location>
<event_name> |
The event attribute
of the <catch> element or the tag name of a <nomatch>,
<noinput>, <error> or <help> element. This may or
may not be the same as the name of the actual event that is
caught. |
<location> |
Points to the location in the document where the event handler
resides. It has the following format:
[<URL>][#<dialog_ID>[.<form_item_name>]]
Where:
<URL> |
The URL of the page. This may include a query
string. |
<dialog_ID> |
The ID of the <form> or <menu>. |
<form_item_name> |
The name of the form
item. | |
Constant: VGLOG_EVENT_ENTER
Examples: event_handler_enter
:NOINPUT|http://host.com/root.vxml event_handler_enter
:myevent|http://host.com/page.vxml#dialog2.field3
|
event_handler_exit |
81 |
Event Handler Exit
Whenever the execution of an event handler is complete,
this entry is logged. This means that the closing </catch>,
</noinput>, etc. tag was reached and the event handler was not left
because of a <goto>, <submit>, <throw>, <return>,
<exit>, <disconnect> or an event.
The format is: event_handler_exit
<event_name>
<event_name> |
The event attribute
of the <catch> element or the tag name of a <nomatch>,
<noinput>, <error> or <help>
element. |
Constant: VGLOG_EVENT_EXIT
Example: event_handler_exit
:error.connection
|
exec_error |
39 |
Execution Error
A fatal problem was encountered during the execution of a
page. Note that a blank line may follow this metric.
The format is: exec_error
[(<URL>,[<application>])]:<desc>
<URL> |
The absolute URL of the
page. |
<application> |
The application name
specified by this page. |
<desc> |
Description of the
problem. |
Constant: VGLOG_EXEC_ERROR
Example: exec_error
(http://host.com/non-vxml.xml,):No <vxml> in VXML page
|
exec_warning |
40 |
Execution Warning
A non-fatal problem was encountered during the execution
of a page.
The format is: exec_warning
(<URL>,[<application>]):<desc>
<URL> |
The absolute URL of the
page. |
<application> |
The application name
specified by this page. |
<desc> |
Description of the
problem. |
Constant: VGLOG_EXEC_WARNING
Example: exec_warning
(http://host.com/clear.vxml,):Variable "x" listed in <clear>'s
attribute "namelist" is not defined
|
fetch_end |
43 |
Resource Fetch Response
Fetch response for a resource (audio, external grammar,
external script, XML data). Note that fetch_end is not logged for
built-in audio files.
The format is: fetch_end
<outcome>
([<origin>][<failure_reason>]):<URL>
<outcome> |
The outcome of the fetch. This can be one of:
Done |
Fetch success. |
Fail |
Fetch
failure. | |
<origin> |
For a successful fetch, the origin of the response. It can be one
of the following:
memory |
The file was served from the cache of the Fetching
Module. |
proxy-hit |
The file was served from the HTTP proxy (Squid). |
proxy-miss |
Means that the HTTP proxy didn't have a fresh enough copy
and the file was fetched from the Web server by the HTTP
proxy. |
revalidated |
The file was cached in Fetching Module, after revalidating
it with the Web server. |
proxy-revalidated |
The file was cached in Fetching Module, after revalidating
it with the HTTP proxy (Squid). |
direct |
Indicates a direct fetch from an Web server when the
platform is configured to bypass the HTTP proxy. |
file |
The file is a local file
(file://...). | |
<failure_reason> |
For a failed fetch, the
reason of failure. This may be "timeout", "connect timeout" for
https timeout, or "HTTP error response xxx" where xxx specifies an
HTTP status code. |
<URL> |
The absolute URL of the fetch
request. |
Constant: VGLOG_FETCH_RESPONSE
Examples: fetch_end Done
(proxy-miss):http://host.com/common/grammar/agent.xml fetch_end Done
(file):file:///usr/local/samples/hello.vox fetch_end Fail
(timeout):http://mars.com/stream.cgi fetch_end Fail (HTTP error
response 404):http://host.com/doesnotexist.wav
|
fetch_start |
42 |
Resource Fetch Request
Fetch request for a resource (audio, external grammar,
external script, XML data). Note that fetch_start is not logged for
built-in audio files.
The format is: fetch_start
<fetch type>:<URL>
<fetch type> |
The resource type of the
file to fetch. It can be one of grammar, audio,
script, or data. |
<URL> |
The absolute URL of the page
that's being fetched. |
Constant: VGLOG_FETCH_REQUEST
Example: fetch_start
data:http://www.example.com/rss/newsfeed.xml
|
filled_enter |
32 |
Filled Entered
A <filled> handler has been
entered.
The format is: filled_enter
<mode>[:<form items>]
<mode> |
The mode attribute of the
<filled>. This can be ALL or
ANY. |
<form items> |
The list of form items that
this <filled> has been triggered
for. |
Constant: VGLOG_FILLED_ENTER
Example: filled_enter
ALL:pword
|
filled_exit |
127 |
Filled Exit
This entry is logged when the execution of a
<filled> element is complete. This means that the closing
</filled> tag was reached and the <filled> was not left
because of a <goto>, <submit>, <throw>, <return>,
<exit>, <disconnect> or an event.
Constant: VGLOG_FILLED_EXIT
Example: filled_exit
|
filling |
76 |
Filling Form Item
Logged when a form item gets filled.
The format is: filling
:[<Dialog Id>].<Form Item Name>:<Form Item
Type>:<Value>
<Dialog Id> |
The id attribute of the menu
or form, if specified. |
<Form Item Name> |
The name of the form
item. |
<Form Item Type> |
The type (tag name) of
the form item that is being filled. This can be one of FIELD,
TRANSFER, RECORD, SUBDIALOG or
OBJECT. |
<Value> |
The value that is used to fill
the form item. |
Constant: VGLOG_FILLING
Example: filling
:.field1:FIELD:yes
|
form_enter |
28 |
Form Entered
Logged when a <form> has been
entered.
The format is: form_enter
[:<ID>]
<ID> |
The ID of the form, if
specified. |
Constant: VGLOG_FORM_ENTER
Examples: form_enter form_enter
:Welcome
|
form_exit |
30 |
Form Exited
The current form has been left either because the FIA
cannot find any other items to visit or there has been an internal
error.
The format is: form_exit
<reason>[:<error>]
<reason> |
How the form has been left. This can be:
normal |
The FIA can't find a form item to visit and the form is
left for "natural reasons". |
internal_error |
There has been an internal
error. | |
<error> |
The description of the error
when reason is
internal_error. |
Constant: VGLOG_FORM_EXIT
Example: form_exit
normal
|
form_select |
29 |
Form Item Selected
The FIA has selected a form item to
visit.
The format is: form_select
:<item_name>:<item_type>
<item_name> |
The name of the form item.
This is an internally generated name if a name hasn't been specified
for the item. |
<item_type> |
The type of the form item.
This can be one of FIELD, TRANSFER, RECORD,
SUBDIALOG, OBJECT, BLOCK, or
INITIAL. |
Constant: VGLOG_FORM_SELECT
Examples: form_select
:pword:FIELD form_select :_tempBlock1:BLOCK
|
goto |
33 |
Goto Executed
Transition to another page, dialog or form
item.
The format is: goto
:[<target_URL>][#<dialog_ID>[.<form_item_name>]]
<target_URL> |
The absolute URL of the
page being transitioned to. |
<dialog_ID> |
The dialog on the current
page or the target page. |
<form_item_name> |
The form item on the
current dialog. |
Constant: VGLOG_GOTO
Examples: goto :#exit goto
:http://diamond/next.vxml goto :#address_form.city
|
incall_begin |
0 |
Inbound Call Begin
This marks the beginning of an inbound
call.
The format is: incall_begin
<DNIS>|<ANI>|<TRAN>|<II>|<UU>|<RDNIS>
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<TRAN> |
The transaction identifier. The format of the
transaction identifier is:
<yyyy><mm><dd><tttttt><seqno>
Where:
<yyyy> |
4 digit year e.g. 2005 |
<mm> |
2 digit month. e.g. 08 |
<dd> |
2 digit day e.g. 20 |
<tttttt> |
6 digit value of time in seconds since 00:00:00 UTC,
January 1, 1970, modulo 1000000 |
<seqno> |
3-digit number generated for each user session;
incremented for each new call, modulo
1000 | |
<II> |
The ISDN Information Digits for the
call. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
<RDNIS> |
Redirected Dialed Number
Identification Service; The number dialed by the user before being
re-directed. |
Constant: VGLOG_INCALL_BEGIN
Example: incall_begin
sip:2222@diamond:5060|sip:1234@pearl:5060|20050310488528015|N/A|foo|N/A
|
incall_end |
1 |
Inbound Call End
This record marks the end of an inbound session. The
record specific data indicates the reason for the call
end.
The format is: incall_end
<reason>
<reason> |
Disconnection reason. It can be one of:
usrend |
Session ended because of user hangup |
aplend |
Session ended because of application hangup |
syserr |
Session ended because of system
error | |
Constant: VGLOG_INCALL_END
Example: incall_end
usrend
|
incall_initiated |
52 |
Inbound Call Initiated
This marks the offering of an inbound call by the
network.
The format is: incall_initiated
<board ID>:<channel ID>
<board ID> |
PSTN board number where
incoming call is placed. For VoIP, it is always
zero. |
<channel ID> |
PSTN channel number where
incoming call is placed. For VoIP, it is always
zero. |
Constant: VGLOG_INCALL_INITIATED
Example: incall_initiated
101:23
|
incall_reject |
2 |
Inbound Call Rejected
This record is used to indicate that an inbound call has
been presented to the platform, but has been rejected for some
reason.
The format is: incall_reject
<DNIS>|<ANI>|<TRAN>|<II>|<UU>|<RDNIS>|<reason>
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<TRAN> |
The transaction identifier. The
format is the same as in incall_begin. |
<II> |
The ISDN Information Digits for the
call. |
<UU> |
The User-to-User information passed
with the call. |
<RDNIS> |
Redirected Dialed Number
Identification Service; The number dialed by the user before being
re-directed. |
<reason> |
Rejection reason. It can be one of:
badfetch |
the page could not be fetched |
decline |
the call is declined based on the page (meta tag) |
error |
some error occurred |
hangup |
Associated inbound call hung up |
noresource |
a resource, such as TTS, ASR or requested Application
Module, is not available |
unknown |
the attempt failed for an unknown reason |
timeout |
the incoming call is accepted, however the network fails
to acknowledge or complete the connection within 10
seconds |
|
Constant: VGLOG_INCALL_REJECT
Example: incall_reject
sip:4167366779@205.150.90.154;user=phone|sip:205.150.90.78|20060621901817666|N/A|N/A|N/A|timeout
|
input_end |
25 |
Input End
Recognition has ended.
The format is: input_end
[<reason>]|[<mode>]|[<grammar_scope>]|[<grammar_url>]|[<phrase>]|[<confidence>]
<reason> |
Can be one of the following:
DISCONNECTED, FAILED, NO_INPUT, ERROR, NO_MATCH, MAX_SPEECH_TIMEOUT,
ASR_MAXSPEECHTIMEOUT, RECORD_END, or TRANSFER
END. |
<mode> |
The input mode. Can be voice or
dtmf. |
<grammar_scope> |
The scope of the
grammar. Can be inline or external. |
<grammar_url> |
The URL of the
grammar. |
<phrase> |
The interpretation of the
input. If no interpretation is present, the value will be the DTMF
sequence for DTMF input or the utterance for speech
recognition. |
<confidence> |
The confidence level of the
input. |
Constant: VGLOG_INPUT_END
Examples: input_end
MATCHED|dtmf|Field|inline|2|1.000000 input_end
DISCONNECTED|||||
|
input_start |
24 |
Input Begin
Marks the start of a recognition
session.
The format is: input_start
[:<modes>]
<modes> |
The list of input modes active for this recognition session,
delimited by the "|" (pipe) character. These can
be:
DTMF |
DTMF recognition. |
VOICE |
Speech recognition. |
TDD |
TDD/TTY
input. | |
Constant: VGLOG_INPUT_BEGIN
Example: input_start
:VOICE|DTMF
|
ivr_action_end |
139 |
IVR action end in VAR
IVR action end logged in VAR
Constant: IVR_ACTION_END
Example: ivr_action_end
FirstIVR|SUCCESS|FirstIVREnded
|
ivr_action_notes |
140 |
IVR action notes in VAR
IVR action notes logged in VAR. VoiceXML action notes may
be logged during the specified action or after it has ended.
Constant: IVR_ACTION_NOTES
Example: ivr_action_notes
actionwithnotes|ivractionnoteshasbeenadded
|
ivr_action_start |
138 |
IVR action start in VAR
IVR action start logged in VAR
Constant: IVR_ACTION_START
Example: ivr_action_start
FirstIVR|parentID=SecondIVR
|
link_triggered |
129 |
Link Triggered
Logged when a link is triggered in the VoiceXML
application.
The format is: link_triggered
<type>=<URL or event>
<type> |
The type of action taken by the link. It can be one of:
event |
An event will be thrown |
next |
The link will goto a
URL | |
<URL or event> |
The URL that the link is
going to or the name of the event thrown due to triggering the
link. |
Constant: VGLOG_LINK_TRIGGERED
Examples: link_triggered
next=#form2 link_triggered event=myevent
|
log |
35 |
Log Executed
<log> element data.
The format is: log
<data>
<data> |
The contents of the <log>
element. |
Constant: VGLOG_LOG
Example: log Hello
World!
|
menu_enter |
31 |
Menu Entered
A <menu> has been entered.
The format is: menu_enter
[<ID>]
<ID> |
The ID of the menu, if
specified. |
Constant: VGLOG_MENU_ENTER
Example: menu_enter
|
menu_exit |
135 |
Menu Exited
A <menu> has exited.
The format is: menu_exit
<reason>
<reason> |
Specifies the reason that the
menu exits. |
Constant: VGLOG_MENU_EXIT
Example: menu_exit
transition
|
mrcp_trace |
132 |
MRCP Trace
The RTSP/MRCP session ID and the MRCP server
information
The format is: mrcp_trace
<event>: <session id> IP: <MRCP server
IP> Vendor: <vendor name>
<event> |
This specifies the MRCP session:
RTSPSESSION |
A RTSP Session is established. |
ChannelID |
A SIP Session is
established. | |
<session id> |
It is an string
representing a RTSP session |
<MRCP server IP> |
This is the
MRCP server IP address and port number information.
|
<vendor name> |
The MRCP server
vendor. |
Constant: VGLOG_MRCP_TRACE
Examples: mrcp_trace RTSPSESSION:
d75a96cd_0000054c_44e20460_0dd6_0000 IP: 205.150.90.215:554 Vendor:
NUANCE mrcp_trace ChannelID: 78136@speechrecog IP: 10.0.0.120:6075
Vendor: NUANCE
|
outcall_begin |
9 |
Outbound Call Begin
This marks an event that an outbound call initiated with
remote dial client is connected.
The format is: outcall_begin
<ANI>|<DNIS>|<TRAN>|<UU>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<TRAN> |
The transaction identifier. The format of the transaction
identifier is:
<yyyy><mm><dd><tttttt><seqno>
Where:
<yyyy> |
4 digit year e.g. 2005 |
<mm> |
2 digit month. e.g. 08 |
<dd> |
2 digit day e.g. 20 |
<tttttt> |
6 digit value of time in seconds since 00:00:00 UTC,
January 1, 1970, modulo 1000000 |
<seqno> |
3-digit number generated for each user session;
incremented for each new call, modulo
1000 | |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
Constant: VGLOG_OUTCALL_BEGIN
Example: outcall_begin
sip:gvp@pearl|sip:dialog.vxml.http%3A//host/helloworld.vxml@diamond|20050316986819816|N/A
|
outcall_end |
10 |
Outbound Call End
This record marks the end of an outbound call initiated by
remote dial client.
The format is: outcall_end
<reason>
<reason> |
Disconnection reason. It can be one of:
usrend |
Session ended because of user hangup |
aplend |
Session ended because of application hangup |
syserr |
Session ended because of system error |
lmtexc |
Session ended because <transfer> maxtime
expires | |
Constant: VGLOG_OUTCALL_END
Example: outcall_end
usrend
|
outcall_initiated |
55 |
Outbound Call Initiated
This marks the initiation of an outbound call by remote
dial client. In particular, a channel is selected and the outbound
calling request is sent to the network.
The format is: outcall_initiated
<board ID>:<channel ID>
<board ID> |
PSTN board number where
incoming call is placed. For VoIP, it is always
zero. |
<channel ID> |
PSTN channel number where
incoming call is placed. For VoIP, it is always
zero. |
Constant: VGLOG_OUTCALL_INITIATED
Example: outcall_initiated
101:6
|
outcall_reject |
11 |
Outbound Call Rejected
This record is used to indicate that outbound call was
initiated but rejected for some reason.
The format is: outcall_reject
<DNIS>|<ANI>|<TRAN>|<II>|<UU>|<RDNIS>|<reason>
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<TRAN> |
The transaction identifier. The
format is the same as in incall_begin. |
<II> |
The ISDN Information Digits for the
call. |
<UU> |
The User-to-User information passed
with the call. |
<RDNIS> |
Redirected Dialed Number
Identification Service; The number dialed by the user before being
re-directed. |
<reason> |
Rejection reason. It can be one of:
badani |
Bad ANI |
baddest |
Call destination is invalid |
badfetch |
the page could not be fetched |
badie |
Bad IE element |
busy |
The called number is busy |
decline |
the call is declined based on the page (meta tag) |
error |
Some error occurred |
fax |
The called number was to a fax machine (with call
analysis) |
glare |
Call glare (conflict with an inbound call) occurred |
hangup |
Associated inbound call hung up |
ineffectiveother |
SIT tone ineffectiveother detected |
intercept |
SIT tone intercept detected |
interrupt |
Call was interrupted by the user or platform |
machine |
Called number was to an answering machine (call
analysis) |
networkbusy |
The network is busy |
noanswer |
Call was not answered or timed out |
noautho |
No authorization for the outbound call |
nocircuit |
SIT tone no circuit detected |
nodialtone |
No dialtone was received (call analysis) |
noresource |
Minimum required resources are not available |
noringback |
No ringback error occurred (call analysis) |
operator |
Operator intercept happened (call analysis) |
reorder |
SIT tone reorder occurred |
unknown |
The attempt failed for an unknown reason |
unsupported |
The network replies unsupported for the request |
vacantcode |
SIT tone vacant code
detected | |
Constant: VGLOG_OUTCALL_REJECT
Example: outcall_reject
sip:gvp@pearl|sip:dialog.vxml.http%3A//host/helloworld.vxml@diamond|20050316956139646|N/A|error
|
outcall_requested |
74 |
Outbound Call Requested
This marks the initiation of an outbound call by remote
dial client. The request is not sent to the network and the channel is
not selected yet when this entry is logged.
Constant: VGLOG_OUTCALL_REQUESTED
Example: outcall_requested
|
parse_error |
37 |
Parse Error
Parse error while compiling a VoiceXML
page.
The format is: parse_error
(<URL>,[<application>], line
[<line>]):<desc>
<URL> |
The absolute URL of the
page. |
<application> |
The application name
specified by this page. |
<line> |
The line number at which the
problem was encountered. |
<desc> |
Description of the
problem. |
Constant: VGLOG_PARSE_ERROR
Example: parse_error
(http://10.0.0.136/cc.vxml,transfer_to_agent,, line 33):Exactly one of
"aai"("uuidata") or "aaiexpr"("uuidataexpr") may be specified in
<transfer>
|
parse_warning |
38 |
Parse Warning
Parse warning while compiling a VoiceXML
page.
The format is: parse_warning
([<URL>],[<application>], line
<line>):<desc>
<URL> |
The absolute URL of the
page. |
<application> |
The application name
specified by this page. |
<line> |
The line number at which the
problem was encountered. |
<desc> |
Description of the
problem. |
Constant: VGLOG_PARSE_WARNING
Example: parse_warning
(http://tester/test.vxml,, line 6):unsupported element FIELD in
BLOCK
|
prompt |
18 |
Prompt Begin
Marks the beginning of prompt playback. There will be a
single entry even if a queue of multiple prompts is being
played.
Constant: VGLOG_PROMPT_BEGIN
Example: prompt
|
prompt_end |
19 |
Prompt End
Playback of prompts has ended.
The format is: prompt_end
<reason>
<reason> |
Specifies whether the prompt playback was completed or
interrupted. It can be one of:
done |
The prompts were played to completion. |
hangup |
The prompt playback was aborted due to hang up.. |
error |
The prompt playback was aborted due to an error. |
dtmfbargein |
The playback of prompts was interrupted by DTMF
barge-in. |
asrbargein |
The playback of prompts was interrupted by speech
barge-in. | |
Constant: VGLOG_PROMPT_END
Examples: prompt_end
done prompt_end dtmfbargein prompt_end asrbargein
|
prompt_play |
134 |
Prompt Play
Playback of a single element of the prompt queue. One or
more of these metrics occur between a prompt and prompt_end
metric.
The format is: prompt_play
<type>|<data>
<type> |
Specifies the type of audio being played. It can be one of:
mark |
A mark tag |
audio |
An audio tag |
break |
A break tag |
tts |
SSML |
beep |
A beep |
recording |
A
recording | |
<data> |
Details of the specific audio
item. This could be a url, an SSML snippet and so
on. |
Constant: VGLOG_PROMPT_PLAY
Examples: prompt_play
audio|http://127.0.0.1/audio/sample.ulaw prompt_play tts|<?xml
version="1.0" encoding="UTF-8"?><speak version="1.0"
xmlns="http://www.w3.org/2001/10/synthesis"
xml:lang="en-US">10.00.</speak>
|
record_end |
21 |
Record End
A recording has finished or has been
aborted.
The format is: record_end
:<outcome>[|<data>]
<outcome> |
The outcome of the record operation. Can be one of:
RECORD SUCCESS |
This indicates that there was audio input before record
termination and the <record> element is being
filled. |
NOINPUT |
This indicates that there was no audio input within the
timeout period. |
local grammar match |
dtmfterm was set to false and the recording was
terminated by a local grammar match with the length of the
recording being less than the mintime attribute. |
global grammar match |
dtmfterm was set to false and the recording was
terminated by a global grammar match. |
MINTIME |
This indicates that the recording was terminated and the
length of the recording was less than the mintime
attribute. |
INTERNAL_ERROR |
This indicates that when processing the end of a recording
an internal error
occured. | |
<data> |
This field provides additional data. The data presented depends
on the outcome of the record operation.
If the outcome of the record is RECORD SUCCESS, data is of the
form |<term
reason>|<duration>|<audio_format>|<filename>.
<term reason> |
This indicates the reason the recording was terminated.
Possible values are:
DTMF |
The recording was terminated by DTMF input while
dtmfterm was set to true. |
MAXTIME |
The recording was terminated because the audio input
duration exceeded maxtime. |
FINALSILENCE |
This means that the audio input was terminated by a
period of silence exceeding finalsilence. |
HANGUP |
This means that the audio input was terminated by
the user hanging up. |
MSG_INTERRUPT |
This means that the audio input was terminated due
to an asynchronous message which was handled
immediately. | |
<duration> |
This contains the duration (in seconds) of the
recording. |
<audio_format> |
This contains the MIME type of the audio format in which
the recording was made. |
<filename> |
This contains the local filename where the recording has
been saved. |
If the outcome of the record is NOINPUT, there may be data
present. If data is present, data is of the form
MINTIME|dtmf=<dtmf>.
<dtmf> |
This indicates which dtmf was pressed to terminate the
recording or it may be the letter "n" in the case where the
recording was terminated because it satisfied the finalsilence
condition and the length of the recording was less that the
mintime attribute. |
If the outcome of the record is MINTIME, data is of the form
|<reason>. Reason can be one of:
HANGUP |
This means that the audio input was terminated by the user
hanging up. |
MSG_INTERRUPT |
This means that the audio input was terminated due to an
asynchronous message which was handled
immediately. | |
Constant: VGLOG_RECORD_END
Examples: record_end :RECORD
SUCCESS|DTMF|4|audio/vox|/usr/local/tmp/file0001.vox record_end :RECORD
SUCCESS|MAXTIME|20|audio/wave|/usr/local/tmp/file0002.vox record_end
:NOINPUT record_end :global grammar match
|
record_start |
20 |
Record Begin
A <record> element has been executed and recording
has started.
The format is: record_start
:<filename>
<filename> |
The local filename where the
recording is going to be
saved. |
Constant: VGLOG_RECORD_BEGIN
Example: record_start
:/usr/local/phoneweb/tmp/00020023-101E744C-0001/...
|
root_appl |
79 |
Root Application
The VoiceXML document specifies a root
document.
The format is: root_appl
<URL>
<URL> |
The root application URL as
specified in the application attribute of the <vxml>
element. |
Constant: VGLOG_ROOT_NAME
Example: root_appl
http://darkstar.com/common/root.vxml
|
subdialog_return |
23 |
Subdialog End
Returning from a VoiceXML subdialog.
The format is: subdialog_return
:[<name>]|<return_type>
<name> |
The name of the
subdialog. |
<return_type> |
This field provides additional data. The data presented depends
on what is returned from the subdialog.
If the subdialog returns a namelist, return_type is of the form
namelist|[<param_name>;<param_value>;[<param_name>;<param_value>;...]]
<param_name> |
A parameter being returned from the subdialog
|
<param_value> |
The value of the parameter. |
If the subdialog returns an event, return_type is of the form
event|<event_name>
<event_name> |
The name of the returned
event. | |
Constant: VGLOG_SUBDIALOG_END
Example: subdialog_return
:GetPIN|namelist|status;OK;realname;Joe;
|
subdialog_start |
22 |
Subdialog Begin
Visiting a VoiceXML subdialog.
The format is: subdialog_start
:<name>:<URL>[#<fragment>]|param|[<param_name>;<param_value>;[<param_name>;<param_value>;...]]
<name> |
The name of the
subdialog. |
<URL> |
The URL of the
subdialog. |
<fragment> |
The fragment (dialog ID), if
specified. |
<param_name> |
A parameter being passed to
the subdialog. |
<param_value> |
The value of the
parameter. |
Constant: VGLOG_SUBDIALOG_BEGIN
Example: subdialog_start
:GetPIN:http://diamond/collectpin.vxml|param|user;joe;
|
submit |
78 |
Submit
When a <submit> is executed, the URL being
transitioned is logged along with submitted parameters, if
any.
The format is: submit
<target>|namelist|{[<name>:<value>,[<name>:<value>...]]}
<target> |
The URL, dialog and form item
being transitioned to. |
<name> |
The name of a variable that is
specified in the namelist
attribute. |
<value> |
The value of the
variable. |
Constant: VGLOG_SUBMIT
Examples: submit
http://host.com/page.cgi#entry|namelist|{"app":45,"page":3} submit
#dialog2|namelist|{}
|
transfer_connected |
73 |
Transfer Connected
This marks the establishment of transfer where the
transfer type with the system provides such information.
The format is: transfer_connected
<ANI>|<DNIS>|<parent>|<UU>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<parent> |
Call ID of the parent inbound
call. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
Constant: VGLOG_TRANSFER_CONNECTED
Example: transfer_connected
4167366493|tel:4167366779;postd=970408|00020023-0C001B58|N/A
|
transfer_end |
14 |
Transfer End
A transfer has ended with either success or
failure.
The format is: transfer_end
:<outcome>
<outcome> |
The outcome of the transfer. The possible values are:
network_busy |
Some intermediate network refused the call. |
error.connection.baddestination |
The destination was invalid. |
error.connection.noauthorization |
The caller was not authorized to transfer to the
destination. |
error.unsupported.uri |
The URI of the destination is not supported. |
error.unsupported.transfer. |
The type of the transfer is not supported for this
configuration. |
busy |
The endpoint refused the call. |
noanswer |
There was no answer within the time specified by the
connecttimeout attribute. |
rejected |
Only possible with multiphase transfers (i.e. when
consultexpr is set); this result occurs when the child script
exits without setting accepttransfer (or with it set to a
value other than true). |
unknown |
The outcome of the transfer is unknown. |
near_end_disconnect |
The call was completed and was terminated by the
caller. |
maxtime_disconnect |
The call duration exceeded the value of maxtime attribute
and was terminated by the platform. |
far_end_disconnect |
The call was completed and was terminated by the
callee. |
far_end_machine |
The remote end was deteced as an answer machine using call
progress analysis. |
far_end_fax |
The remote end was deteced as a fax machine using call
progress analysis. |
sit_unallocated |
The SIT tone unallocated was detected using call progress
analysis. |
sit_not_in_service |
The SIT tone not in service was detected using call
progress
analysis. | |
Constant: VGLOG_TRANSFER_END
Example: transfer_end
:noanswer
|
transfer_initiated |
72 |
Transfer Initiated
This marks the initiation of transfer.
The format is: transfer_initiated
<board ID>:<channel ID>
<board ID> |
PSTN board number where
incoming call is placed. For VoIP, it is always
zero. |
<channel ID> |
PSTN channel number where
incoming call is placed. For VoIP, it is always
zero. |
Notes: For redirect type of
transfer, <BOARD ID>:<CHANNEL ID> has the information of the
inbound, and for transfers involving outbound call this has the
information of the outbound.
Constant: VGLOG_TRANSFER_INITIATED
Example: transfer_initiated
0:0
|
transfer_result |
15 |
Transfer Result
This record is used to indicate that one-leg transfer has
completed.
The format is: transfer_result
<ANI>|<DNIS>|<UU>|<method>|<reason>
<ANI> |
Automatic Number Identification
(if so provisioned); The number from which the user is
calling. |
<DNIS> |
Dialed Number Identification
Service; The number dialed by the user. |
<UU> |
The User-to-User information passed
with the call. This is intended to be represented in IA5 format. Any
non-printable data is encoded with 'percent' encoding as defined in
RFC 2068. Non-printable data is presented as the hex-equivalent
preceded by a percent sign. It will be set to "N/A" if it's not
available. |
<method> |
Transfer method applied to the network. It can be one of:
bridge/BRIDGE |
Bridge transfer |
h450/H450 |
H.450-2 blind transfer |
h450join/H450JOIN |
H.450-2 consultative transfer |
hkf/HKF |
Hook flash |
inband/INBAND |
Inband DTMF transfer |
mediaredirect/MEDIAREDIRECT |
Media redirect transfer |
refer/REFER |
SIP refer transfer |
referjoin/REFERJOIN |
SIP refer transfer with replace
header | |
<reason> |
Transfer result. It can be one of:
aplend |
Transfer was ended by application. |
baddest |
Call destination is invalid |
badie |
Bad IE element |
busy |
The called number is busy |
done |
Call is successfully transferred |
error |
Some error occurred |
fax |
The called number was to a fax machine (with call
analysis) |
hangup |
Associated inbound call hung up |
ineffectiveother |
SIT tone ineffectiveother detected |
intercept |
SIT tone intercept detected |
interrupt |
Call was interrupted by the user or platform |
invalidtrigger |
Invalid trigger for the current call state |
lmtexc |
Outbound call has reached maximum call time |
machine |
Called number was to an answering machine (call
analysis) |
maxredirects |
Maximum redirects reached |
missingie |
Missing mandatory IE in ISDN transfer message |
networkbusy |
The network is busy |
noanswer |
Call was not answered or timed out |
noautho |
No authorization for the outbound call |
nocircuit |
SIT tone no circuit detected |
nodialtone |
No dialtone was received |
noringback |
No ringback error occurred |
operator |
Operator intercept happened (call analysis) |
reorder |
SIT tone reorder occurred |
resourcelimit |
Minimum required resources are not available |
timeout |
(For Q.Sig Transfer only) Call was disconnected when
network fails to respond withint the configurated time limit,
defined by the parameter dlgc.qsigfailontimeout |
unknown |
The attempt failed for an unknown reason |
unsupported |
The network replies unsupported for the request |
vacantcode |
SIT tone vacant code
detected | |
Constant: VGLOG_TRANSFER_RESULT
Example: transfer_result
sip:Username@205.150.90.136:5060|sip:XXXX@galahad|N/A|REFER|done
|
transfer_start |
13 |
Transfer Start
A transfer element has been executed.
The format is: transfer_start
:<dest>
<dest> |
The transfer
destination. |
Constant: VGLOG_TRANSFER_BEGIN
Example: transfer_start
:3333@wizard
|
tts_close |
151 |
TTS Close
Logged on TTS close
The format is: tts_close
<session_id>
<session_id> |
The MRCP Session
ID. |
Constant: VGLOG_TTS_CLOSE
Example: tts_close
MRCP-ID
|
tts_open |
150 |
TTS Open
Logged on TTS open result
The format is: tts_open
<session_id>|<result_text>
<session_id> |
The MRCP Session
ID. |
<result_text> |
Human readable result. It can be one of:
|
Constant: VGLOG_TTS_OPEN
Example: tts_open
MRCP-ID|success
|
wf_arrived |
17 |
Page Fetch Response
Fetch response for a VoiceXML page
The format is: wf_arrived
<outcome>
([<origin>][<failure_reason>]):<URL>
<outcome> |
The outcome of the fetch. This can be one of:
s |
Fetch success. |
f |
Fetch
failure. | |
<origin> |
For a successful fetch, the origin of the response. It can be one
of the following:
memory |
The file was served from the cache of the Fetching
Module. |
proxy-hit |
The file was served from the HTTP proxy (Squid). |
proxy-miss |
Means that the HTTP proxy didn't have a fresh enough copy
and the file was fetched from the Web server by the HTTP
proxy. |
revalidated |
The file was cached in Fetching Module, after revalidating
it with the Web server. |
proxy-revalidated |
The file was cached in Fetching Module, after revalidating
it with the HTTP proxy (Squid). |
direct |
Indicates a direct fetch from an Web server when the
platform is configured to bypass the HTTP proxy. |
file |
The file is a local file
(file://...). | |
<failure_reason> |
For a failed fetch, the
reason of failure. This may be "timeout", "connect timeout" for
https timeout, or "http-error-xxx" where xxx specifies an HTTP
status code. |
<URL> |
The absolute URL of the fetch
request. |
Constant: VGLOG_WF_RESPONSE
Examples: wf_arrived s
(proxy-miss):http://host.com/test.vxml wf_arrived s
(file):file:///usr/local/samples/hello.vxml wf_arrived f
(timeout):http://mars.com/slow.cgi wf_arrived f
(http-error-404):http://host.com/doesnotexist.vxml
|
wf_lookup |
16 |
Page Fetch Request
Fetch request for a VoiceXML page
The format is: wf_lookup
<URL>
<URL> |
The absolute URL of the page
that's being fetched. |
Constant: VGLOG_WF_REQUEST
Example: wf_lookup
http://grass.genesyslab.com/test.vxml
|