[VoiceOps] Broadsoft / 3CX SIP Trunks

Zak Rupas zak at simplesignal.com
Tue Oct 2 10:34:15 EDT 2012

Are you using B2BUA or the old school EM trunking setup?


Zak Rupas | Tier 3 Engineer

[image: Description: Description: cid:image001.png at 01CBDE2D.5E1CC730]

Support Line 303-242-8616 Option 1


*From:* voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
*On Behalf Of *PE
*Sent:* Tuesday, October 02, 2012 8:21 AM
*To:* voiceops at voiceops.org
*Subject:* Re: [VoiceOps] Broadsoft / 3CX SIP Trunks


There's an Edgemarc in the middle and it is throwing a 404 because it
doesn't know what to do with the call. I think I am now sending what the
3CX wants but unfortunately a proxy is required for this implementation.

I knew it was too soon to declare victory. Back to scratching my head.

On Tue, Oct 2, 2012 at 8:33 AM, PE <peeip989 at gmail.com> wrote:

Thanks all. It is too early to declare victory but based on my tests it
looks like the Acme SIPConnect feature + Broadworks Alternate Trunk
Identity is going to be the solution.

On Tue, Sep 25, 2012 at 5:27 PM, PE <peeip989 at gmail.com> wrote:

Greetings fellow voipsters,

Have any of you done a SIP trunk integration between Broadsoft and 3CX? Or,
more specifically, I have a customer with a 3CX device (don't ask) that is
registered and I can send an INVITE, but their end denies the call (sends a
480 Temporarily Unavailable response) because it is having trouble routing
it to the destination in the 3CX system. This is because they are expecting
only the extension (4-digits), which I can send in the To: header but the
SIP URI is the full, registered User ID so that the SBC knows how to get it
to them. They are expecting only 4 digits in both the INVITE URI header and
the To header.

I know I can create a complex/convoluted header manipulation with the SBC
but it just feels like there must be another way.

Anyone know how to config the 3CX -- or even have a decent workaround -- to
support this?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121002/8cb8fee6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 32330 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20121002/8cb8fee6/attachment-0001.png>

More information about the VoiceOps mailing list