VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
January 2018
- 19 participants
- 29 messages
Troubles with Comcast
by matthew@corp.crocker.com
You probably need to work with your tandem provider to find out they are presenting the all circuits busy error
On Jan 23, 2018, at 5:37 PM, Mike Hammett <voiceops at ics-il.net<mailto:voiceops at ics-il.net>> wrote:
I apologize in advance for I am new to this level of voice.
I'm sending calls to the local tandem and I'm getting all circuits are busy when I call a Comcast number (or one ported to Comcast). Calls to those numbers work from other places (like my cell phone). Calls to other carriers on that tandem work.
How can I reach someone at Comcast to troubleshoot this?
We're using the Metaswitch platform.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
Jan. 23, 2018
Troubles with Comcast
by voiceops@ics-il.net
I apologize in advance for I am new to this level of voice.
I'm sending calls to the local tandem and I'm getting all circuits are busy when I call a Comcast number (or one ported to Comcast). Calls to those numbers work from other places (like my cell phone). Calls to other carriers on that tandem work.
How can I reach someone at Comcast to troubleshoot this?
We're using the Metaswitch platform.
-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
Midwest Internet Exchange
http://www.midwest-ix.com
Jan. 23, 2018
Broadworks / Merging calls with Voipmon
by anthony.caiozzo@telchemy.com
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:voiceops-bounces at voiceops.org] On Behalf Of Richard Jobson
Sent: Tuesday, January 23, 2018 12:23 AM
To: Anthony Orlando <avorlando at yahoo.com>; Zilk, David <David.Zilk at cdk.com>
Cc: voiceops at voiceops.org
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 <voiceops-bounces at voiceops.org <mailto:voiceops-bounces at voiceops.org> > on behalf of Anthony Orlando via VoiceOps <voiceops at voiceops.org <mailto:voiceops at voiceops.org> >
Reply-To: Anthony Orlando <avorlando at yahoo.com <mailto:avorlando at yahoo.com> >
Date: Monday, January 22, 2018 at 6:25 PM
To: "Zilk, David" <David.Zilk at cdk.com <mailto:David.Zilk at cdk.com> >
Cc: "voiceops at voiceops.org <mailto:voiceops at voiceops.org> " <voiceops at voiceops.org <mailto: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 <mailto: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 <mailto: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 <mailto: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 <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
_____
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 <mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 23, 2018
Broadworks / Merging calls with Voipmon
by richard@teraquant.com
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
Jan. 23, 2018
Broadworks / Merging calls with Voipmon
by avorlando@yahoo.com
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
Jan. 23, 2018
Broadworks / Merging calls with Voipmon
by matthew@corp.crocker.com
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 Communications, Inc.
President
From: "Zilk, David" <David.Zilk at cdk.com>
Date: Monday, January 22, 2018 at 4:21 PM
To: Matthew Crocker <matthew at corp.crocker.com>, Matthew Beckwell <matthewb at aitech.net>, "voiceops at voiceops.org" <voiceops at voiceops.org>
Subject: RE: [VoiceOps] Broadworks / Merging calls with Voipmon
In my experience the leg gets identified by the correlation ID that broadworks adds to the responses associated with the original INVITE. VoIPmonitor will use that to complete the correlation.
From: Matthew Crocker [mailto:matthew at corp.crocker.com]
Sent: Monday, January 22, 2018 1:19 PM
To: Zilk, David <David.Zilk at cdk.com>; Matthew Beckwell <matthewb at aitech.net>; voiceops at voiceops.org
Subject: Re: [VoiceOps] Broadworks / Merging calls with Voipmon
Thanks David,
The Broadworks Correlation Id is enabled but the original INVITE from the end-user (Polycom) doesn?t have it so voipmon isn?t picking it up (which make sense). I was hoping there was a way for Broadworks to pull something out of the original invite for tracking.
Selecting both calls in voipmon and merging works, just doesn?t merge auto-magically
-Matt
--
Matthew Crocker
Crocker Communications, Inc.
President
From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of "Zilk, David" <David.Zilk at cdk.com<mailto:David.Zilk at cdk.com>>
Date: Monday, January 22, 2018 at 4:11 PM
To: Matthew Beckwell <matthewb at aitech.net<mailto:matthewb at aitech.net>>, "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Subject: 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-bounces at voiceops.org] On Behalf Of Matthew Beckwell
Sent: Monday, January 22, 2018 1:02 PM
To: voiceops at voiceops.org<mailto: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<mailto: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<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
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.
Jan. 22, 2018
Broadworks / Merging calls with Voipmon
by David.Zilk@cdk.com
In my experience the leg gets identified by the correlation ID that broadworks adds to the responses associated with the original INVITE. VoIPmonitor will use that to complete the correlation.
From: Matthew Crocker [mailto:matthew at corp.crocker.com]
Sent: Monday, January 22, 2018 1:19 PM
To: Zilk, David <David.Zilk at cdk.com>; Matthew Beckwell <matthewb at aitech.net>; voiceops at voiceops.org
Subject: Re: [VoiceOps] Broadworks / Merging calls with Voipmon
Thanks David,
The Broadworks Correlation Id is enabled but the original INVITE from the end-user (Polycom) doesn?t have it so voipmon isn?t picking it up (which make sense). I was hoping there was a way for Broadworks to pull something out of the original invite for tracking.
Selecting both calls in voipmon and merging works, just doesn?t merge auto-magically
-Matt
--
Matthew Crocker
Crocker Communications, Inc.
President
From: VoiceOps <voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>> on behalf of "Zilk, David" <David.Zilk at cdk.com<mailto:David.Zilk at cdk.com>>
Date: Monday, January 22, 2018 at 4:11 PM
To: Matthew Beckwell <matthewb at aitech.net<mailto:matthewb at aitech.net>>, "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Subject: 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-bounces at voiceops.org] On Behalf Of Matthew Beckwell
Sent: Monday, January 22, 2018 1:02 PM
To: voiceops at voiceops.org<mailto: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<mailto: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<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
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.
Jan. 22, 2018
Broadworks / Merging calls with Voipmon
by matthew@corp.crocker.com
Thanks David,
The Broadworks Correlation Id is enabled but the original INVITE from the end-user (Polycom) doesn?t have it so voipmon isn?t picking it up (which make sense). I was hoping there was a way for Broadworks to pull something out of the original invite for tracking.
Selecting both calls in voipmon and merging works, just doesn?t merge auto-magically
-Matt
--
Matthew Crocker
Crocker Communications, Inc.
President
From: VoiceOps <voiceops-bounces at voiceops.org> on behalf of "Zilk, David" <David.Zilk at cdk.com>
Date: Monday, January 22, 2018 at 4:11 PM
To: Matthew Beckwell <matthewb at aitech.net>, "voiceops at voiceops.org" <voiceops at voiceops.org>
Subject: 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-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<mailto: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<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
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.
Jan. 22, 2018
Broadworks / Merging calls with Voipmon
by abalashov@evaristesys.com
If the intermediate UAs can be configured to pass through arbitrary X-
headers, the necessary intelligence can be spliced in in a very
low-friction / high-performance / high-reliability way with a Kamailio
SIP proxy.
Bolting this sort of functionality on from the side because the
proprietary platforms just can't be configured to do it is a very common
project for us, and doesn't cost much.
I'm not saying it's an obvious slam dunk; there's a number of modalities
to explore here, not the least of which is the BW -> phone scenario.
Still, food for thought.
--
Alex Balashov | Principal | Evariste Systems LLC
Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/
Jan. 22, 2018
Broadworks / Merging calls with Voipmon
by David.Zilk@cdk.com
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<mailto: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<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailma…>
----------------------------------------------------------------------
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.
Jan. 22, 2018