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.<br><br><div class="gmail_quote">On Mon, Jul 26, 2010 at 11:43 AM, Ryan Ratliff <span dir="ltr"><<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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.<br>
<font color="#888888"><br>
-Ryan<br>
</font><div><div></div><div class="h5"><br>
On Jul 26, 2010, at 1:32 PM, Tanner Ezell wrote:<br>
<br>
Well, the whole idea is that the call hits CUCM, hits the CTI Route<br>
Point which is owned by the JTAPI user and is controlled by UCCX (cti<br>
route point rings uccx, uccx does call control, transfers call to cti<br>
port, etc etc..).<br>
<br>
In theory, if the device is unregistered, CFUR will hit and take<br>
action but yes, I believe jtapi resync will overwrite those settings.<br>
<br>
I'm not at a UCCX box at the moment but check under the Trigger<br>
settings, if it was going to be there it would be near 'forward when<br>
busy'<br>
<br>
On Mon, Jul 26, 2010 at 12:37 PM, Fuermann, Jason <<a href="mailto:JBF005@shsu.edu">JBF005@shsu.edu</a>> wrote:<br>
> I think the problem you’re going to run into is if you data resync in UCCX.<br>
> It will overwrite the CFUR. As far as messing up UCCX, I’m not a developer<br>
> on it, but I highly doubt it.<br>
><br>
><br>
><br>
> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ryan Ratliff<br>
> Sent: Monday, July 26, 2010 10:31 AM<br>
> To: Steve G<br>
> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] Forward Unregistered CTI Ports with UCCX<br>
><br>
><br>
><br>
> If UCCX doesn't support setting the CFUR then I would like to think it would<br>
> ignore the field entirely. You can sure as heck test it, and I'd also be<br>
> asking your CSE what version of UCCX will support this field in CUCM and if<br>
> there is a bug to track it.<br>
><br>
><br>
><br>
> -Ryan<br>
><br>
><br>
><br>
> On Jul 26, 2010, at 11:22 AM, Steve G wrote:<br>
><br>
> We are on CUCM 7.1.3 and it is supported in this version of CUCM. However,<br>
> the TAC rep says it is not supported with UCCX and could cause Jtapi issues<br>
> is you are not supposed to configure anything on the CTI RP in CUCM, but do<br>
> it all on UCCX. Also, let's say we set the CTI RP to Forward Unregistered,<br>
> and then updated Jtapi. Wouldn't that clear out the forward unregistered<br>
> settings?<br>
><br>
> On Mon, Jul 26, 2010 at 8:12 AM, Tanner Ezell <<a href="mailto:tanner.ezell@gmail.com">tanner.ezell@gmail.com</a>><br>
> wrote:<br>
><br>
> It's not really a UCCX thing. What version of UCM? If you're version<br>
> supports forward on unregistered then that's all you can do..<br>
><br>
> On Mon, Jul 26, 2010 at 11:07 AM, Steve G <<a href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br>
>> Anyone??? going once, going twice...<br>
>><br>
>> On Fri, Jul 23, 2010 at 11:08 AM, Steve G <<a href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br>
>>><br>
>>> I meant CTI Route Points...not CTI Ports.<br>
>>><br>
>>> On Fri, Jul 23, 2010 at 11:05 AM, Steve G <<a href="mailto:smgustafson@gmail.com">smgustafson@gmail.com</a>> wrote:<br>
>>>><br>
>>>> In UCCX is there a way to configure a CTI Port to forward Unregistered<br>
>>>> to<br>
>>>> anther number...ie Hunt Pilot? We are running into an issue where CTI<br>
>>>> ports<br>
>>>> become unregistered and don't recover without manual intervention of<br>
>>>> updating the jtapi triggers in UCCX. We have a TAC rep saying that we<br>
>>>> can<br>
>>>> not modify the CTI ports in CUCM as that is not supported. So if UCCX<br>
>>>> has a<br>
>>>> jtapi problem we are dead in the water until we can login and<br>
>>>> update/resync<br>
>>>> the jtapi triggers.<br>
>>>> I am extremely new to UCCX so please forgive me if my terminology is<br>
>>>> wacky.<br>
>>>> Thanks,<br>
>>>> Steve<br>
>><br>
>><br>
><br>
>> _______________________________________________<br>
>> cisco-voip mailing list<br>
>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>><br>
>><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> cisco-voip mailing list<br>
> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>
><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>