Call recording Jabber to AQM over DA vpn

[lowfell]

Trying to enable call recording for homeworkers using Jabber through Microsoft DA vpn. now i thought this may be a not supported issue, but we have manged to get about for users working. If you look at my screenshot, the FIRST one is Working & the second one isn't event though they are setup the same

Expressway is 12.5.6

AQM is 11.5.1.979

This one is working.

T

This one is not working

You might say do wiresahrk, but it would be difficult to do as these are busy homeworkers and in any case they are using a vpn, how could we do that?

Anyone help please?

[Konstantin Vaksin]

In Call Recording, you have to be sure, that there is RTP path to the recording server established from the phone.

If that would come to the Recording Server, your call will be recorded. So if you can’t make sniffer captures from the phone, do that from Recording Server.
You might want to figure out IP Addresses of Jabber devices

Kostia

[lowfell]

Thanks, i'll get my customer to try this and we'll see what happens

[Graham Old]

What does the QM show for failing calls.

Login to the QM web page and select "Recording Monitoring"

If you think it is the VPN/RTP stream you could setup for gateway prefered, this will only record external calls.

Graham

[lowfell]

The recording monitoring says ‘recordingMonitorCallState.MacNotAssociated’ for the ones that aren’t recording and the csfs are set up in VOIP devices.

Any ideas?

[bill.king1]

Are you using these agents with both Expressway as well as Finesse? If so, keep in mind that there are restrictions with this configuration.

[lowfell]

They are using Expressway with Jabber, not Finesse doe the same restrictions apply?

[bill.king1]

There are more if you are using them both together, but if you look here, there are some restrictions as far as recording, etc.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/exwy_b_mra-expressway-deployment-guide/exwy_b_mra-expressway-deployment-guide_chapter_01.html

[lowfell]

hello all. We believe the traffic is getting as far as the recording server as we see an error associted with the user who isn't working as 

"recordingMonitorCallstate.macNotassociated"

This user is setup exactly the same as the others, so surely if the others work this one should?