Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

?
sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now
^
Forum Index » DMCC APIs » Devices that don't support RTP streams in RegisterTerminal?   XML
 
Author Message
nicklynch



Joined: 26/03/2013 12:28:40
Messages: 8
Offline

Are there any devices that I won't receive RTP streams for when using RegisterTerminalRequest (setting localMediaInfo in RegisterTerminalRequest registering in DEPENDENT mode and CLIENT media mode)? Will I always get streams regardless of protocol (SIP and so on)? Do all device types support it?

Judging from this, since what I'm doing is similar to call recording:
https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/support/faq/dmcc/index.gsp#7

it looks like analog phones won't work.

Though I'm not sure how ServiceObserve and SingleStepConference work for call recording.

This message was edited 1 time. Last update was at 11/01/2021 16:53:30

JohnBiggs



Joined: 20/06/2005 14:06:52
Messages: 815
Location: Thornton, CO
Offline

An RTP stream starting is not a guarantee. There are situations where it will not start due to various conditions.

It seems you are really asking what types of stations can I use multiple registrations per device form of call recording with. The answer to that is SIP and H.323 only.

Analog phones do work with SSC and SO recording, but not multiple registrations (MR) per device - The MR mechanism only works with SIP and H.323 devices. There are other station types that MR does not work with (MET, MFAT, and some others most are pretty old at this point in time).

I suggest working with this ebook, even though there is missing information in it related to SIP endpoints (you have the FAQ that fills in those details) and split stream recording; overall it is a better starting point.

https://www.devconnectprogram.com/site/global/products_resources/avaya_aura_application_enablement_services/educational_resources/ebooks/mastering_dmcc/index.gsp

Depending on how things are configured the application is either starting a RTP stream between CM and your application or between the far end device and your application. If you are just getting started building your application, or testing with the DMCC Dashboard, I suggest disabling point to point media (direct media) in the network region that you are using for the DMCC side IP endpoints. This is a simpler starting point than trying to handle direct media on a point to point call. Once a call becomes a 3 party call (either through SO or SSC) or via multiple registrations it will be anchored on CM and the RTP paths pretty stable.

[WWW]
MartinFlynn



Joined: 30/11/2009 05:00:18
Messages: 1751
Offline

Another brief point - for SIP phones, you must register the recording terminal in INDEPENDENT mode. INDEPENDENT mode is also OK for H.323.

Martin
 
 
Go to: