Messages

91

YateBTS / Re: How do i clear the online subscribers list

« on: January 06, 2017, 02:27:55 AM »

That's normal. If yate is stopped when phone sends detach from network it will miss that event. The phone will be marked as away after a specific time if it doesn't register to the network again.

92

YateBTS / Re: How do i clear the online subscribers list

« on: January 04, 2017, 02:50:15 AM »

The content of the page is not refreshed automatically. Did you click on it again or moved to other tab and back?

93

YateBTS / Re: Call logs empty?

« on: January 04, 2017, 02:41:52 AM »

The config.php must be in the nib web directory. You already have an empty config.php there

94

YateBTS / Re: How do i clear the online subscribers list

« on: January 03, 2017, 04:08:25 AM »

List subscribers contains the manually defined subscribers. If you are using regexp, you won't see any subscribers in that page.

95

YateBTS / Re: Call logs empty?

« on: January 03, 2017, 03:30:18 AM »

Hi,

Do you see any error when viewing the call logs tab? Do you have /etc/yate/cdrfile.conf? If should look something like:

general]
file=/var/log/yate-cdr.csv
tabs=false

Also make sure that the file listed above /var/log/yate-cdr.csv is readable by apache.

96

Yate users hangout place / Re: Network wide SMS message?

« on: December 20, 2016, 02:33:00 AM »

Hi,

It's in nib directory in yate sources;
http://yate.null.ro/websvn/filedetails.php?repname=yatebts&path=%2Ftrunk%2Fnib%2Fnib.js

After install you should find it in /usr/share/yate/scripts or /usr/local/share/yate/scripts

97

YateBTS / Re: Trouble with subscribers expiring

« on: December 19, 2016, 06:57:13 AM »

Hi,

There is a bug in nib.js that we didn't manage to fix yet. For the moment you can configure subscribers individually until we fix the regexp issue sometimes in january.

98

Yate users hangout place / Re: Network wide SMS message?

« on: December 19, 2016, 02:32:52 AM »

Hi,

No, you don't have that option. But you can modify the nib javascript application: "nib.js" to send a message to all registered devices.

99

Other Yate server issues / Re: Sip-i --> Yate --> sip

« on: December 16, 2016, 03:17:36 AM »

Hi,

Yate doesn't have sip-i support.

100

Yate based projects / Re: Connecting two YateBTS GSM Base Stations with the use of RPi3 and BladeRF

« on: December 14, 2016, 02:57:14 AM »

Hi,

You didn't specify how you configured the BTSs. I suppose you used nib mode and accepted registrations with regexp. Normally alls call that can't be routed internally will be sent to the outbound connection with caller parameter rewritten. You can define an outbound connection from the interface (doesn't matter if it doesn't registrates) and catch the call.execute in regexroute and rewrite param lication from  "line/.." (${location}^line ) to sip/sip:\0@ip2:port. Same for the other box, just replace ip2 with the ip of the first box.

101

Other Yate server issues / Re: Stop processing to the next 'if' once the condition in first met.

« on: November 11, 2016, 02:55:43 AM »

You need a break after $ev->handled = true;  to stop processing.

102

Installation from packets/SVN/.exe/AppStore / Re: Yate nib web UI issues

« on: October 07, 2016, 01:36:28 AM »

Hi,

Do you see an error in the web interface? If not, check the /var/log/httpd/error_log to see if you get any hint? If you don't see anything, check php.ini and make sure errors are displayed or logged.

103

Installation from packets/SVN/.exe/AppStore / Re: Yate nib web UI issues

« on: October 06, 2016, 07:21:59 AM »

I'm not sure what you need, but that tab is not realtime. Once you click on it, it asks yate to return registered subscribers, but that information is not refreshed automatically. You need to refresh the page yourself.

104

Installation from packets/SVN/.exe/AppStore / Re: Yate nib web UI issues

« on: October 06, 2016, 03:23:26 AM »

Hi,

If you connect with telnet on port 5038  then type "nib list registered"  do you see them?

Monica

105

Other Yate server issues / Re: PHP warning

« on: August 31, 2016, 06:50:08 AM »

Hi,

It's not dangerous, but you might lose some debug messages and it might be confusing.

It seems you are using Yate::Output("message") in the scripts without running Yate::Output(true) before the main loop.  In this case the debug messages won't appear in Yate telnet log, and they will be pushed to the php error stream.

By following the code it seems the error stream could not pe opened for write: fopen("php://stderr","w").

It would be better to put Yate::Output(true) before using  Yate::Output("message") in the scripts. It might be confusing not seeing the messages when debugging