Cc: voiceops@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 Co
rg>
Reply-To: Anthony Orlando <avorla...@yahoo.com>
Date: Monday, January 22, 2018 at 6:25 PM
To: "Zilk, David" <david.z...@cdk.com>
Cc: "voiceops@voiceops.org" <voiceops@voiceops.org>
Subject: Re: [VoiceOps] Broadworks / Merging calls with Voipmon
Sounds
Sent: Monday, January 22, 2018 1:02 PM
> To: voiceops@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:
>
ker.com]
Sent: Monday, January 22, 2018 1:19 PM
To: Zilk, David <david.z...@cdk.com>; Matthew Beckwell <matth...@aitech.net>;
voiceops@voiceops.org
Subject: Re: [VoiceOps] Broadworks / Merging calls with Voipmon
Thanks David,
The Broadworks Correlation Id is enabled but the original INV
To: voiceops@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 = t
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
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
