Brekeke Server not repsonding to regisrtration requests

1. Brekeke Product Name and Version: V3.3.5.8 (Evaluation)

2. Java version:

3. OS type and the version: Windows XP

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

5. Your problem:


I have installed Brekeke Server ( Version 3.3.5.8 Evaluation) on Windows XP PC. The server is not responding to the registration messages sent form the User agent.

Please do let me know if any additional settings are required for the same.

Are you sure that REGISTER packets reached the SIP Server's PC?

Are there no response sent from the Brekeke SIP Server ? How about "401 Unauthorized"?

Are you sure there is no firewall running on the Windows XP?
Let you disable "Windows Firewall"

Are you sure that REGISTER's request-URI points the SIP Server's IP address or FQDN?

Which transport (UDP, TCP or TLS) does the SIP UA use for sending REGISTER?

Which UA product are you using?

Thanks for the inputs.
After disabling the firewall on the PC, Server is responding to registration requests.

If you want to keep using a firewall.
http://wiki.brekeke.com/wiki/Using-Brek ... a-firewall

Here's the needed details if you wish to use XP with Firewall : RECOMMENDED

BREKEKE WIKI LINK:
http://wiki.brekeke.com/wiki/Using-Brek ... a-firewall



Using Brekeke product with a firewall
If you are using a firewall in the same machine where Brekeke product is working on,

STEPS:

Add "java.exe" as a trusted program in the firewall settings.
Open the following ports at the firewall.
UDP/TCP:5060 (for SIP packet)
UDP:10000-10999 (for RTP packet in Brekeke SIP Server v2)
UDP:10000-29999 (for RTP packet in Brekeke SIP Server v3)
If you are using other ports for Brekeke SIP Server, please set them at the firewall.

Here's the protocol to use for simplicity.
XP FIREWALL SETUP:

*HOW TO OPEN/CLOSE RTP 10000-10999 PORT RANGE IN COMMAND PROMPT*

OPEN RTP PORT RANGE [Run in Command Prompt]
FOR /L %I IN (10000,1,10999) DO netsh firewall add portopening UDP %I "Brekeke Sip Server RTP"%I

CLOSE RTP PORT RANGE [Run in Command Prompt]
FOR /L %I IN (10000,1,10999) DO netsh firewall delete portopening UDP %I "Brekeke Sip Server RTP"%I

Two commands to open/close port range since XP Firewall doesn't allow this via GUI. Just replace the port range with first port where 10000 and last port where 10999. That's what I have setup since I'm on v2. May you set the port range with the v3 port range or your custom range if you are using dynamic ports.

Revert back if you face issues with setting this up.

Thanks,
Kent C.

Earlier after disabling the firewall V3.3.5.8 (Evaluation) , SIP server was working fine. But now again the same issue of SIP server not responding to registratiom messages has cropped up.

What other changes do you suggest for this version with firewall setting disabled ?
What could be the reason for the SIP server not responding now , since it was working fine earlier ?

Check the SIP Server's Interface address at the [Status] page.
Is it the IP address you sent REGISTER packet to?

Yes the IP address is the same.
Able to capture the Register requests on the same PC where SIP server is installed , but the Server is not responding to register messages.

One more interesting point I noticed is, the SIP server is repsonding to register requests from few User agents , but not for the other User agents.

Which SIP client product are you using?
Does the same issue happen even if you use Linphone or X-Lite?
Do you have any DialPlan rules which catch REGISTER?

We are using Vendor specific SIP User agents.
Haven't tried with Linphone or X-Lite yet.
We have dial plan rules set for Invite, nothing set for Register.


Note: The same user agents which were working earlier with the same number registered , is not working now.

One more point which I noticed now is, if the IP of the same UA is changed, than the SIP Server is responding to the registration requests sent by the UA.

Request for your reviews on the observed behaviour.

Are there any IP addresses listed in the [Block List]->[Blocked IP Address] page?

How about the IP address of the SIP client?

If so, the SIP Server blocked them.

The blocked list had the list of the IP's of the user agents for which we were facing the issue. Not sure what made them to get blocked.

Anyways, thanks Harold for your valuable inputs.

