[VoiceOps] Broadworks / Merging calls with Voipmon

[Richard Jobson]

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 call the Call Merging Algorithm to ensure all legs of any call flow are correlated into one view/message flow/ladder diagram. Since we introduced the product to North America in 2008, we’ve never been defeated on this.

 

The downside is, yes, it’s a commercial product. However, at the end of the day, if the objective is productivity and ROI, may the commercial product be right for the business?

 

Thanks for the opportunity to comment ☺

best regards

Richard 

 

From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of Anthony Orlando via VoiceOps <voiceops at voiceops.org>
Reply-To: Anthony Orlando <avorlando at yahoo.com>
Date: Monday, January 22, 2018 at 6:25 PM
To: "Zilk, David" <David.Zilk at cdk.com>
Cc: "voiceops at voiceops.org" <voiceops at voiceops.org>
Subject: 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 <David.Zilk at cdk.com> wrote:

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-bounces at voiceops.org] On Behalf Of Matthew Beckwell
Sent: Monday, January 22, 2018 1:02 PM
To: voiceops at voiceops.org
Subject: 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 for "related" calls. They will have have a common correlation header (but different call-id) like this:

 

X-BroadWorks-Correlation-Info:1126786:1

 

 

Then, in voipmonitor.conf you can set this parameter in the sniffer configuration to keep track of that header's value in the database:

 

matchheader = X-BroadWorks-Correlation-Info

 

 

VoIPmonitor won't merge them into a single SIP Diagram (at least not that I've found)-- but you should start to see the "related" call legs (with different Call-ID's but the same X-BroadWorks-Correlation-Info header) show up in the "Legs by header" tab when you're looking at a call's details in the VoIPmonitor GUI.

 

~Matthew

 

 

 

 

 

On Mon, Jan 22, 2018 at 2:36 PM, Matthew Crocker <matthew at corp.crocker.com> wrote:

                

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 -> Broadworks & Broadworks -> PSTN).     The Call-id on each call is different,  Broadworks generates a new SIP Dialog for the call.   If the customer has a hunt group there could be several INVITEs going out to multiple phones, all with different Call-Id.     Does anyone know of a way to get VoipMon to merge the calls into a single CDR/SIP Diagram?  Is there a way to configure Broadworks to embed the original Call-Id in the new INVITE (Parent-Call-Id Header)?

 

I’m running R20sp1

 

Thanks

 

-Matt 

 

-- 

Matthew Crocker

Crocker Communications, Inc.

President


_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

 

This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20180122/bb471de0/attachment-0001.html>