Can not call to assigned devices.

TheDriver · Post by **TheDriver** » Wed Jul 18, 2012 8:26 am

1. Brekeke Product Name and version:
Brekeke SIP Server , Version 3.0.6.3 Evaluation

2. Java version:
java version "1.7.0_05"

3. OS type and the version:
Microsoft Windows [Version 6.0.6002]

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

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
Pattern 4

6. Your problem:
We can not call any device which is connected to the server. The calls are declined. If we call from the clients via a other SIP server, it work perfectly. If we call from the other SIP - Server it is also impossible (Client not avalible)

All our clients are behind a firewall, the Server is with his only leg in the internet. For me it look like the call going to the Intranet IP addresses.

Contact: <sip:xxxxx@192.168.2.100:5060;transport=TCP>

How can we make sure that not the internal address is in use and the NAT is working?

On our sipxecs Server the contact string looks like this.
<sip:xxxxx@178.203.66.189:1562;transport=TCP;x-sipX-privcontact=192.168.2.100:5060;transport=TCP>
It does not matter how it looks like, the main thing is it works.

voipwell.com · Post by **voipwell.com** » Wed Jul 18, 2012 9:01 am

Are the clients that can not receive calls registered to the Brekeke SIP server and showing up as registered in the Brekeke registered tab ?

Tata · Post by **Tata** » Wed Jul 18, 2012 2:09 pm

What kind of SIP client are you using?

TheDriver · Post by **TheDriver** » Wed Jul 18, 2012 11:33 pm

The client is Onsight Expert and Onsight Device from Librestream.

Yes the devices are registered and they can call from Brekeke SIP-Server to Clients at other SIP - Servers.

janP · Post by **janP** » Thu Jul 19, 2012 12:29 am

if you use UDP instead of TCP at the client, does the same issue still happen?

TheDriver · Post by **TheDriver** » Fri Jul 20, 2012 12:13 am

The Solution is so easy.
After a restart of the server, the server show the registered clients. But after a restart they are not registered anymore.
After restart unregister the clients on the server and wait for the expiration time or reconnect them manually.

Thank you, for thinking about my stupid problem.

janP · Post by **janP** » Fri Jul 20, 2012 9:46 am

I don't think it is the solution... because you need to unregister the clients manually...

I suppose the cause of the problem is a TCP connection.
It seems the client doesn't reconnect TCP connection if the SIP Server disconnect it due to restart.

I'm using X-Lite. It can reconnect to the SIP Server over TCP automatically after I restart the SIP Server.

To avoid the problem, let you set UDP instead of TCP at the setting of the client.