Forgot to mention, after clearing the blocked list its working fine.
Thanks once again

The BlockList may block your UA's IP addresses again.

so let you add them in the [Filtering Policy] as allowed IP address.
or tweak "Attempt Monitoring" at the [Settings] page.

http://wiki.brekeke.com/wiki/BlockList

Hi,

When the registration requests from User agent is coming with Domain name, the Brekeke SIP server is responding with 403 Forbidden message.
But when the registraion requests has domain name as IP address , the server is responding to the requests properly.

Note: Have entered the correct domain name in the Server.
Configuration-->SIP-->Realm(Ex:Domain name) tab.

Please let me know if any other setting is required for the server to respond to the domain names as URI.

Thanks,
Rakesh

I don't think you need to set Realm to use your domain.

I think the SIP server does not consider the domain as its own domain. Can you try adding the domain as an interface at [Configuration]?

Lucy

Thanks for the inputs. Its working now.

Hi,

The issue has again cropped up , even after adding the domain as an interface at [Configuration].

The registration requests from User agent is coming with Domain name, and the Brekeke SIP server is responding with 403 Forbidden message.

As mentioned earlier,when the registraion requests has domain name as IP address , the server is responding to the requests properly.

Please let me know if any other setting is required for the server to respond to the domain names as URI.

Thanks,
Rakesh

Is the SIP server located behind NAT?
Is the doman's IP address always same?
Does the issue happen if you use SIP Auth for REGISTER?

Explain the issue clearly.

Is the SIP server located behind NAT?

User Agent, SIP Server are in the same subnet. NAT is not required.

Is the doman's IP address always same? Yes

Does the issue happen if you use SIP Auth for REGISTER? Yes, Issue occurs even when the SIP Auth is On/Off.

Does the SIP Server use own global IP address?
Is the SIP Server's domain name associated with this IP address?

Does the SIP client UA use own global IP address?

What kind of SIP client UA are you using?
Does the same issue happen if you use another SIP client such as X-Lite?

Does the SIP Server use own global IP address?

This is a lab setup, which has localised subnet. SIP Server, UA's are within the same subnet. SIP Server has its own adress


Is the SIP Server's domain name associated with this IP address? Yes

Does the SIP client UA use own global IP address? Yes, UA has its own address with resons mentioned in earlier question.

What kind of SIP client UA are you using? ONT's which has SIP UA running on it.

Does the same issue happen if you use another SIP client such as X-Lite? Haven't tried.

Note: The same setup was working earlier , when the domain was added as an interface at [Configuration].

Why do you use a domain in SIP request?
Since SIP server and SIP UA are on the same LAN, you don't have to use a domain.

It seems domain is associated with a global IP not local IP.

We are using Domain name as part of testing the UA functionalities
This is a localised lab setup.

Does the same issue happen even if you specify the SIP Server's IP address instead of the domain name in the SIP UA's setting?

If you use the domain name in the SIP UA's setting, the SIP UA will send a REGISTER to the SIP Server through a router because the domain name points the router's global IP address.
Some router products can not handle this kind of routing.

The issue does not occur when IP address is mentioned.

As mentioned, this is a localised lab setup and there are no routers in between. Moreover the Reigster packets are reaching the SIP server, the issue is that the SIP Server is responding with 403 forbidden when the Register messages have domain name.

If REGISTER's request-URI indicates a domain name, the SIP Server tires to resolve its IP address with the DNS, and forwards the REGISTER to the resolved IP address.

You said that the domain name points a global IP address.
Therefore SIP server tires to forwards the REGISTER to the global IP address.

To prevent it, put the domain name at the [Interface address x] in the [Configuration]->[System] page.

Have tried with the domain name added as an interface at Configuration -->System page. But still getting 403 from SIP server.

Note: The same setup was working earlier.

Rakesh,

Are you using Auth for REGISTER?
Let you disable it for testing.
It is the "REGISTER=on/off" in the [Configuration]->[SIP] page.
You need to restart the SIP Server after you changed the setting.

Also make sure that the SIP server's PC can reach the DNS server.

Try nslookup for the domain name.
If nslookup can not resolve the domain, you need to set DNS settings correctly.