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