If you SPAN the voice gateway port, you can record any call that goes through the voice gateway. But you might not be able to correlate the call with an IP phone number if that call was not originated from the IP phone (like MVA call).
Hi, Not sure if anyone else is facing this problem still, or whether an answer has been found?
I am facing the same issue for a customer who needs to voice-record all calls into and out of their network. There are multiple ISDN-30 circuits on multiple ISRs, and it is probable that a call that comes into the MVA system from PSTN will get routed straight back out to PSTN.
We are looking at RedBox voice recorder to do the recording of the audio, however the only way that this could pick up the RTP traffic is to use a network SPAN to intercept all network ports where the ISRs plug into the switch. The only problem here is that due to the need to record all conversations we are going to use DMS to record the phones (need to catch internal calls too) so if we SPAN the ISRs then we will get duplicate calls.
In the event that we SPAN the ISRs to catch the MVA calls we will face two issues:
a) We would need to filter the calls made to the MVA pilot number so that we avoice duplicate recordings as mentioned above.
b) We would not be guuaranteed to catch the traffic at all, because in my own understanding once the outbound leg of the call (MVA to PSTN) has been established then the RTP will be enfd-point to end-point right? In which case it would not leave the VLAN at best, and at worst it would not leave the ISR at all if it went back out the same ISDN trunk.
So, I'm stymied here. The only way I see this being possible is to route calls via alternative dedicated hardware for the MVA access, but this is not going to make customer happy.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.