02-12-2021 08:59 AM
YP
Hi, I have a bit of an issue due to Cisco's limited recording options! We have CUCM with 8800 phones & CUBE HA for PSTN access.
Requirement is to capture point-to-point, SNR and all forwarded calls to PSTN for given users. I don't think there is any single solution Cisco provides that meets these requirements with CUBE HA. Only setup that comes close is XMF based but it does not support CUBE HA so I have managed to get Phone BiB with SIPREC working to meet all of my requirements but running in to an issue where forwarded calls ending up with a prefix in front of dialled number.
On the CUBE I have two incoming dial-peers (XX & YY) from CUCM where one is standard (XX) that handles calls in/out without any issue. I have added an additional Dial-peer (YY) with incoming destination number match so it gets invoked for all of my SNR & FWD calls with a prefix and triggers SIPREC forking for just these media streams to the recorder.
All works great but now the recorder gets dialed number with the prefix, is there a way to remove this prefix before SIPREC gets invoked by a Dial-peer YY or even before calls hits this YY dial-peer OR does anyone know another way to achieve similar results?
If CUBE supported multiple SIP ports then I could just have separate trunk from CUCM for this to the CUBE and life could be simple!
Solved! Go to Solution.
02-12-2021 09:36 AM
Can you not use voice translation rules/profile in the inbound direction on dial peer YY to modify the number to drop the prefix? If this does not work you’ll likely need to look at using a SIP profile to manipulate the content of the SDP in the inbound direction of the dial peer.
02-12-2021 09:36 AM
Can you not use voice translation rules/profile in the inbound direction on dial peer YY to modify the number to drop the prefix? If this does not work you’ll likely need to look at using a SIP profile to manipulate the content of the SDP in the inbound direction of the dial peer.
02-12-2021 10:05 AM
If all else fails you could create multiple trunks in CM to the gateway if you use TLS for the second trunk as that would be port 5061 and the trunk you likely have now use port 5060 on UDP or TCP.
02-14-2021 12:33 PM
Thanks Roger, yes used the voice translation-profile to remove the prefix from YY and all working great!
I did this before posting but forgot to fix the called number in VFC recorder profile so when I was testing VFC would not accept number without prefix so thought SIPREC was not working but finally removed it from the recorder and all started to work.
By the way using 5061 was my jail break card!
thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide