James, Thanks for your help. I have had email confirmation from the Brekeke Development team that they are non-compliant to 3GPP 24.229.

James,

Yes we diid and as I suspected there was no change.

James, Are you certain? Do you work for Brekeke? Is this what the Server is looking for because if it is it does not comply with 3GPP 24.229. According to 3GPP the nonce must be empty when sent in the initial REGISTER. 5.1.1.2.3 Initial registration using SIP digest without TLS On sending a REGISTER ...

James.

Thanks Will do. However, I fail to see why this would prevent the Server from sending a 401 when we spcifiy the realm on the server.

Davi,

According to 3GPP 24.229 Clause 5.1.1.2.1 the inital Register must contain an authorization header. This is how a UA specifies that does not want to register with a proxy

Dave,

I deleted the header value from the example

Hope,

Thanks for your response. We have tried both variables in the user authentication field and get 403 in both cases

We are having a similar problem. We have configured the server to have a realm value manually set in the user authentication and/or the domain. We also turned off auth-From and To in both user authentication and domain. When this is the case we get a 403 response. The value of realm set in the ...

1. Brekeke Product Name and version: 2. Java version: 3. OS type and the version: 4. UA (phone), gateway or other hardware/software involved: 5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/networkpatterns.html : 6. Your problem: This may be a bit of a dim question but I ...