[cisco-voip] Forward Unregistered CTI Ports with UCCX
Steve G
smgustafson at gmail.com
Mon Jul 26 15:27:37 EDT 2010
Thanks all. I'm going to test in a lab and see what the behavior is. It is
not an option in UCCX, so hopefully it would ignore it on a jtapi resync.
On Mon, Jul 26, 2010 at 11:43 AM, Ryan Ratliff <rratliff at cisco.com> wrote:
> Agreed, depending on how the AXL stuff works it will either overwrite the
> setting OR ignore it completely. IMO if they don't let you set it via the
> UCCX admin then the AXL sync should ignore that setting. Either way I'd
> test it with a dummy RP before deploying live.
>
> -Ryan
>
> On Jul 26, 2010, at 1:32 PM, Tanner Ezell wrote:
>
> Well, the whole idea is that the call hits CUCM, hits the CTI Route
> Point which is owned by the JTAPI user and is controlled by UCCX (cti
> route point rings uccx, uccx does call control, transfers call to cti
> port, etc etc..).
>
> In theory, if the device is unregistered, CFUR will hit and take
> action but yes, I believe jtapi resync will overwrite those settings.
>
> I'm not at a UCCX box at the moment but check under the Trigger
> settings, if it was going to be there it would be near 'forward when
> busy'
>
> On Mon, Jul 26, 2010 at 12:37 PM, Fuermann, Jason <JBF005 at shsu.edu> wrote:
> > I think the problem you’re going to run into is if you data resync in
> UCCX.
> > It will overwrite the CFUR. As far as messing up UCCX, I’m not a
> developer
> > on it, but I highly doubt it.
> >
> >
> >
> > From: cisco-voip-bounces at puck.nether.net
> > [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
> > Sent: Monday, July 26, 2010 10:31 AM
> > To: Steve G
> > Cc: cisco-voip at puck.nether.net
> > Subject: Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX
> >
> >
> >
> > If UCCX doesn't support setting the CFUR then I would like to think it
> would
> > ignore the field entirely. You can sure as heck test it, and I'd also be
> > asking your CSE what version of UCCX will support this field in CUCM and
> if
> > there is a bug to track it.
> >
> >
> >
> > -Ryan
> >
> >
> >
> > On Jul 26, 2010, at 11:22 AM, Steve G wrote:
> >
> > We are on CUCM 7.1.3 and it is supported in this version of CUCM.
> However,
> > the TAC rep says it is not supported with UCCX and could cause Jtapi
> issues
> > is you are not supposed to configure anything on the CTI RP in CUCM, but
> do
> > it all on UCCX. Also, let's say we set the CTI RP to Forward
> Unregistered,
> > and then updated Jtapi. Wouldn't that clear out the forward unregistered
> > settings?
> >
> > On Mon, Jul 26, 2010 at 8:12 AM, Tanner Ezell <tanner.ezell at gmail.com>
> > wrote:
> >
> > It's not really a UCCX thing. What version of UCM? If you're version
> > supports forward on unregistered then that's all you can do..
> >
> > On Mon, Jul 26, 2010 at 11:07 AM, Steve G <smgustafson at gmail.com> wrote:
> >> Anyone??? going once, going twice...
> >>
> >> On Fri, Jul 23, 2010 at 11:08 AM, Steve G <smgustafson at gmail.com>
> wrote:
> >>>
> >>> I meant CTI Route Points...not CTI Ports.
> >>>
> >>> On Fri, Jul 23, 2010 at 11:05 AM, Steve G <smgustafson at gmail.com>
> wrote:
> >>>>
> >>>> In UCCX is there a way to configure a CTI Port to forward Unregistered
> >>>> to
> >>>> anther number...ie Hunt Pilot? We are running into an issue where CTI
> >>>> ports
> >>>> become unregistered and don't recover without manual intervention of
> >>>> updating the jtapi triggers in UCCX. We have a TAC rep saying that we
> >>>> can
> >>>> not modify the CTI ports in CUCM as that is not supported. So if UCCX
> >>>> has a
> >>>> jtapi problem we are dead in the water until we can login and
> >>>> update/resync
> >>>> the jtapi triggers.
> >>>> I am extremely new to UCCX so please forgive me if my terminology is
> >>>> wacky.
> >>>> Thanks,
> >>>> Steve
> >>
> >>
> >
> >> _______________________________________________
> >> cisco-voip mailing list
> >> cisco-voip at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/cisco-voip
> >>
> >>
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100726/009bf2f1/attachment.html>
More information about the cisco-voip
mailing list