Genesys CTI User Forum
Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: anoredis on December 16, 2013, 10:33:42 AM
-
Hello,
I need some help over here. I have installed 8.1 successfully and it's working perfectly. I have no experience (very little actually) with 7.6. I know that the application is generated as a set of asp files and to provide it you must set the IVR profile src to start.asp of the application. In GVP 8 I just point it to the Main.vxml. I have configured MCP LRG and an IVR profile that is using the Legacy GVP interpreter and points to the start.asp(?).
The call is established but I hear nothing. What am I doing wrong here?
-
Not hear about some pre-requisities with ASP scripts. It is just one of the type of language for writting web application, currently ASP is end-of-life and ASP.NET is using as major platform, but it is not related to the GVP and Genesys in general of course. MCP can get the vxml file from various directory as a webserver (most used option), filesystem (best for testing purposes), from network folder.So, all depends on your deployment and needs. You just have to add valid "address" of your vxml file to the IVR profile - if you have webapp which returns vxml, you have to point to the URL of this webapp, in other case point to the vxml directly (for example file:///C:/GVP/scripts/helloworld.vxml).
-
Thanks for replying Kubig.
So, for targeting a 7.6 application which doesn't contain a vxml file in its folder should I target the start.asp generated by Genesys Studio?
-
I do not know how is builded your application, but MCP need vxml for executing and it can get via HTTP protocol as I said in last topic. I do not know what do start.asp page, what returns to the GET requests.
-
The application is built with Gensys Studio application. It generates .asp pages. In 7.6 GVP, in the IVR profile you set the URI to http://myServer/myProject/start.asp. There is no vxml. But what about GVP 8.1? I set the URI same way as above (no vxml just a start.asp page) and I hear nothing...
Anyone, any syggestions?
-
What says MCP logs? What returns the webapp for first GET? Are you using MCP with version 8.1.4 and below (higher version does not support GVPi)
-
Not sure about the MCP logs. All seems normal. A lot of 200 OK and it fetches the page content and structure. Yes, I am aware of that. I use 8.1.4.
So, regardless what I have done. What is the correct path to follow when you are trying to get 7.6 applications to work with your 8.1 GVP? You just add a new IVR profile and tell it to use the legacy interpreter for the page you are targeting in its URI or you need to provide additional congiguration?
-
I cannot help, I have never used the Genesys studio for developing the vxml applications. From general point of view, no changes are necessary within using 7.6 vxml app with 8.1 GVP.
-
Thanks Kubig, no worries.
Does anybody know the drill? How do you target a 7.6 application through GVP 8.1? ???
-
[quote author=anoredis link=topic=8138.msg35825#msg35825 date=1387271468]
Thanks Kubig, no worries.
Does anybody know the drill? How do you target a 7.6 application through GVP 8.1? ???
[/quote]
as I wrote, application from 7.6 release (written in LGVP) is possible to play on GVP 8.1 (with MCP lower than 8.1.5 version) in general. It is necesssary to use application that are using ASP? What is IIS configuration for this application? You are not still answer the question about MCP logs, without similiar information is not possible to help you.
-
I have no access to the applications server. The applications are written in asp. Start.asp is something like the index.html of the application which defines the structure of the application. In the uri of the IVR profile i set the path to start.asp. as I would do with the Main.vxml of an application created with composer. I can send you the mcp log if you want, I cannot point to something specific in it
-
I seem to remember some options somewhere to specify which VoiceXML interpreter to use e.g. the old VoiceGenie one or the next generation one (NGI?). Sorry - short of time or would have checked the documentation for you.
-
Thank you very much for your reply genesysguru!
The option (at least the one I am aware of) is where you define a new IVR profile in Genesys Administrator. I have set it but still no luck.
Thank you very much for your time!
-
I repeat myself..logs,logs,logs...
-
As far as I remember there is an option to enable the legacy mode in the MCP. You must take care that the legacy mode is not supported in the last versions of MCP (8.1.7). As far as I know, the last MCP version that support Legacy mode is 8.1.4...
Regards
-
mfsaez I did not mess with any of the MCP options. I only set it in the IVR profile. I have installed the 8.1.4 version because I need CTI Connector and this is the last version that supports it.
Yes, kubig, you are right. I have managed to get it working. The ASR is working as well, at least in 8 applications. Simple test applications that I have created for 7.6 (just a couple of prompts) play as well. Now my concern is the architecture and how to set the CTI connector to work properly because I target complex applications that require CTI information. So far, the call is dropped because it asks for attached data.
-
You are false. CTI connector is supported in all version of GVP 8.1, it means 8.1.4+ as well. You never talked about CTI integration in this topic... What is your problem with CTI connector integration? Which function from CTI "portfolio" need? I think that CTI connector is no needed as more for almost function.
-
I am really new to this but I remember well that in the documentation it is stated that CTI connector is supported till 8.1.4. Additionally, my supervisor insisted that I installed this version for that cause. The case is this. We have a customer that has developed numerous applications in 7.6 and wants to migrate to 8.1 without messing with them. As far as I know the applications require userdata and that drops the call because of ctic misconfiguration. It would be GREAT if I hadn't to implement CTI connector...
-
So, ok..what is the problem within deployment of CTI Connector in your env?
-
CTI connector is a must for you as it is the "replacement" of TServer IVR con 7.6. On 8.x you don't need it because UserData goes with SIP headers and handled by SIP Server.
-
Happy New Year to everyone!! I wish you the best for 2014!!
I have implemented a solution with CTI connector. I still can't get it working. I have followed the "Voice Platform Solution 8.1 Integration Guide" for a behind mode. I have created a simple application with a prompt and a userdata which tries to fetch the connID. In my CTI connector log i get the following.
[code]2014-01-07 11:17:04.255 DBUG 00000000-00000000 2748 0AC00000 XMLMsgProcessThrd.cpp:58 Posting the XML page : <?xml version='1.0' encoding='UTF-8'?><!DOCTYPE GctiMsg SYSTEM 'IServer.dtd'><GctiMsg><CallId>F3B21374-AD9E-4B13-C8BB-9CE922CBB27B</CallId><EndCall EndCause='FeatureNotSupported'/></GctiMsg>[/code] I also have some questions that are not clarified in the manual (at least I did not find it) or it is not clear to me.
1) What is the "client name" which is a mandatory property in the CTI connector options? Is it the tenant name (like Resources?)
2) I have the RP 4900 which targets the place group which contains the 4901-4903 places. I have also created the 4901-4903 IVR ports. Can you please explain how the routing will be done? I do not have a clear picture of this. How is the whole procedure linked with an IVR profile?
Thank you all for your help!
-
Here is no education center, so do not expect that anybody will want to explain whole procedure and call flow of GVP model. In general, routing selects free place which is linked to the VTP port. The VTP port should be configured to contact RM in object annex. So, SIP server sends SIP invite to the RM and he checks CTI integration configuration (if is enabled, forced, etd.). RM decide if the CTI is necessary, if yes..sends SIP to the CTIC. CTIC gets DNIS through IVR T-Server and sends SIP invite to the RM for mapping IVR profile,choose free MCP and execute VXML script.
Clientname in CTIC configuration has to be pointed to the IVR object in Genesys configuration.
PS: You did not still answer the main question..why are you using CTIC? What are the reasons? Integration without CTIC is more simple and cover most of provided funcionalies.
-
Thanks for the explanation Kubig.
I have stated earlier that I have to use CTIC because the client wants to use 7.6 applications. Migration is only done through CTIC as it is mentioned in the documentation and instructed by my supervisor. It would be great if it didn't cause it would be fewer steps to be taken. If you know a workaround I would be grateful
-
Properly execution of 7.6 GVP application does not require CTI. It is not a prerequisite.CTIC is necessary in scenario when you need to use IVR T-Server (laarge environments) or to use functions that are available only through CTIC (ie. GetAccessNumber, Delete/replace KVP via T-Lib, GetStatistic). So, if no one from reason above does not meet it, you can deployGVP without CTIC and IVR T-Server. I strongly recommend to you use GVP without CTIC (it is more easier configuration and deployment) or learn about GVP before try to deploy it.
I have deployed GVP with CTIC many times and the procedure is not hard, but it is necessary to know how GVP works and know his model.
-
Yes, I need to use T-Server IVR for this one
-
Reasons? Using of 7.6 GVP applications is not the reason as I wrote.
So, if you "need" to use IVR T-Server.What is not understandable for you during the deployment procedure? Have you configured LRG for gateway and CTI integration on this base? Have you properly created VTP ports, IVR object, places, virtual agents for VTP? Have you properly configured CTIC and IVR T-Server/I-Server?What steps did you do at this time?
-
I guess his reasons can be a simple GetAccessNumber for Alcatel PBX for example...or many others.
What is not working? Can you see logs on TServer IVR at least indicating some type of connection to GVP CTIC?
-
Kubig, I have configured both Gateway always use CTI and CTI LRGs. I have created the virtual ports and the places for each one. Also a place group wich contains these places. I target the place group from the routing point in which i have loaded my simple strategy. I have added in the connections of RM the CTIC and at the IVR server the connection to TServer IVR.
Thank you Cavagnaro, Yes, I am able to see that it is logging in the TServer IVR
Bare with me, I am really new to this
-
CTIC with IVR T-Server/I-Server are integrated? IVR object in CME with necessary objects is created? If you start solution, in what status are the VTP ports?
-
Yes IVR object in Switching->IVR was created, i have provided the information of the TServer IVR hostadress and port no to the CTIC mandatory options and added the connection to the IVR Server into TServer IVR and vice versa.
-
Just created or confiured as well? This is very important :-) Each object (VTP, vagent,IVR, IVR ports) has specific configuration.
-
Yes, I know :) I had the manual open and went step by step for behind mode. Created all according to the "Voice Platform Solution 8.1
Integration Guide". I have not created any virtual agent as I never encountered this in the guide.
-
[quote author=anoredis link=topic=8138.msg35883#msg35883 date=1389102921]
Yes, I am able to see that it is logging in the TServer IVR
[/quote]
Then maybe show us some TServer IVR logs when you try to establish a call with CTI?
-
Ofcourse, sorry for the many lines. I make a call to the RP 4900. I hear a prompt and then press 1. It is supposed to get some data and if successful it will play some music. Still no luck hearing the music. After pressing 1 the call drops after a while.
[code]@09:54:36.3690 [ISCC] [connection 01afde90] connecting [0]1
@09:54:36.3690 [ISCC] [connection 01b019e0] Received from connection [528]2
@09:54:36.3690 [ISCC] Received from server TServerTSAPI@PDS Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690372 [00b26184]
ISCCAttributeTrackingID 11532763 [00aff9db]
@09:54:36.3690 [ISCC] Error: Server TServerTSAPI@PDS Switch/1 has rejected the connection. Reconnecting...
@09:54:36.3690 [ISCC] [connection 01b019e0] disconnected [528]2
@09:54:36.3690 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {disconnected}}
@09:54:36.3690 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {connecting}}
@09:54:36.3690 [ISCC] [connection 01b019e0] connecting [0]1
@09:54:41.3690 [ISCC] [connection 01afde90] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:41.3690 [ISCC] [connection 01afde90] Starting connection [528]1
@09:54:41.3690 [ISCC] [connection 01afde90] Parameters: ("name"="SIPAvayaServer","host"="w2k3gen07.test.com","is-server"="1","client-type"="1","server-type"="1","port"="4060","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:41.3690 [ISCC] [connection 01b019e0] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:41.3690 [ISCC] [connection 01b019e0] Starting connection [512]1
@09:54:41.3690 [ISCC] [connection 01b019e0] Parameters: ("name"="TServerTSAPI","host"="W2K3GEN02","is-server"="1","client-type"="1","server-type"="1","port"="7000","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:41.3690 [ISCC] [connection 01afde90] Socket connected on connection [528]1
@09:54:41.3690 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {authorizing}}
@09:54:41.3690 [ISCC] Send to server SIPAvayaServer@SIP Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690373 [00b26185]
ISCCAttributeReferenceID 11690373 [00b26185]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:41.3690 [ISCC] [connection 01afde90] Sent to connection [528]2
@09:54:41.3850 [ISCC] [connection 01b019e0] Socket connected on connection [512]1
@09:54:41.3850 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {authorizing}}
@09:54:41.3850 [ISCC] Send to server TServerTSAPI@PDS Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690374 [00b26186]
ISCCAttributeReferenceID 11690374 [00b26186]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:41.3850 [ISCC] [connection 01b019e0] Sent to connection [512]2
@09:54:41.3850 [ISCC] [connection 01afde90] Received from connection [528]2
@09:54:41.3850 [ISCC] Received from server SIPAvayaServer@SIP Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690373 [00b26185]
ISCCAttributeTrackingID 11584707 [00b0c4c3]
@09:54:41.3850 [ISCC] Error: Server SIPAvayaServer@SIP Switch/1 has rejected the connection. Reconnecting...
@09:54:41.3850 [ISCC] [connection 01afde90] disconnected [528]2
@09:54:41.3850 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {disconnected}}
@09:54:41.3850 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {connecting}}
@09:54:41.3850 [ISCC] [connection 01afde90] connecting [0]1
@09:54:41.3850 [ISCC] [connection 01b019e0] Received from connection [512]2
@09:54:41.3850 [ISCC] Received from server TServerTSAPI@PDS Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690374 [00b26186]
ISCCAttributeTrackingID 11532766 [00aff9de]
@09:54:41.3850 [ISCC] Error: Server TServerTSAPI@PDS Switch/1 has rejected the connection. Reconnecting...
@09:54:41.3850 [ISCC] [connection 01b019e0] disconnected [512]2
@09:54:41.3850 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {disconnected}}
@09:54:41.3850 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {connecting}}
@09:54:41.3850 [ISCC] [connection 01b019e0] connecting [0]1
@09:54:46.3850 [ISCC] [connection 01afde90] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:46.3850 [ISCC] [connection 01afde90] Starting connection [512]1
@09:54:46.3850 [ISCC] [connection 01afde90] Parameters: ("name"="SIPAvayaServer","host"="w2k3gen07.test.com","is-server"="1","client-type"="1","server-type"="1","port"="4060","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:46.3850 [ISCC] [connection 01b019e0] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:46.3850 [ISCC] [connection 01b019e0] Starting connection [528]1
@09:54:46.3850 [ISCC] [connection 01b019e0] Parameters: ("name"="TServerTSAPI","host"="W2K3GEN02","is-server"="1","client-type"="1","server-type"="1","port"="7000","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:46.3850 [ISCC] [connection 01afde90] Socket connected on connection [512]1
@09:54:46.3850 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {authorizing}}
@09:54:46.3850 [ISCC] Send to server SIPAvayaServer@SIP Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690375 [00b26187]
ISCCAttributeReferenceID 11690375 [00b26187]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:46.3850 [ISCC] [connection 01afde90] Sent to connection [512]2
@09:54:46.4010 [ISCC] [connection 01b019e0] Socket connected on connection [528]1
@09:54:46.4010 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {authorizing}}
@09:54:46.4010 [ISCC] Send to server TServerTSAPI@PDS Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690376 [00b26188]
ISCCAttributeReferenceID 11690376 [00b26188]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:46.4010 [ISCC] [connection 01b019e0] Sent to connection [528]2
@09:54:46.4010 [ISCC] [connection 01afde90] Received from connection [512]2
@09:54:46.4010 [ISCC] Received from server SIPAvayaServer@SIP Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690375 [00b26187]
ISCCAttributeTrackingID 11584709 [00b0c4c5]
@09:54:46.4010 [ISCC] Error: Server SIPAvayaServer@SIP Switch/1 has rejected the connection. Reconnecting...
@09:54:46.4010 [ISCC] [connection 01afde90] disconnected [512]2
@09:54:46.4010 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {disconnected}}
@09:54:46.4010 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {connecting}}
@09:54:46.4010 [ISCC] [connection 01afde90] connecting [0]1
@09:54:46.4010 [ISCC] [connection 01b019e0] Received from connection [528]2
@09:54:46.4010 [ISCC] Received from server TServerTSAPI@PDS Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690376 [00b26188]
ISCCAttributeTrackingID 11532768 [00aff9e0]
@09:54:46.4010 [ISCC] Error: Server TServerTSAPI@PDS Switch/1 has rejected the connection. Reconnecting...
@09:54:46.4010 [ISCC] [connection 01b019e0] disconnected [528]2
@09:54:46.4010 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {disconnected}}
@09:54:46.4010 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {connecting}}
@09:54:46.4010 [ISCC] [connection 01b019e0] connecting [0]1
@09:54:50.8700 [gli:WARN]: request for fd: 524
@09:54:50.8700 [gli:DEBUG]: Receiving message on ( -1 , 2 )
fd = 524
localAddr = 10.197.100.33:7001
remoteAddr = 10.197.101.14:56805
@09:54:50.8700 [gli:DEBUG3]: Read:
0: 00 03 01 32 02 00 3c 3f 78 6d 6c 20 76 65 72 73 * ...2..<?xml vers
16: 69 6f 6e 3d 22 31 2e 30 22 20 65 6e 63 6f 64 69 * ion="1.0" encodi
32: 6e 67 3d 22 75 74 66 2d 38 22 3f 3e 3c 21 44 4f * ng="utf-8"?><!DO
48: 43 54 59 50 45 20 47 63 74 69 4d 73 67 20 53 59 * CTYPE GctiMsg SY
64: 53 54 45 4d 20 22 49 53 65 72 76 65 72 2e 64 74 * STEM "IServer.dt
80: 64 22 3e 0d 0a 3c 47 63 74 69 4d 73 67 3e 0d 0a * d">..<GctiMsg>..
96: 20 20 20 20 3c 43 61 6c 6c 49 64 3e 0d 0a 09 09 * <CallId>....
112: 45 46 33 46 41 33 35 31 2d 44 30 39 41 2d 34 44 * EF3FA351-D09A-4D
128: 34 46 2d 34 37 42 30 2d 45 34 34 46 44 42 32 37 * 4F-47B0-E44FDB27
144: 44 46 41 35 0d 0a 20 20 20 20 3c 2f 43 61 6c 6c * DFA5.. </Call
160: 49 64 3e 0d 0a 20 20 20 20 3c 4e 65 77 43 61 6c * Id>.. <NewCal
176: 6c 20 43 61 6c 6c 43 6f 6e 74 72 6f 6c 4d 6f 64 * l CallControlMod
192: 65 3d 22 4e 65 74 77 6f 72 6b 22 20 56 65 72 73 * e="Network" Vers
208: 69 6f 6e 3d 22 34 2e 30 22 20 3e 0d 0a 20 20 20 * ion="4.0" >..
224: 20 20 20 20 20 3c 43 61 6c 6c 65 64 4e 75 6d 3e * <CalledNum>
240: 0d 0a 20 20 20 20 20 20 20 20 20 20 20 20 34 39 * .. 49
256: 30 33 0d 0a 20 20 20 20 20 20 20 20 3c 2f 43 61 * 03.. </Ca
272: 6c 6c 65 64 4e 75 6d 3e 0d 0a 20 20 20 20 3c 2f * lledNum>.. </
288: 4e 65 77 43 61 6c 6c 3e 0d 0a 3c 2f 47 63 74 69 * NewCall>..</Gcti
304: 4d 73 67 3e 0d 0a * Msg>..
@09:54:50.8700 [xml:DEBUG]: XmlSap::process(): Xml string received = [ <?xml version="1.0" encoding="utf-8"?><!DOCTYPE GctiMsg SYSTEM "IServer.dtd">
<GctiMsg>
<CallId>
EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5
</CallId>
<NewCall CallControlMode="Network" Version="4.0" >
<CalledNum>
4903
</CalledNum>
</NewCall>
</GctiMsg>
]
@09:54:50.8700 [tcl:DEBUG2]: App Received: Type = Indication
Id = "00.00.0a.72"
Call Id = "00.00.02.2a"
Data = ...
Offset = 6
Properties =
[GLI] = Properties:
[AppId] = Int(0)
[Circuit] = Int(2)
[Group] = Int(-1)
[Version] = Int(2)
[XML] = Properties:
[Encoding] = String(utf-8)
[Message] = Properties:
[GctiMsg] = Properties:
[CallId] = Properties:
[Val] = String(EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5)
[NewCall] = Properties:
[Attrs] = Properties:
[CallControlMode] = String(Network)
[Version] = String(4.0)
[CalledNum] = Properties:
[Val] = String(4903)
[Version] = String(1.0)
09:54:50.870 Trc 29043 Received message 00.00.02.2a:00.00.0a.72:New Call Network.
@09:54:50.8700 [tcl:DEBUG2]: TimerManager::startTimer: local id: 359 , conn id: 778043406 , period: 28800000
@09:54:50.8700 [tcl:DEBUG]: TclHandler::copy_value : IN_MSG [ GLI.Group ] -> USER_DATA [ GLI.Group ]
@09:54:50.8700 [tcl:DEBUG]: TclHandler::copy_value : IN_MSG [ GLI.Circuit ] -> USER_DATA [ GLI.Circuit ]
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ XML.Message.GctiMsg.NewCall.CalledNum.Val ] = String(4903)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ XML.Message.GctiMsg.NewCall.Attrs.Version ] = String(4.0)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ XML.Message.GctiMsg.NewCall.ANI.Val ]: set to default val:
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ XML.Message.GctiMsg.NewCall.DNIS.Val ]: set to default val:
@09:54:50.8700 [tcl:DEBUG]: TclHandler::value_exists : ENV_DATA [ TLIB.DNList.4903 ] exists
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : ENV_DATA [ TLIB.DNList.4903.DNType ] = Int(1)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ GLI.Group ] = Int(-1)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ GLI.Circuit ] = Int(2)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ XML.Encoding ] = String(utf-8)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::set_value : USER_DATA [ DestEncoder ] = String(UTF-8)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::copy_value : IN_MSG [ XML.Message.GctiMsg.CallId.Val ] -> USER_DATA [ CallID ]
@09:54:50.8700 [tcl:DEBUG]: New call rejected on CalledNum: 4903 (called number not configured)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::queue_event creating internal event: InternalStopIServer ( 00.00.02.2a (null) )
@09:54:50.8700 [tcl:DEBUG]: TclHandler::create_msg : Created message: ( 00.00.02.2a 00.00.0a.73 )
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : IN_MSG [ XML.Message.GctiMsg.CallId.Val ] = String(EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::get_value : USER_DATA [ DestEncoder ] = String(UTF-8)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::set_value : OUT_MSG [ XML.Raw ] = String(<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE GctiMsg SYSTEM 'IServer.dtd'><GctiMsg><CallId>EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5</CallId><EndCall EndCause='FeatureNotSupported'/></GctiMsg>)
@09:54:50.8700 [tcl:DEBUG]: TclHandler::copy_value : USER_DATA [ GLI.Group ] -> OUT_MSG [ GLI.Group ]
@09:54:50.8700 [tcl:DEBUG]: TclHandler::copy_value : USER_DATA [ GLI.Circuit ] -> OUT_MSG [ GLI.Circuit ]
@09:54:50.8700 [tcl:DEBUG]: TclHandler::set_value : OUT_MSG [ RouteDest ] = String(ivr)
09:54:50.870 Trc 29044 Sent message 00.00.02.2a:00.00.0a.73:EndCall.
@09:54:50.8700 [tcl:DEBUG2]: App Sent: Type = Request
Id = "00.00.0a.73"
Call Id = "00.00.02.2a"
Data = ...
Offset = 0
Properties =
[GLI] = Properties:
[Circuit] = Int(2)
[Group] = Int(-1)
[RouteDest] = String(ivr)
[XML] = Properties:
[Raw] = String(<?xml version='1.0' encoding='UTF-8'?><!DOCTYPE GctiMsg SYSTEM 'IServer.dtd'><GctiMsg><CallId>EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5</CallId><EndCall EndCause='FeatureNotSupported'/></GctiMsg>)
@09:54:50.8700 [tcl:DEBUG2]: stop: local id: 359 conn id: 778043406
@09:54:50.8700 [tcl:DEBUG]: Notify End Call: 00.00.02.2a
@09:54:50.8700 [xml:DEBUG]: XmlSap::process(): Xml string to transmit = [ <?xml version='1.0' encoding='UTF-8'?><!DOCTYPE GctiMsg SYSTEM 'IServer.dtd'><GctiMsg><CallId>EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5</CallId><EndCall EndCause='FeatureNotSupported'/></GctiMsg> ]
@09:54:50.8700 [gli:DEBUG]: GliManager::Write on group: -1 , circuitId: 2 cp: 22641488
@09:54:50.8700 [gli:DEBUG]: GliManager::Write on group: -1 , circuitId: 2
@09:54:50.8700 [gli:DEBUG]: Sending message on ( -1 , 2 )
fd = 524
localAddr = 10.197.100.33:7001
remoteAddr = 10.197.101.14:56805
@09:54:50.8700 [gli:DEBUG3]: Wrote:
0: 00 03 00 c0 02 00 3c 3f 78 6d 6c 20 76 65 72 73 * ......<?xml vers
16: 69 6f 6e 3d 27 31 2e 30 27 20 65 6e 63 6f 64 69 * ion='1.0' encodi
32: 6e 67 3d 27 55 54 46 2d 38 27 3f 3e 3c 21 44 4f * ng='UTF-8'?><!DO
48: 43 54 59 50 45 20 47 63 74 69 4d 73 67 20 53 59 * CTYPE GctiMsg SY
64: 53 54 45 4d 20 27 49 53 65 72 76 65 72 2e 64 74 * STEM 'IServer.dt
80: 64 27 3e 3c 47 63 74 69 4d 73 67 3e 3c 43 61 6c * d'><GctiMsg><Cal
96: 6c 49 64 3e 45 46 33 46 41 33 35 31 2d 44 30 39 * lId>EF3FA351-D09
112: 41 2d 34 44 34 46 2d 34 37 42 30 2d 45 34 34 46 * A-4D4F-47B0-E44F
128: 44 42 32 37 44 46 41 35 3c 2f 43 61 6c 6c 49 64 * DB27DFA5</CallId
144: 3e 3c 45 6e 64 43 61 6c 6c 20 45 6e 64 43 61 75 * ><EndCall EndCau
160: 73 65 3d 27 46 65 61 74 75 72 65 4e 6f 74 53 75 * se='FeatureNotSu
176: 70 70 6f 72 74 65 64 27 2f 3e 3c 2f 47 63 74 69 * pported'/></Gcti
192: 4d 73 67 3e * Msg>
@09:54:50.8700 [gli:DEBUG]: Notify Sent: ( 00.00.02.2a 00.00.0a.73 )
@09:54:50.8700 [gli:DEBUG]:
Properties:
[GLI] = Properties:
[Circuit] = Int(2)
[Group] = Int(-1)
@09:54:50.9170 [gli:WARN]: request for fd: 524
@09:54:50.9170 [gli:DEBUG]: Receiving message on ( -1 , 2 )
fd = 524
localAddr = 10.197.100.33:7001
remoteAddr = 10.197.101.14:56805
@09:54:50.9170 [gli:DEBUG3]: Read:
0: 00 03 00 df 02 00 3c 3f 78 6d 6c 20 76 65 72 73 * ......<?xml vers
16: 69 6f 6e 3d 22 31 2e 30 22 20 65 6e 63 6f 64 69 * ion="1.0" encodi
32: 6e 67 3d 22 75 74 66 2d 38 22 3f 3e 3c 21 44 4f * ng="utf-8"?><!DO
48: 43 54 59 50 45 20 47 63 74 69 4d 73 67 20 53 59 * CTYPE GctiMsg SY
64: 53 54 45 4d 20 22 49 53 65 72 76 65 72 2e 64 74 * STEM "IServer.dt
80: 64 22 3e 0d 0a 3c 47 63 74 69 4d 73 67 3e 0d 0a * d">..<GctiMsg>..
96: 20 20 20 20 3c 43 61 6c 6c 49 64 3e 0d 0a 09 09 * <CallId>....
112: 45 46 33 46 41 33 35 31 2d 44 30 39 41 2d 34 44 * EF3FA351-D09A-4D
128: 34 46 2d 34 37 42 30 2d 45 34 34 46 44 42 32 37 * 4F-47B0-E44FDB27
144: 44 46 41 35 0d 0a 20 20 20 20 3c 2f 43 61 6c 6c * DFA5.. </Call
160: 49 64 3e 0d 0a 20 20 20 20 3c 45 6e 64 43 61 6c * Id>.. <EndCal
176: 6c 20 45 6e 64 43 61 75 73 65 3d 22 4e 6f 72 6d * l EndCause="Norm
192: 61 6c 22 20 3e 0d 0a 20 20 20 20 3c 2f 45 6e 64 * al" >.. </End
208: 43 61 6c 6c 3e 0d 0a 3c 2f 47 63 74 69 4d 73 67 * Call>..</GctiMsg
224: 3e 0d 0a * >..
@09:54:50.9170 [xml:DEBUG]: XmlSap::process(): Xml string received = [ <?xml version="1.0" encoding="utf-8"?><!DOCTYPE GctiMsg SYSTEM "IServer.dtd">
<GctiMsg>
<CallId>
EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5
</CallId>
<EndCall EndCause="Normal" >
</EndCall>
</GctiMsg>
]
@09:54:50.9170 [tcl:DEBUG2]: App Received: Type = Indication
Id = "00.00.0a.75"
Call Id = "00.00.02.2b"
Data = ...
Offset = 6
Properties =
[GLI] = Properties:
[AppId] = Int(0)
[Circuit] = Int(2)
[Group] = Int(-1)
[Version] = Int(2)
[XML] = Properties:
[Encoding] = String(utf-8)
[Message] = Properties:
[GctiMsg] = Properties:
[CallId] = Properties:
[Val] = String(EF3FA351-D09A-4D4F-47B0-E44FDB27DFA5)
[EndCall] = Properties:
[Attrs] = Properties:
[EndCause] = String(Normal)
[Version] = String(1.0)
09:54:50.917 Trc 29043 Received message 00.00.02.2b:00.00.0a.75:End Call.
@09:54:50.9170 [tcl:DEBUG]: TclHandler::value_exists : USER_DATA [ SM.LastError.OriginalProps.TLIB.Message ] does not exist
@09:54:50.9170 [tcl:DEBUG]: TclHandler::value_exists : USER_DATA [ SM.LastError.OriginalProps.XML.Message ] exists
@09:54:50.9170 [tcl:DEBUG]: TclHandler::value_exists : USER_DATA [ SM.LastError.OriginalProps.GLI.Group ] exists
@09:54:50.9170 [tcl:DEBUG]: TclHandler::value_exists : USER_DATA [ SM.LastError.OriginalProps.GLI.Circuit ] exists
@09:54:50.9170 [tcl:DEBUG]: TclHandler::value_exists : USER_DATA [ SM.LastError.OriginalProps.XML.Message.GctiMsg.EndCall ] exists
@09:54:50.9170 [tcl:DEBUG]: Notify End Call: 00.00.02.2b
@09:54:51.4010 [ISCC] [connection 01afde90] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:51.4010 [ISCC] [connection 01afde90] Starting connection [528]1
@09:54:51.4010 [ISCC] [connection 01afde90] Parameters: ("name"="SIPAvayaServer","host"="w2k3gen07.test.com","is-server"="1","client-type"="1","server-type"="1","port"="4060","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:51.4010 [ISCC] [connection 01b019e0] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:51.4010 [ISCC] [connection 01b019e0] Starting connection [512]1
@09:54:51.4010 [ISCC] [connection 01b019e0] Parameters: ("name"="TServerTSAPI","host"="W2K3GEN02","is-server"="1","client-type"="1","server-type"="1","port"="7000","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:51.4010 [ISCC] [connection 01afde90] Socket connected on connection [528]1
@09:54:51.4010 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {authorizing}}
@09:54:51.4010 [ISCC] Send to server SIPAvayaServer@SIP Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690377 [00b26189]
ISCCAttributeReferenceID 11690377 [00b26189]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:51.4010 [ISCC] [connection 01afde90] Sent to connection [528]2
@09:54:51.4170 [ISCC] [connection 01b019e0] Socket connected on connection [512]1
@09:54:51.4170 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {authorizing}}
@09:54:51.4170 [ISCC] Send to server TServerTSAPI@PDS Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690378 [00b2618a]
ISCCAttributeReferenceID 11690378 [00b2618a]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:51.4170 [ISCC] [connection 01b019e0] Sent to connection [512]2
@09:54:51.4170 [ISCC] [connection 01afde90] Received from connection [528]2
@09:54:51.4170 [ISCC] Received from server SIPAvayaServer@SIP Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690377 [00b26189]
ISCCAttributeTrackingID 11584711 [00b0c4c7]
@09:54:51.4170 [ISCC] Error: Server SIPAvayaServer@SIP Switch/1 has rejected the connection. Reconnecting...
@09:54:51.4170 [ISCC] [connection 01afde90] disconnected [528]2
@09:54:51.4170 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {disconnected}}
@09:54:51.4170 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {connecting}}
@09:54:51.4170 [ISCC] [connection 01afde90] connecting [0]1
@09:54:51.4170 [ISCC] [connection 01b019e0] Received from connection [512]2
@09:54:51.4170 [ISCC] Received from server TServerTSAPI@PDS Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690378 [00b2618a]
ISCCAttributeTrackingID 11532771 [00aff9e3]
@09:54:51.4170 [ISCC] Error: Server TServerTSAPI@PDS Switch/1 has rejected the connection. Reconnecting...
@09:54:51.4170 [ISCC] [connection 01b019e0] disconnected [512]2
@09:54:51.4170 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {disconnected}}
@09:54:51.4170 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {connecting}}
@09:54:51.4170 [ISCC] [connection 01b019e0] connecting [0]1
@09:54:56.4170 [ISCC] [connection 01afde90] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:56.4170 [ISCC] [connection 01afde90] Starting connection [512]1
@09:54:56.4170 [ISCC] [connection 01afde90] Parameters: ("name"="SIPAvayaServer","host"="w2k3gen07.test.com","is-server"="1","client-type"="1","server-type"="1","port"="4060","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:56.4170 [ISCC] [connection 01b019e0] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:54:56.4170 [ISCC] [connection 01b019e0] Starting connection [528]1
@09:54:56.4170 [ISCC] [connection 01b019e0] Parameters: ("name"="TServerTSAPI","host"="W2K3GEN02","is-server"="1","client-type"="1","server-type"="1","port"="7000","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:54:56.4170 [ISCC] [connection 01afde90] Socket connected on connection [512]1
@09:54:56.4170 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {authorizing}}
@09:54:56.4170 [ISCC] Send to server SIPAvayaServer@SIP Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690379 [00b2618b]
ISCCAttributeReferenceID 11690379 [00b2618b]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:56.4170 [ISCC] [connection 01afde90] Sent to connection [512]2
@09:54:56.4320 [ISCC] [connection 01b019e0] Socket connected on connection [528]1
@09:54:56.4320 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {authorizing}}
@09:54:56.4320 [ISCC] Send to server TServerTSAPI@PDS Switch/1: message ISCCRequestAuthorize
ISCCAttributeTrackingID 11690380 [00b2618c]
ISCCAttributeReferenceID 11690380 [00b2618c]
ISCCAttributeTSCPVersion '7.6.008.20'
ISCCAttributeServerVersion '7.5.016.16'
ISCCAttributeServerXCapabilities '(2=(56=393216),92=(56=393216),160=(146=1),161=(146=1),162=(146=1))'
ISCCAttributeServerCapabilityMask {bstring}
ISCCAttributeProtocolVersion 'ISCC protocol 5.1'
ISCCAttributeDeviceType -1 [ffffffff]
ISCCAttributeServerRole Primary
ISCCAttributeServerLocation 'Test GVP-SIPSwitch'
ISCCAttributeServerName 'IPCS-TServerIVR'
@09:54:56.4320 [ISCC] [connection 01b019e0] Sent to connection [528]2
@09:54:56.4320 [ISCC] [connection 01afde90] Received from connection [512]2
@09:54:56.4320 [ISCC] Received from server SIPAvayaServer@SIP Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690379 [00b2618b]
ISCCAttributeTrackingID 11584713 [00b0c4c9]
@09:54:56.4320 [ISCC] Error: Server SIPAvayaServer@SIP Switch/1 has rejected the connection. Reconnecting...
@09:54:56.4320 [ISCC] [connection 01afde90] disconnected [512]2
@09:54:56.4320 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {disconnected}}
@09:54:56.4320 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {connecting}}
@09:54:56.4320 [ISCC] [connection 01afde90] connecting [0]1
@09:54:56.4320 [ISCC] [connection 01b019e0] Received from connection [528]2
@09:54:56.4320 [ISCC] Received from server TServerTSAPI@PDS Switch/1: message ISCCEventAuthorizeResponse
ISCCAttributeResponseCode Not_Configured
ISCCAttributeReferenceID 11690380 [00b2618c]
ISCCAttributeTrackingID 11532773 [00aff9e5]
@09:54:56.4320 [ISCC] Error: Server TServerTSAPI@PDS Switch/1 has rejected the connection. Reconnecting...
@09:54:56.4320 [ISCC] [connection 01b019e0] disconnected [528]2
@09:54:56.4320 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {disconnected}}
@09:54:56.4320 [ISCC] {server TServerTSAPI@PDS Switch {role backup} {connecting}}
@09:54:56.4320 [ISCC] [connection 01b019e0] connecting [0]1
@09:55:01.4320 [ISCC] [connection 01afde90] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:55:01.4320 [ISCC] [connection 01afde90] Starting connection [528]1
@09:55:01.4320 [ISCC] [connection 01afde90] Parameters: ("name"="SIPAvayaServer","host"="w2k3gen07.test.com","is-server"="1","client-type"="1","server-type"="1","port"="4060","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:55:01.4320 [ISCC] [connection 01b019e0] Timer expired on connection [0]1
addp-trace 1
(addp_xconfig) local 30000 msec, remote 90000 msec, trace off
@09:55:01.4320 [ISCC] [connection 01b019e0] Starting connection [512]1
@09:55:01.4320 [ISCC] [connection 01b019e0] Parameters: ("name"="TServerTSAPI","host"="W2K3GEN02","is-server"="1","client-type"="1","server-type"="1","port"="7000","protocol"="addp","addp-timeout"="30","addp-remote-timeout"="90","addp-trace"="1")
@09:55:01.4320 [ISCC] [connection 01afde90] Socket connected on connection [528]1
@09:55:01.4320 [ISCC] {server SIPAvayaServer@SIP Switch {role backup} {authorizing}}
@09:55:01.4320 [ISCC] Send to server SIPAvayaServer@SIP Switch/1: message ISCCRequestAuthorize
[/code]
-
For me it looks like bad configuration of one of the necessary objects. As first, try to check your IVR object configuration and related objects under it. For sure, check your VTP configuration (annex) and be sure that are located under SIP switch and not under dummy.
-
I am sure you are right about sth is not configured correctly but I do not think that it is that one. The guide states that they should be the dummy ones. I have tried the actual ones too on the real sipServer but with no luck. I did not find any information about the VTPs Annex. My VTPs have just the following properties on the TServer section. [tt]contact=sip:RMIPAdress:RMPort and event-ringing-on-100trying=true[/tt]
-
I usually add a prefix option to the VTP port configuration. I think that bad configuration is on IVR object layer or in CTIC <-> IVR integration. How did you configure IVR object and related objects? Where did you create the VTP?
-
I have created an IVR object which is named GVP8 which i set as the clientname in CTIC. Version 8.1.4 and IVR server the IPCS-IServer. Then at the IVR ports I add the ports 4901-4903 which I link to the dummy ones (same names both on dummy-real). In CTIC i have set the address and port I found on the gli section of the IVRServer and the clientname GVP8 as I mentioned before
-
And in IVR ports options have you configured something? Where are located the VTP ports - under dummy or SIP switch?
-
the IVR ports just have two options in TServer section.
contact=sip:RMIPAdress:RMPort
event-ringing-on-100trying=true
i have created them in both, real and dummy switch. Also I have tried both to link dummy and real switch ports in the IVR object but I have the same result.
-
IVR ports under IVR object must have other options. The options that you wrote are related to the VTP ports. All objects created under switch must be located under SIP switch, not under dummy
-
Yes, you are right. The IVR ports have no options by default. The guide does not provide any information on that. It just says that you must add the IVR ports named respectively to the VTPs you have created. No further info about the IVR ports.
-
Also, my IVRServer and TServer IVR are on 7.5 version. I have conf server, sip server and GVP components in 8.1. Do you think that this may be causing any trouble? :-\
-
I think you don't have Connection between TServer legacy and TServer IVR, therefore ISCC validation is refused.
-
I have made the connection but still getting the same error. Feature not supported etc.. :(
-
The connection is not necessary and I think is not a root cause of the issue
-
I have installed fresh IVRServer and TServer_IVR ver 8.1. Do I have to install any IVR driver for that?
-
No. But I am not sure that newer version will solve your problem. I do not think the problem/cause is in version.
-
Thanks Kubig!
still stuck here :(
-
You do know there are some functions you can/can't use while using CTI, right? I think you are using one of those and therefore your app fails.
-
I would recommend test all on "hello world" vxml application that does not contain any advance function.
-
At last! I got it!! ;D
Among others...
[code]13:47:33.937 Std 20104 EROR 00000000-00000000 3312 0AC0057D UDataResp.cpp:215 UDataResp returned failure with result = 'NoMatch'. sessionid=9023AC92-275B-4C6B-0892-0[/code]
The key being requested by the application is not present on the IVR Server side.
I have to deliver GVP proactive solution till friday, fingers crossed, I have never done such a thing before... ???
-
Ohh sh!t, schoolboy error - any PoC must be deployed with "extreme" easy sample, which cannot bring another problems or issue. The worst way how to try or test some solution is do that with advanced application and non-basic steps/procedure. If you will fill this prerequisite in future, you will have better and peaceful life and do not waste time on "PEBKAC" (Problem exists between keyboard and chair) problems.