[VoiceOps] Broadsoft / 3CX SIP Trunks

[MICHAEL STERL]

we have this working without an edgemarc today for 3cx SIP Trunks. message me directly if you want more info. 
-Michael 




On Sep 25, 2012, at 3:43 PM, Zak Rupas <zak at simplesignal.com> wrote:

> I personally only ever got a 3cx working with an Edgemarc etc and would point the PBX at the Edgemarc etc
>  
> Thanks—
> Zak Rupas | Tier 3 Engineer
>  
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of PE
> Sent: Tuesday, September 25, 2012 3:28 PM
> To: voiceops at voiceops.org
> Subject: [VoiceOps] Broadsoft / 3CX SIP Trunks
>  
> 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?
>  
>  
> Thanks
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20120925/44014cb0/attachment.html>