| Message |
|
[+]
Avaya Orchestration Designer
» Delay after caller presses "*", 13/03/2014 15:40:44
» Go to message
|
|
Hi Neil,
1) "*" is not being used as a term char. It is used to play a list of accounts
2) Yes. The "Remote DTMF Processing" is set to No. Hence the VB is doing the DTMF Recognition.
Based on your response below, this seems to be a telephony issue. Any suggestions on how we can debug that?
Thanks,
Vamsi Kadiyala
|
 |
|
[+]
Avaya Orchestration Designer
» Delay after caller presses "*", 12/03/2014 13:01:03
» Go to message
|
|
Hi Neil,
The prompt is barginable.
I am attaching a snippet of the session slot log where we see the delay. I am also attaching the complete log for the call.
@2014-03-10 08:48:42,457||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Utility.cpp:469:LogIPCMessage|LSPP1NETAB04####
@2014-03-10 08:48:42,457||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving vpchannel.cpp:6497:SendMessage|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|waiting for rec result...|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering vpchannel.cpp:6525:WaitForMessage|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINE|VB|23691|Session=LSPP1NETAB04-2014069134829-8|waiting for DIALOG_SPECIFIC_MESSAGES|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.language Level = 0 value is STRING: en-us|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.maxnbest Level = 0 value is INTEGER: 1|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.sensitivity Level = 0 value is FLOAT: 0.5|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.speedVsAccuracy Level = 0 value is FLOAT: 0.5|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.terminatorChar Level = 0 value is STRING: #|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.timeout Level = 0 value is INTEGER: 8000|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINEST|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1279:Key = vxi.rec.timeoutTerminator Level = 0 value is INTEGER: 0|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINE|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1302:AVBrecRecognize() - Prompts are not queued|LSPP1NETAB04####
@2014-03-10 08:48:42,458||FINE|CommonVXI.Rec|22976|Session=LSPP1NETAB04-2014069134829-8|osbrec.cpp:1338:AVBrecRecognize() Input modes according to active grammars. ASR(OFF), bDTMF(ON)|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23037|Session=LSPP1NETAB04-2014069134829-8|******** Entering Dialog.cpp:337:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23037|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Dialog.cpp:337:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Entering Dialog.cpp:348:ProcessInboundMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Entering vpchannel.cpp:5620:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Leaving vpchannel.cpp:5620:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|successfully added msg to channel queue|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Dialog.cpp:348:ProcessInboundMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINE|VB|23691|Session=LSPP1NETAB04-2014069134829-8|received a VXML_PROMPT_PLAY_COMPLETE|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering Utility.cpp:469:LogIPCMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,265||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|VXML_PROMPT_PLAY_COMPLETE
{
dialogHandle: 8
playCompleted: 0
promptID: 15
position: 1800
markName: ""
markTimeElapsed: 1800
playCompleteStatus: COMPLETE_NORMAL
}
|LSPP1NETAB04####
@2014-03-10 08:48:44,266||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Utility.cpp:469:LogIPCMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,266||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving vpchannel.cpp:6525:WaitForMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,266||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|VPChannel::DoRecog got a VXML_PROMPT_PLAY_COMPLETE|LSPP1NETAB04####
@2014-03-10 08:48:44,266||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|waiting for rec result...|LSPP1NETAB04####
@2014-03-10 08:48:44,266||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering vpchannel.cpp:6525:WaitForMessage|LSPP1NETAB04####
@2014-03-10 08:48:44,266||FINE|VB|23691|Session=LSPP1NETAB04-2014069134829-8|waiting for DIALOG_SPECIFIC_MESSAGES|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23037|Session=LSPP1NETAB04-2014069134829-8|******** Entering Dialog.cpp:337:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23037|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Dialog.cpp:337:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Entering Dialog.cpp:348:ProcessInboundMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Entering vpchannel.cpp:5620:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Leaving vpchannel.cpp:5620:QueueMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|successfully added msg to channel queue|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23690|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Dialog.cpp:348:ProcessInboundMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINE|VB|23691|Session=LSPP1NETAB04-2014069134829-8|received a VXML_REC_RECOGNITION_RESULT|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering Utility.cpp:469:LogIPCMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|VXML_REC_RECOGNITION_RESULT
{
dialogHandle: 8
bargein: 1
DTMF: 1
result: "*"
haveUtterance: 0
utteranceDuration: 0
utterancePath: ""
rslt: [
inputMode: 177073336
]
}
|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving Utility.cpp:469:LogIPCMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving vpchannel.cpp:6525:WaitForMessage|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|VPChannel::DoRecog got a VXML_REC_RECOGNITION_RESULT|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:545:IsDTMF|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:545:IsDTMF|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:281:IsEnabled|LSPP1NETAB04####
@2014-03-10 08:48:47,384||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:281:IsEnabled|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:295:CheckPhrase|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|calling OSBrecDTMF::CheckPhrase() with grammarID: 17|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:295:CheckPhrase|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:545:IsDTMF|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:545:IsDTMF|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:281:IsEnabled|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:281:IsEnabled|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:295:CheckPhrase|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|calling OSBrecDTMF::CheckPhrase() with grammarID: 18|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:295:CheckPhrase|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:545:IsDTMF|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:545:IsDTMF|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:281:IsEnabled|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Leaving VPrecGrammar.cpp:281:IsEnabled|LSPP1NETAB04####
@2014-03-10 08:48:47,385||FINEST|VB|23691|Session=LSPP1NETAB04-2014069134829-8|******** Entering VPrecGrammar.cpp:295:CheckPhrase|LSPP1NETAB04####
|
|
|
[+]
Avaya Orchestration Designer
» Delay after caller presses "*", 12/03/2014 09:36:08
» Go to message
|
|
Hi,
We are migrating a DD 3.0 application that runs on Avaya IR to Orchestration Designer 6.0 that is running on AAEP. It is a like for like conversion, meaning none of the logic changed. There are a few nodes in the application where the caller can either enter his account number or press "*" to hear a list of these accounts. On the Avaya IR when a caller presses "*" at this node that transition to the next node was really quick and this is to be expected since the grammar has been filled and "termtimeout" is Zero Seconds by default in OD. However on AAEP when a caller presses "*" there is a delay of 4-5 seconds before the caller goes to the next node. I tried changing the "termtimeout" manually but that did not help. Just to verify I changed the "interdigittimeout" to 100 ms and after pressing "*" the transition to the next node is really quick. So this proved to me that the rest of the components were loading properly at that node. But this is not a fix for me since the caller needs to enter the account number here So my "interdigittimeout" needs to be higher.
Any idea why the "termtimeout" is not being triggered after the caller enters "*"?. This only seems to be a problem on AAEP and not Avaya IR. The "termtimeout" seems to work fine for numeric digits but does not seem to work for "*".
Thanks,
Vamsi Kadiyala
|
|
|
[+]
Avaya Orchestration Designer
» HTTPS protocol very slow, 10/02/2014 11:50:50
» Go to message
|
|
Hi,
We have migrated from Dialog Designer 3 to Orchestration Designer 6.0. We are using AAEP 6.0. The Dialog Designer modules are hosted on a Tomcat Server (6.0.29). We originally started of with "http" as the communication between the AAEP and the application server. The testing was smooth and the pages were being rendered quickly and we did not have any issues.
But we were asked to change to "https" between AAEP and Application server(Tomcat) due to some considerations. So for this we created the certificates on the application server, enabled SSL and imported the certificates onto the EPMS console. The communication has been established between AAEP and the Application Server (Tomcat) but it is very very slow. We are having a hard time figure out where the latency is coming from. I understand that "https" is a little more expensive and can take a little longer but no idea why it is so slow
Any idea what the reasons might be or how we can debug this?
Thanks,
Vamsi
|
|
|
[+]
Avaya Orchestration Designer
» AES Connector, 13/12/2013 10:17:59
» Go to message
|
|
Hi,
We are trying to use the Orchestration Designers AES Connector for integration with AES and using TSAPI. During the Tomcat start up I see the following errors in the aesConnector trace logs and TSAPI_Trace.txt
aesConnector Trace :
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.setTServerWait: TServer wait time is 4
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.init: initing AES connector. Verbosity set at 3
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.init: AES Connector Version is 06.00.13.01
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Observer timeout interval found: 100
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.CheckObserverTimeoutSet: Provider startup delay found: 4000
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.getConnectionString: No entry for TServer in configuration file
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.initProvider: Look for TServer config in DD application configuration (new method to 4.0)
13/12/2013 08:00:23:556 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: getting provider:AVAYA#LSPV1NETAA04#CSTA-S#LKPV1NETAB05
13/12/2013 08:00:24:102 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider obtained
13/12/2013 08:00:24:102 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: give provider cycles:40 of delay:100ms
13/12/2013 08:00:24:102 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is not in service -- STATE: 1, give small delay
13/12/2013 08:00:24:212 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
13/12/2013 08:00:24:212 DEBUG - CTIConnectorManager.ConfigureFromConfigurationFile: provider is now in service -- STATE: 2
13/12/2013 08:00:24:212 DEBUG - CTIConnectorManager.initProvider: provider vendor version is 9
13/12/2013 08:00:24:212 DEBUG - CTIConnectorManager.initProvider: setup named licensing.
13/12/2013 08:00:25:257 ERROR - CTICallObserver.CTICallObserver: failed to add an observer on extension: 16291 error is failure to monitor device
13/12/2013 08:00:25:288 DEBUG - ProviderMonitor: Checking:lkpv1netab05 for availability
13/12/2013 08:00:25:319 DEBUG - CTIConnectorManager.getProviderObserver: received provider in service event
13/12/2013 08:00:25:413 DEBUG - Provider:lkpv1netab05 has no valid observers, will retry to get them
13/12/2013 08:00:25:725 ERROR - CTICallObserver.CTICallObserver: failed to add an observer on extension: 16291 error is failure to monitor device
13/12/2013 08:00:33:728 DEBUG - ProviderMonitor: Checking:lkpv1netab05 for availability
13/12/2013 08:00:33:759 DEBUG - Provider:lkpv1netab05 has no valid observers, will retry to get them
13/12/2013 08:00:34:008 ERROR - CTICallObserver.CTICallObserver: failed to add an observer on extension: 16291 error is failure to monitor device
13/12/2013 08:00:42:011 DEBUG - ProviderMonitor: Checking:lkpv1netab05 for availability
13/12/2013 08:00:42:089 DEBUG - Provider:lkpv1netab05 has no valid observers, will retry to get them
TSAPI :
2013-12-13 08:00:24,960 [GetEventThread] INFO TSInvokeID - DONE handling INVOKE ID 11 for TSProvider[#1]@145fe3b
2013-12-13 08:00:24,960 [main] TRACE LucentAddressImpl - com.avaya.jtapi.tsapi.impl.LucentAddressImpl@1f7abae constructed.
2013-12-13 08:00:24,960 [main] TRACE LucentV7ProviderImpl - <-- getAddress[String number]: com.avaya.jtapi.tsapi.impl.LucentV7ProviderImpl@145fe3b
2013-12-13 08:00:24,960 [main] TRACE LucentAddressImpl - --> addCallObserver[CallObserver observer]: com.avaya.jtapi.tsapi.impl.LucentAddressImpl@1f7abae
2013-12-13 08:00:24,960 [main] TRACE LucentAddressImpl - --> addCallObserver[CallObserver observer, boolean remain]: com.avaya.jtapi.tsapi.impl.LucentAddressImpl@1f7abae
2013-12-13 08:00:24,960 [main] TRACE LucentAddressImpl - --> addCallEventMonitor(CallObserver observer, boolean remain,CallListener listener): com.avaya.jtapi.tsapi.impl.LucentAddressImpl@1f7abae
2013-12-13 08:00:24,992 [main] INFO TsapiSession - Sent InvokeID 12 for TSProvider[#1]@145fe3b
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - CSTAMonitorDevice ::=
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - {
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - deviceID "16291"
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - monitorFilter
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - {
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - call 0x0 < >
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - feature 0x0 < >
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - agent 0x0 < >
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - maintenance 0x0 < >
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - privateFilter 0
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - }
2013-12-13 08:00:24,992 [main] DEBUG TsapiSession - }
2013-12-13 08:00:25,132 [GetEventThread] INFO TsapiSession - Received invokeID 12 for TSProvider[#1]@145fe3b
2013-12-13 08:00:25,132 [GetEventThread] DEBUG TsapiSession - CSTAUniversalFailureConfEvent ::=
2013-12-13 08:00:25,132 [GetEventThread] DEBUG TsapiSession - {
2013-12-13 08:00:25,132 [GetEventThread] DEBUG TsapiSession - error 12 < INVALID_CSTA_DEVICE_IDENTIFIER >
2013-12-13 08:00:25,132 [GetEventThread] DEBUG TsapiSession - }
2013-12-13 08:00:25,132 [GetEventThread] INFO TSInvokeID - Handling INVOKE ID 12 for TSProvider[#1]@145fe3b
2013-12-13 08:00:25,132 [GetEventThread] INFO TSInvokeID - DONE handling INVOKE ID 12 for TSProvider[#1]@145fe3b
2013-12-13 08:00:25,132 [main] ERROR TSDevice - MonitorDevice request failed - retrying
com.avaya.jtapi.tsapi.TsapiPlatformException: CSTA Error: 12
at com.avaya.jtapi.tsapi.tsapiInterface.TSErrorMap.throwCSTAException(TSErrorMap.java:100)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:562)
at com.avaya.jtapi.tsapi.tsapiInterface.TsapiSession.send(TsapiSession.java:449)
at com.avaya.jtapi.tsapi.tsapiInterface.Tsapi.monitorDevice(Tsapi.java:1100)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2643)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.setMonitor(TSDevice.java:2565)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressCallMonitor(TSDevice.java:746)
at com.avaya.jtapi.tsapi.impl.core.TSDevice.addAddressCallMonitor(TSDevice.java:601)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addCallEventMonitor(TsapiAddress.java:812)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addCallObserver(TsapiAddress.java:713)
at com.avaya.jtapi.tsapi.impl.TsapiAddress.addCallObserver(TsapiAddress.java:404)
at com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager$CTICallObserver.init(CTIConnectorManager.java:296)
at com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager.prepareObservers(CTIConnectorManager.java:1741)
at com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager.configureFromApplicationConfig(CTIConnectorManager.java:1791)
at com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager.initProvider(CTIConnectorManager.java:2109)
at com.avaya.sce.cticonnector.servlet.server.CTIConnectorManager.init(CTIConnectorManager.java:1276)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1213)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1026)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4421)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4734)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1317)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:324)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1065)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:840)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1057)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463)
at org.apache.catalina.core.StandardService.start(StandardService.java:525)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:754)
at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
In my runtimeconfig I set up 16291 in the extension map of the AES server. 16291 is the DNIS associated with my TFN. Any idea as to what I am missing here?
Thanks,
Vamsi Kadiyala
|
|
|
[+]
Avaya Orchestration Designer
» Overriding the Session.dnis value Outside Orchestration Designer, 11/11/2013 08:17:23
» Go to message
|
|
Hi,
We read the ANI and DNIS from the Session.ani and Session.dnis values in our Orchestration Designer App. Our Call flow is driven based on the DNIS of the caller, ie We have multiple TFN's set-up each having its own DNIS and that drives the call flow. However in our test environment we only have one TFN set up. So is there a way I can manually ask for the DNIS in a static vxml page and override the value of Session.dnis from within that static vxml page?
I want to do this so that I don't change the Orchestration Designer code for testing purposes alone.
|
|
