Author Message
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
Hi Team,

We were used EPM 7.0.2/OD 7.0.
Then we deployed new EPM 8.1.2/OD 8.1.2 with same flow on previous version.
As a results, voice browser hangs when executing certain call flows.

1. Run the application created by OD on EP
2. Execute some menu selection on the call flow
3. Phone goes silent and disconnects after menu selection

At first step of my investigation, we created a test flow using the grammar we used previous version.

The test flow has 4 Prompt&Collect, and each Prompt&Collect calls the provided grammar as follows.
"TestCustomGrammar" below is the OD flow name.

Prompt&Collect node:
1st: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_ContractS.grxml
2nd: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_Service2.grxml#main_rule
3rd: /TestCustomGrammar/data/Japanese/grammars/grammar_FcSelService__Dealings.grxml#main_rule
4th: /TestCustomGrammar/data/Japanese/grammars/grammar_RefDetail_KamokuInput.grxml#main_rule

Next, we tried to reproduce this issue with combination of EPM and OD version using sample flow with same grammar file.
As a results, we can say that this issue were occurred when we used EP8.1.

Case1: EP7.0 / OD7.0.1 - OK
Case2: EP8.1.2 / OD8.1.2 - NG
Case3: EP8.1.2 / OD7.0.1 - NG
Case4: EP7.0 / OD8.1.2 - OK

In NG case, 1st and 2nd Prompt&Collect node were working well. Then we confirmed same issue was occurred on 3rd Prompt&Collect node.
If we tried to add “#main_rule” id after 1st uri as below, we confirmed same issue was occurred on 1st Prompt&Collect node.

1st: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_ContractS.grxml#main_rule
2nd: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_Service2.grxml#main_rule
3rd: /TestCustomGrammar/data/Japanese/grammars/grammar_FcSelService__Dealings.grxml#main_rule
4th: /TestCustomGrammar/data/Japanese/grammars/grammar_RefDetail_KamokuInput.grxml#main_rule

Furthermore we confirmed all of Prompt&Collect node can be work without “#main_rule” id after uri as below.

1st: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_ContractS.grxml
2nd: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_Service2.grxml
3rd: /TestCustomGrammar/data/Japanese/grammars/grammar_FcSelService__Dealings.grxml
4th: /TestCustomGrammar/data/Japanese/grammars/grammar_RefDetail_KamokuInput.grxml

As a results, we can say that this issue was only occurred when we use “EP8.1.2” or “ #main_rule” after each uri on Avaya Japan lab.
Please advise whether the specification change or the supported node requirements change for the Voice Browser between EP/OD7.0 and EP/OD8.1.2 are there or not?

In our investigation, if grammar file has multiple rule id like below, if we add rule id after uri, Voice Browser didn't hung up.
-----
1st: /TestCustomGrammar/data/Japanese/grammars/grammar_Input_ContractS.grxml#main_rule

-- grammar_Input_ContractS.grxml --
<?xml version="1.0" encoding="UTF-8"?>
<grammar version="1.0" xml:lang="ja-JP" root="main_rule" mode="dtmf" tag-format="semantics/1.0" xmlns="http://www.w3.org/2001/06/grammar">

<rule id="main_rule" scope="public">
<item><ruleref uri="#main_sub_rule"/>#</item>
</rule>

<rule id="main_sub_rule" scope="public">
<one-of>
<item repeat="8"><ruleref uri="#number"/></item>
<item repeat="10"><ruleref uri="#number"/></item>
</one-of>
</rule>

<rule id="number" scope="public">
<one-of>
<item>0</item>
<item>1</item>
<item>2</item>
<item>3</item>
<item>4</item>
<item>5</item>
<item>6</item>
<item>7</item>
<item>8</item>
<item>9</item>
</one-of>
</rule>

</grammar>
-----

If grammar file has single "rule id" like below, if we add rule id after uri, Voice Browser will be hung up.
Is this estimated results?
-----
4th: /TestCustomGrammar/data/Japanese/grammars/grammar_RefDetail_KamokuInput.grxml#main_rule

-- grammar_RefDetail_KamokuInput.grxml --
<?xml version="1.0" encoding="UTF-8"?>
<grammar version="1.0" xmlns="http://www.w3.org/2001/06/grammar" tag-format="semantics/1.0" mode="dtmf" root="main_rule">

<rule id="main_rule" scope="public">
<one-of>
<item>1#</item>
<item>2#</item>
<item>3#</item>
<item>4#</item>
<item>6#</item>
<item>7#</item>
</one-of>
</rule>

</grammar>
-----
Best regards, K.Yamahara
massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
Hi Kenji.

What exactly does it mean "the Voice Browser hangs up" ? Do you see any error message ? The OD 7.2.3 and 8.1.2 are using the same AVB/VXI 7.2.1.5
Kenji
Joined: Jan 22, 2015
Messages: 105
Offline
Hi Massimo-san,

Thank you for your update.

>What exactly does it mean "the Voice Browser hangs up" ? Do you see any error message ? The OD 7.2.3 and 8.1.2 are using the same AVB/VXI 7.2.1.5
[Kenji]
In our call flow, the Voice Browser was looks like hangs up. Then call was disconnected.
And we confirmed below message in logs of getmpplogs.sh.
Therefore we understood VXMLMGR were stopped or restarted.
---
@2023-05-11 10:01:11,972|PSESM00002|WARN|SessMgr|13420|FileName=AppCtrl.cpp,LineNumber=233|Network error occurred on VXML message channel, error = 107|vmmpp81287####
---
@2023-05-11 10:01:11,973||FINE|SessMgr|1904||CSessionMgr::Monitor - App process error has occurred: VXMLMGR, with error 107|vmmpp81287####
----
Best regards, K.Yamahara
massimo__croci
Joined: Jan 31, 2020
Messages: 518
Offline
The error message is from the platform (the EP). Basing on the EP documentation, PSESM00002 error means that "The connection between the SessionManager and vxmlmgr processes encountered problems. The vxmlmgr process was either stopping or restarting".



Go to:   
Mobile view