|
Home > Archive > Voice over IP Cisco > September 2006 > JTAPI subsystem in partial_service
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
JTAPI subsystem in partial_service
|
|
| Rasim Duric 2006-09-08, 1:12 am |
| Hi all,
JTAPI subsystem is flapping between in_service and partial_service on
one of our IPCCX applications. I've stopped and restarted the CRS engine
but it would run for a while and back in partial_service again. I can
see in the MIVR trace file some CTI ports going OOS but they always stay
registered with CCM and are associated with the proper JTAPI user. The
calls to these OOS CTI ports would ring the hunt pilot since they would
hit it as the CTI Route Point forwarding target (FW on Failure Ext/Int,
FW Busy Int/Ext, FW No Answer Int/Ext). No FW targets defined for the
CTI ports though.
What could be causing this issue? My impression is that this problem has
started since we upgraded CCM 3.3 to 4.1(3)sr3a and IPCCX 3.1 to 3.5(3)
but not sure.
Is anybody experiencing such a behaviour and would an upgrade to CCM
4.1(3)sr3c fix the problem as TAC suggested? TIA.
Rasim Duric
Network Analyst (CCS)
University of Guelph
Guelph, N1G 2W1, ON
519-824-4120x53146
rduric@uoguelph.ca
| |
| Mike Lay \(milay\) 2006-09-08, 1:12 am |
| Just a SWAG but did you update the JTAPIClient after the upgrade? Also
forward on failure is not the same as forward on not registered,
upcoming feature.
Mike
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Rasim Duric
Sent: Thursday, September 07, 2006 8:19 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] JTAPI subsystem in partial_service
Hi all,
JTAPI subsystem is flapping between in_service and partial_service on
one of our IPCCX applications. I've stopped and restarted the CRS engine
but it would run for a while and back in partial_service again. I can
see in the MIVR trace file some CTI ports going OOS but they always stay
registered with CCM and are associated with the proper JTAPI user. The
calls to these OOS CTI ports would ring the hunt pilot since they would
hit it as the CTI Route Point forwarding target (FW on Failure Ext/Int,
FW Busy Int/Ext, FW No Answer Int/Ext). No FW targets defined for the
CTI ports though.
What could be causing this issue? My impression is that this problem has
started since we upgraded CCM 3.3 to 4.1(3)sr3a and IPCCX 3.1 to 3.5(3)
but not sure.
Is anybody experiencing such a behaviour and would an upgrade to CCM
4.1(3)sr3c fix the problem as TAC suggested? TIA.
Rasim Duric
Network Analyst (CCS)
University of Guelph
Guelph, N1G 2W1, ON
519-824-4120x53146
rduric@uoguelph.ca
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Rasim Duric 2006-09-08, 1:12 am |
| Yes, I did update the JTAPI client after the upgrade.
Rasim Duric
Network Analyst (CCS)
University of Guelph
Guelph, N1G 2W1, ON
519-824-4120x53146
rduric@uoguelph.ca
-----Original Message-----
From: Mike Lay (milay) [mailto:milay@cisco.com]
Sent: Thursday, September 07, 2006 9:26 PM
To: Rasim Duric; cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] JTAPI subsystem in partial_service
Just a SWAG but did you update the JTAPIClient after the upgrade? Also
forward on failure is not the same as forward on not registered,
upcoming feature.
Mike
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Rasim Duric
Sent: Thursday, September 07, 2006 8:19 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] JTAPI subsystem in partial_service
Hi all,
JTAPI subsystem is flapping between in_service and partial_service on
one of our IPCCX applications. I've stopped and restarted the CRS engine
but it would run for a while and back in partial_service again. I can
see in the MIVR trace file some CTI ports going OOS but they always stay
registered with CCM and are associated with the proper JTAPI user. The
calls to these OOS CTI ports would ring the hunt pilot since they would
hit it as the CTI Route Point forwarding target (FW on Failure Ext/Int,
FW Busy Int/Ext, FW No Answer Int/Ext). No FW targets defined for the
CTI ports though.
What could be causing this issue? My impression is that this problem has
started since we upgraded CCM 3.3 to 4.1(3)sr3a and IPCCX 3.1 to 3.5(3)
but not sure.
Is anybody experiencing such a behaviour and would an upgrade to CCM
4.1(3)sr3c fix the problem as TAC suggested? TIA.
Rasim Duric
Network Analyst (CCS)
University of Guelph
Guelph, N1G 2W1, ON
519-824-4120x53146
rduric@uoguelph.ca
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|