Re: [VoiceOps] Broadworks / Merging calls with Voipmon

Indeed Anthony. Apologies, if I fail to restraint myself from chipping in here…. ;) As long as there is something to correlate on (even as far down as SDP) [which there always is] Palladion/EOM/Oracle Communications Operations Monitor has always supported the functionality to tweak what we

Re: [VoiceOps] Broadworks / Merging calls with Voipmon

Sounds like a crappy way of correlating a call especially if u have several b2bua’s. Several commercial products out there that have multiple ways of correlating a call. Sent from my iPhone > On Jan 22, 2018, at 4:10 PM, Zilk, David wrote: > > If you click on the

Re: [VoiceOps] Broadworks / Merging calls with Voipmon

Well, would you look at that. The 183 Session Progress from Broadworks -> Polycom has the header. VoipMon should be merging them together. I’ll dig deeper but I think it is an issue with the voipmon config at this point. Thanks for the help ☺ -Matt -- Matthew Crocker Crocker

Re: [VoiceOps] Broadworks / Merging calls with Voipmon

If you click on the ‘Merge’ dropdown while displaying the Legs by Header, you can select ‘SIP History’ to display the SIP Ladder diagram of all the legs together. David From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Matthew Beckwell Sent: Monday, January 22, 2018 1:02 PM

Re: [VoiceOps] Broadworks / Merging calls with Voipmon

Hi Matt, Here's what I've done to get close to what you're looking for... In the BroadWorks Application Server, set these parameters: AS_CLI/Interface/SIP> *sendCallCorrelationIDAccess = true* *sendCallCorrelationIDNetwork = true* Once you do that, you'll see BroadWorks start to add a header

[VoiceOps] Broadworks / Merging calls with Voipmon

Hello, We currently have Broadworks/AcmePacket handling calls to/from customers. We have a couple VoipMon sensors running watching all traffic inside/outside our SBC. Currently calls are presented in VoipMon as two different calls (PSTN -> Broadworks & Broadworks -> Polycom) or (Polycom