Routing Calls to System - Requires Username Authentication

[JRayfield]

1. Brekeke Product Name and Version:

SIP Server 3.5.2.8

2. Java version:

Version 7

3. OS type and the version:

Windows 7 Pro

4. UA (phone), gateway or other hardware/software involved:

3CX IP PBX

5. Your problem:

I need to set up BSS so that 3CX IP PBX's can register with it and then calls can be routed to a VoIP service provider that requires username/password authentication.

Setting up BSS for a 3CX IP PBX to register with it is easy. And I can easily route calls from the 3CX IP PBX to a VoIP service provider that only uses IP authentication.

But, I don't understand how to set up BSS so that it can register with the VoIP service provider, so that calls from the 3CX system can be routed to the VoIP service provider.

I would appreciate any help.

John

[snuyzm]

Use Upper Registration or Thru Registration at Brekeke SIP Server.

If you can paste your 3CX's register settings here, I can advice.

[JRayfield]

I've got Thru Registration working.

But when I set up Upper Registration, I can get the 3CX PBX to register with both my BSS and the VoIP service provider, but I can't get a number to be dialed 'through' to the VoIP service provider.

I think the problem now is I need a Dial Plan Rule to 'forward' the dialed number from 3CX, 'through' my BSS, to the VoIP service provider.

I've set up Dial Plans for dialing 'through' BSS when not using Upper Registration, but a similar dial plan rule doesn't work.

I guess I"m really stumped here.

John

[JRayfield]

Here's more of what's happening.

1. 3CX is sending the INVITE message to BSS.

2. BSS is sending the INVITE message to the VoIP service provider.

3. The VoIP service provider is sending back a "407 Proxy Authentication Required".

4. The whole process repeats.

I know that 3CX will Authenticate INVITE's. But in this case, it appears that BSS is not sending the INVITE with Authentication to the VoIP service provider.

I disabled INVITE Authentication 'off' in the BSS Configuration, but I don't like leaving that off, for security reasons.

Suggestions?

John

[snuyzm]

John, you don't have to use both Upper/Thru Registration.
If there are multiple VoIP service providers you want to connect concurrently, Thru Registration is better because you can not define multiple destinations in Upper Registration's setting.

But if a SIP client (such as 3CX) can not define an inbound proxy server and registrar separately, Upper Registration should be used.

[snuyzm]

It seems 3CX sends new INVITE to 407 returned from the SIP server but it doesn't send another new INVITE to 407 returned from the VoIP service provider (and forwarded from the SIP server.)

Some SIP clients can handle multiple 407 challenges within same call.


If you disable Auth at the Brekeke SIP Server, you will make it works but I know you can not disable it.


Try this rule. It disables auth only if INVITE is sent from authorized IP address with REGISTER.

For example:

Matching Patterns

$request = ^INVITE $registeredsender = true

Deploy Patterns

$auth = off $continue = true