I am using a call recording system with h.323 endpoints via multi-reg. This is going via AES DMCC. I need to start mixing in SIP stations and I'm being told multi reg is not supported. Is there a way to get single step working with these while keeping the current MR?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SIP Station Recording
- Thread starter trilogy8
- Start date
ZeroZeroOne
Systems Engineer
I'm guessing you're using Calabrio. I've only worked on this once but here's what I remember.
SIP Endpoints don't register directly to Communication Manager so CM can't fork the audio for recording. Calabrio only interfaces with CM so to get this working you need to build an equal number of H.323 stations to correspond with the SIP endpoints that will be recorded. Calabrio calls these H.323 stations "Virtual" so don't confuse these with Avaya's virtual station type. Calabrio uses these H.323 stations to do a "single step conference" to the SIP station in order to listen in on the call.
The basic steps are:
[ul]
[li]Create a "Virtual" H.323 station in CM for every SIP endpoint to be recorded[/li]
[li]Apply a DMCC license and a TSAPI license to every "Virtual" station[/li]
[li]All "Virtual" station names need to have the same prefix, such as "DMCC". After that can be anything: "DMCC 01", etc.[/li]
[li]In Calabrio, there needs to be a one-for-one correlation between the "Virtual" station and the SIP station to be recorded.[/li]
[/ul]
Follow the Avaya DevConnect configuration notes for more specific details. One little "gotcha" that isn't documented is that you must disable automatic exclusion on the COS for the stations.
I hope that helps.
SIP Endpoints don't register directly to Communication Manager so CM can't fork the audio for recording. Calabrio only interfaces with CM so to get this working you need to build an equal number of H.323 stations to correspond with the SIP endpoints that will be recorded. Calabrio calls these H.323 stations "Virtual" so don't confuse these with Avaya's virtual station type. Calabrio uses these H.323 stations to do a "single step conference" to the SIP station in order to listen in on the call.
The basic steps are:
[ul]
[li]Create a "Virtual" H.323 station in CM for every SIP endpoint to be recorded[/li]
[li]Apply a DMCC license and a TSAPI license to every "Virtual" station[/li]
[li]All "Virtual" station names need to have the same prefix, such as "DMCC". After that can be anything: "DMCC 01", etc.[/li]
[li]In Calabrio, there needs to be a one-for-one correlation between the "Virtual" station and the SIP station to be recorded.[/li]
[/ul]
Follow the Avaya DevConnect configuration notes for more specific details. One little "gotcha" that isn't documented is that you must disable automatic exclusion on the COS for the stations.
I hope that helps.
- Thread starter
- #3
ZeroZeroOne
Systems Engineer
If your system is similar then no. It will only look at the "DMCC" H.323 stations and use them to conference to the SIP stations.
- Status