[cisco-voip] EngHouse CTI Route Points

[Stephen Welsh]

The Cisco JTAPI API includes the concept of a MediaTerminal that can be registered as either a CTI Port or CTI RoutePoint, been that way for a while I believe.

All that really means is the negotiate the RTP TX/RX IPAddress and UDP Port when a call arrives or is placed to/from the MediaTerminal you register

The overview of the MediaTerminal are on this page:

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/jtapi_dev/9_1_1/jtapidevguide/featsupported.html

You still need a ‘media engine’ to send/receive RTP streams, the Cisco JTAPI library does not have any media termination, just the ability to control/signal CTI Port/Route Point RTP streams.

I’ve successfully tested using a CTIRoute Point instead of a SIP Trunk for call recording, pretty handy for ourselves when we have a solid JTAPI codebase but no SIP stack (as yet). I’m sure there are other situations when a CTI RoutePoint has been used instead of a SIP Trunk.

Kind Regards

Stephen Welsh
CTO
UnifiedFX



On 22 Mar 2018, at 20:46, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:


This is an interesting thread. You talk about terminating media. But, we know that an unregistered CTI routepoint will forward calls appropriately. That’s what we use for phantom extensions and forwarding calls to call trees in Connection.

Are these apps you are referring to using this method to route calls to a SIP trunk for example? Or are they actually registered?

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

<image001.png>

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Thursday, March 22, 2018 1:45 PM
To: Brian Meade <bmeade90 at vt.edu<mailto:bmeade90 at vt.edu>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] EngHouse CTI Route Points

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<mailto: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<mailto: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<mailto:avholloway%2Bcisco-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<mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto: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/ad3919a5/attachment.html>