Stream Manager Recorder with Cisco Tserver 7.6.x

Hello,

I am facing problem to make work a conversation record in our environnment based on Tserver 7.6.xx for CUCM and Stream Manager 7.6.X . The Anouncement Record work well using a Strategy with User Anouncement Object.

I based my configuration on doing the following :

Call recording is enabled on DNs using the record option.
Call recording is enabled by specifying extension record in RequestRouteCall.
The routing strategy may determine whether or not call recording is needed.
To invoke this feature, the following key-value pairs should be attached to the
Attribute Extensions of the RequestRouteCall request:
Key: record
Value: destination
When the extension is set to destination, the recording will be initiated on the routing destination DN (agent) and will continue while the agent stays in the call

We need to make it work as soon as possible we are having delay problem.
My Best Regards,

TServer and Stream Manager Traces are enclosed in this Post!

Hello,

Your issue is caused by wrong configuration. Based on provided logs both T-Server and Stream Manager runs on the host SIEGGENP. Such configuration is possible but you have to specify unique TCP/IP ports used by the applications. But I see in your configuration that T-Server’s option “sm-port” is set to 5061 and the same port is used by SIP interface of Stream Manager. That’s wrong as option “sm-port” should specify unique TCP/IP port that T-Server opens for listening and Stream Manager connects to this port.

R.

Hi René,

I am pleased to read your answer to my issue. Does it mean that i need to specify another port for Stream Manager for Tserver (sm-port) ?

Best Regards,

Yup, SM needs two ports, one for TLib and the other for SIP

THK THK

Guys,

i have change the config but having no record - the stream manager traces shows a TSERVER instruction to destroy LEG ???

08:51:18.828 Std 04503 Connected to TServer_CCM(fd:264) at SIEGGENP:6061
08:51:18.828 Trc 04542 Sent to TServer_CCM(fd:264) ← HELLO(tt=0,id=0,ver=1.6,addr=150.150.4.249,name=Stream Manager) ref=0
08:51:18.828 Trc 04541 Got from TServer_CCM(fd:264) → HELLO_ACK(id=1,err=0) ref=0
08:51:18.828 Trc 04541 Got from TServer_CCM(fd:264) → READY
UDP[240] port 8000 closed at 08:51:35.437
08:52:53.187 Trc 04541 Got from TServer_CCM(fd:264) → CREATE_LEG(leg=10,type=0,conf_id=0) ref=5
RTPLeg[10] created RTP:8002(fd=240), RTCP:8003(fd=280)
08:52:53.187 Trc 04542 Sent to TServer_CCM(fd:264) ← CREATE_LEG_ACK(sm_id=1,leg=10,rtp:8002,rtcp:8003,err=0) ref=5
08:52:53.250 Trc 04541 Got from TServer_CCM(fd:264) → DESTROY_LEG(leg=10) ref=7
RTP(leg=10):8002/8003 completed (remote 0.0.0.0:0)
RX=0/0+0(err=0) rtcp=0(err=0) ssrc[0] jitter=0(max=0)
TX=0/0+0(err=0) rtcp=0(err=0) seq=0
total duration: 0.1 sec
(no active legs)
08:52:53.265 Trc 04542 Sent to TServer_CCM(fd:264) ← DESTROY_LEG_ACK(id=1,err=0) ref=7
UDP[240] port 8002 closed at 08:53:13.281

Thanks for your assistance again !

Rgds,

Babacar,

Could you post here full logs of T-Server and Stream Manager.

R.

PS. I saw in your previous log that call was established just for 1 seconds on agent’s extension. Could you please leave it established for longer time like 30 secs?

René,

You have the Full log attached to my previous post. I have etablished the call for a minute but the result is the same, SM notify only 1 sec.

let me know if you need more traces !
Rgds,

Sorry,

I’ve overlooked attached files. I’m a bit confused by call flow I see in your log. Could you explain me what the DNs 8895,9921 and 1570 are (Routing Point? Extension?)?

R.

René,

The 1570 is a caller / 9921 the routing Point for the strategy and 8895 is an extension which is not used in my strategy -

the 1570 call the 9921 and the call is routed to the 6801

hope this will help !

Rgds,

Hi,

I see that SM leg is created when call arrives to Routing Point 9921 and destroyed once the call is routed to an agent. Have you correctly enabled recording on agent’s DN and not on RP?

R.

Hi, can you clarify - in you case recording announcement from strategy is work fine. but then you try make the regular call recording it’s not working? Is it true?

Well, actually , if i don’t miss something, you version of T-Server does not support regular call recording. Version 7.6 only support recording announcement from strategy. You can configure CUCM to use SM as independent, not controlled by Genesys T-Server, SIP recording services or you should upgrade you T-Server to version 8.x

WBR Thaler

Ouu

Thanks for your post Timur! I’ve completely overlooked T-Server version and automatically assumed release 8.0… My fault.

R.

Hi Timur,

I am afraid that you are right. The recording annoucement work realy find! We would like to make the regular record using ExtensionAttach[‘record’,‘destination’] function.

Is it possible to put TServer 8.0 on Framework 7.6 - sorry buit i did not yet read the 7.8 RN to know. ? if this is not possible could you give more details (procedure) about the CUCM integration with SM. It may be the Solution.

My Best Regards,

Babacar,

you can use the T-Server version 8.x at Framework 7.x without any problem, but of course in this case you mast got the updated licenses file. Genesys have WP about configuration process, but it CUCM version dependence and sayd about version 4.x-5.x. For CUCM version 6.x-7.x it not to simple but if you have Cisco enginer with strong knowledge of CUCM it’s not a problem.

Use SM as independend SIP-recorder is also simple - jast take the Cisco guide , try google it if you have’t ones. However, if you need same key points or more clarify - which version of CUCM you have?

WBR Thaler

Call Manager Version 4.2(1)

Rgds,

Hi babacar!

Did you have access to Genesys support site ?

hello Timur,

yep they send me today the Tserver V8.0 which is compatible with FR 7.x and i have installed it but my problem still here.

please have a look on the attached traces. I am blocked !

Rgds,

What is the ConnID of your call test?

Ermm…I see something very funny here in your strategy:

ExtensionsAttach[‘record’,‘destination’]

From documentation:

2) It is also possible to enable recording using extensions in routing strategy. If inbound call goes to the routing point, in the routing strategy it is possible to specify extension “record=destination”. “destination” in this scenario means the DN where call is routed - in most cases that would be the Agent DN.

But I think you may wanna try this one better:

1) Just specify option “record=true” on the Agent DN. This will instruct SIP Server to record all the calls which comes from / goes to this DN.