[cisco-voip] EngHouse CTI Route Points

[Anthony Holloway]

So, what I'm gathering from the responses (some to me directly), is that
CTI Route Points have for a long time, been able to terminate media, and I
was just unaware.  Given that I have never worked with the CTI protocol, I
guess this makes sense, as I was just deriving my understanding from UCCX
or CUACA type apps which use CTI Ports.  Got it.

On Thu, Mar 22, 2018 at 12:10 PM Brian Meade <bmeade90 at vt.edu> wrote:

> Probably just started with Cisco trying to sell licenses for ports.
> Similar to Unity Connection.  Unity Connection still even has virtual ports
> even with SIP.
>
> On Thu, Mar 22, 2018 at 11:03 AM, NateCCIE <nateccie at gmail.com> wrote:
>
>> Genesis call center does the same thing. I think it’s just a Cisco thing
>> for their apps with respect to CTI ports.
>>
>> Sent from my iPhone
>>
>> > On Mar 22, 2018, at 8:40 AM, Anthony Holloway <
>> avholloway+cisco-voip at gmail.com> wrote:
>> >
>> > Can someone please tell me how EngHouse can get away with using only
>> CTI Route Points and no CTI Ports, and yet, still terminate media?
>> >
>> > If they're aren't doing anything fancy, then why do so many, if not all
>> other, CTI applications, require both CTI Route Points and CTI Ports?
>> >
>> > Signed,
>> > Confused about CTI
>> > _______________________________________________
>> > 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/20180322/909e4b4f/attachment.html>