Reading along with this thread I had very similar reaction to Richard’s and felt the need to chime in here.
Telchemy’s SQmediator platform features similarly themed, customer configurable, call leg correlation logic to achieve the desired behavior…. which is generally to produce an a fully correlated end-to-end view of service quality. Like Palladion/EOM, Telchemy products are a commercial product. With that comes premium service, support and true carrier class scalability and like you all, we need to pay to keep the lights on. In addition, it’s Telchemy’s network of VQmon licensees (e.g. Polycom, Cisco, Yealink, Velocloud, Adtran) that Telchemy has built that enable platforms like these to gain these end-of-line quality insights using scalable, reliable, accurate and portable embedded analysis technology. And also like Richard – I appreciate the opportunity to comment. 😉 Questions / comments – happy to engage offline. -anthony From: VoiceOps [mailto:[email protected]] On Behalf Of Richard Jobson Sent: Tuesday, January 23, 2018 12:23 AM To: Anthony Orlando <[email protected]>; Zilk, David <[email protected]> Cc: [email protected] Subject: 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 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 <[email protected] <mailto:[email protected]> > on behalf of Anthony Orlando via VoiceOps <[email protected] <mailto:[email protected]> > Reply-To: Anthony Orlando <[email protected] <mailto:[email protected]> > Date: Monday, January 22, 2018 at 6:25 PM To: "Zilk, David" <[email protected] <mailto:[email protected]> > Cc: "[email protected] <mailto:[email protected]> " <[email protected] <mailto:[email protected]> > 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 <[email protected] <mailto:[email protected]> > 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:[email protected]] On Behalf Of Matthew Beckwell Sent: Monday, January 22, 2018 1:02 PM To: [email protected] <mailto:[email protected]> 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 <[email protected] <mailto:[email protected]> > 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 [email protected] <mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_voiceops&d=DwMFaQ&c=N13-TaG7c-EYAiUNohBk74oLRjUiBTwVm-KSnr4bPSc&r=VcRLyVxkyGds34uxiPM944HQvaWq-nynyZXfNpSfhOs&m=DPywImXDofS37q3FK-CGpyiEaDc6gi0BFORMDbPZPRg&s=9CuOLGl9u8cnWJw9-dABvCLAolSSIQUnP2QC3mnjiDk&e=> _____ 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 [email protected] <mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list [email protected] <mailto:[email protected]> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
