According to very unambiguous directives from the pertinent RFCs, all routing should always be done based on the Request URI / INVITE request line. The To header should NEVER be used for routing (in >= 3261). It is a purely cosmetic commentary on the intended logical endpoint of the call. On 09/25/2012 05:27 PM, PE 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? Thanks
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Fax: +1-404-961-1892 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/