Messages

76

Yate bugs / Re: YateServer not responding

« on: October 02, 2013, 03:08:59 AM »

It seems 127.0.0.1 does not work on Mac OS. Please try "telnet localhost 5038".

Also, you could try starting the YateServer through this command :
"sudo /Library/Application\ Support/Yate/yate.init start"

It also has options stop and restart and then check again with telnet and/or ps -Aaf | grep yate and report back to us.

77

Yate bugs / Re: YateServer not responding

« on: September 30, 2013, 01:39:55 AM »

How do you start YateServer?
If you go to a Terminal and issue the "ps -Aaf | grep yate" command, what results do you get?
Does issuing "telnet 127.0.0.1 5038" command int the Terminal work?
Do you see any log message regarding Yate (starting or crashing) in the Console? If so, please post them here. Also, please look in ~/Library/Log/CrashReporter if you have any logs for Yate crashing and if so, please post them here.

78

Yate bugs / Re: SNMP and Database

« on: January 23, 2013, 06:31:45 AM »

The solution seems to be to deprecate the entries that cause the problem and add new ones which are valid for snmptable (either by including the data currently in a sequence in the table columns, either by defining 2 tables linked by index).

My question is what happens when you interrogate for a deprecated OID. Maybe you could help me with that?

79

Yate bugs / Re: SNMP and Database

« on: November 06, 2012, 06:25:34 AM »

Hi,

We cannot accept the patch as this seems to be a limitation of the snmptable application.  Capturing the  SNMP packets shows that Yate returns the appropriate data, only that they are on a level below in the MIB tree. snmptable ignores all those responses.

snmpwalk seems to be the appropriate tool for this case as it can deal with the layout of the table data.

Regards,
Oana