How to monitor end points with XYMON via Brekeke
Moderator: Brekeke Support Team
How to monitor end points with XYMON via Brekeke
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/ ... terns.html :
6. Your problem:
We have various remote Quintum Tenor endpoints with dynamic IP internet service.
All Quintums register every 300 seconds to our Brekeke SIP Server.
How can we use the IP address information reflected on the SIP Server to monitor our Quintum network via XYMON or any other network monitoring application?
Thanks
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/ ... terns.html :
6. Your problem:
We have various remote Quintum Tenor endpoints with dynamic IP internet service.
All Quintums register every 300 seconds to our Brekeke SIP Server.
How can we use the IP address information reflected on the SIP Server to monitor our Quintum network via XYMON or any other network monitoring application?
Thanks
In the past we used Xymon to monitor our remote Quintum network via DNS as all of our remote Quintums have Dynamic IP internet service. Now that we have incorporated the Brekeke SIP server into our network we can no longer use DNS.
Do you know of a network monitoring application (perhaps similar to Xymon) that will work by using the IP's posted on the Registered Clients page?
Xymon is a system for monitoring of hosts and networks, inspired by the Big Brother system. It provides real-time monitoring, an easy web-interface, historical data, availability reports and performance graphs. Xymon was previously known as "Hobbit".
http://sourceforge.net/projects/hobbitmon/
Thanking you in advance.
Do you know of a network monitoring application (perhaps similar to Xymon) that will work by using the IP's posted on the Registered Clients page?
Xymon is a system for monitoring of hosts and networks, inspired by the Big Brother system. It provides real-time monitoring, an easy web-interface, historical data, availability reports and performance graphs. Xymon was previously known as "Hobbit".
http://sourceforge.net/projects/hobbitmon/
Thanking you in advance.
Ok. I understood.
Which edition of SIP Server are you using?
If you are using Advanced Edition, you can use Failure Notification feature for monitoring a SIP UA.
http://wiki.brekeke.com/wiki/Brekeke-SI ... tification
In your case, if Tenor is down then the notification mail will be sent to you.
Which edition of SIP Server are you using?
If you are using Advanced Edition, you can use Failure Notification feature for monitoring a SIP UA.
http://wiki.brekeke.com/wiki/Brekeke-SI ... tification
In your case, if Tenor is down then the notification mail will be sent to you.
The Failure Notification feature can monitor any SIP device even if the device's IP address is a dynamic because it can use a device's REGISTER IP address.
With the Failure Notification, the SIP Server sends a notification mail to you if the SIP device is down. It means you can keep these mails as historical data.
You can ask Brekeke's sales team to provide an evaluation license of Advanced Edition.
With the Failure Notification, the SIP Server sends a notification mail to you if the SIP device is down. It means you can keep these mails as historical data.
You can ask Brekeke's sales team to provide an evaluation license of Advanced Edition.
We upgraded to the Advance Edition.
I have added some remote Tenor Endpoints to the Heartbeat page.
However, only if I put in the current IP address of the tenor the feature works well. The problem is that all the IP addresses for the for remote tenors are dynamic. I suppose once the IP address changes we will get a false failure e-mail notification.
What should I put in the SIP URI field so that the heartbeat feature work for us?
I have added some remote Tenor Endpoints to the Heartbeat page.
However, only if I put in the current IP address of the tenor the feature works well. The problem is that all the IP addresses for the for remote tenors are dynamic. I suppose once the IP address changes we will get a false failure e-mail notification.
What should I put in the SIP URI field so that the heartbeat feature work for us?
The below Endpoint Tenor is registered in the "Registered Clients" as follows:
User
im5q1
Contact URI
sip:im5q1@192.168.1.60:5106
Detail
Expires : 300
Priority : 1000
User Agent : Quintum/1.0.0 SN/0030E1030BD4 SW/P107-09-00
Requester : 189.147.171.101:5106
Time Update : Mon Jun 21 17:23:58 CDT 2010
Heartbeat settings:
Heartbeat 1
Heartbeat Monitoring Method: SIP
SIP URI: sip:im5q1@192.168.1.60:5106
Interval: 30
Response Codes: 404
Please confirm what I am doing wrong as I am still getting a Failure.
User
im5q1
Contact URI
sip:im5q1@192.168.1.60:5106
Detail
Expires : 300
Priority : 1000
User Agent : Quintum/1.0.0 SN/0030E1030BD4 SW/P107-09-00
Requester : 189.147.171.101:5106
Time Update : Mon Jun 21 17:23:58 CDT 2010
Heartbeat settings:
Heartbeat 1
Heartbeat Monitoring Method: SIP
SIP URI: sip:im5q1@192.168.1.60:5106
Interval: 30
Response Codes: 404
Please confirm what I am doing wrong as I am still getting a Failure.
Thanks for your response, but unfortunately is still not working I have tried the following settings for SIP URI and they all go immediately to "Failed", the only way it works is configuring heartbeat as NETWORK and putting the public IP of the UA, but this is not desirable because the IP changes
sip:im5q1@localhost
sip:im5q1@<IP of the server>
sip:im5q1
sip:im5q1@
im5q1
sip:im5q1@192.168.1.60:5106
sip:im5q1@192.168.1.60
sip:im5q1@<public IP of the UA>
im5q1@<public IP of the UA>
What could be wrong ?
sip:im5q1@localhost
sip:im5q1@<IP of the server>
sip:im5q1
sip:im5q1@
im5q1
sip:im5q1@192.168.1.60:5106
sip:im5q1@192.168.1.60
sip:im5q1@<public IP of the UA>
im5q1@<public IP of the UA>
What could be wrong ?
I have copy and paste the information reflected on the "Registered Clients" screen.
User
im5q1
Contact URI
sip:im5q1@192.168.1.60:5106
Detail
Expires : 300
Priority : 1000
User Agent : Quintum/1.0.0 SN/0030E1030BD4 SW/P107-09-00
Requester : 189.147.148.91:5106
Time Update : Wed Jun 30 06:59:18 CDT 2010
User
im5q1
Contact URI
sip:im5q1@192.168.1.60:5106
Detail
Expires : 300
Priority : 1000
User Agent : Quintum/1.0.0 SN/0030E1030BD4 SW/P107-09-00
Requester : 189.147.148.91:5106
Time Update : Wed Jun 30 06:59:18 CDT 2010
Please find below the call log generated when running Heartbeat 1.
java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
at com.brekeke.net.sip.common.SIPpacketInvoke.invoke(Unknown Source)
at com.brekeke.siptool.haman.HeartbeatSIP.sendPacket(Unknown Source)
at com.brekeke.siptool.haman.HeartbeatSIP.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
null(2) is down!!
Email sent to:noc@noiptel.com
java.net.SocketTimeoutException: Receive timed out
at java.net.PlainDatagramSocketImpl.receive0(Native Method)
at java.net.PlainDatagramSocketImpl.receive(PlainDatagramSocketImpl.java:136)
at java.net.DatagramSocket.receive(DatagramSocket.java:712)
at com.brekeke.net.sip.common.SIPpacketInvoke.invoke(Unknown Source)
at com.brekeke.siptool.haman.HeartbeatSIP.sendPacket(Unknown Source)
at com.brekeke.siptool.haman.HeartbeatSIP.run(Unknown Source)
at java.lang.Thread.run(Thread.java:619)
null(2) is down!!
Email sent to:noc@noiptel.com