Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ioana Stanciu

Pages: 1 ... 3 4 [5] 6
61
Linux / Re: Make file error
« on: June 22, 2015, 01:30:25 AM »
It looks like it doesn't find libbladeRF for linking.

Please follow instructions found here http://wiki.yatebts.com/index.php/Installing

If you still have issues, please post a log containing the result of your running of the configure script and a full make log (in order to able to see the make command).


62
YateBTS / Re: Could not route call to '32843'
« on: May 21, 2015, 01:36:09 AM »
You should have had libgsm1-dev installed before installing yate. So, if you now have installed, you need to rebuild and reinstall Yate (so that Yate can detect that it has libgsm1-dev and can activate the support for it).
During reinstallation of Yate, during the configure step, make you see something like this in the output of configure:
Code: [Select]
checking for gsm.h in /usr/include... yes
Then reinstall Yate.
Afterwards, configure and reinstall YateBTS.

63
YateBTS / Re: Could not route call to '32843'
« on: May 20, 2015, 01:52:18 AM »
Regarding this:

Quote
it is not possible to give you the whole telnel log because terminal cuts the starting lines when they are a lot!

you said that you are starting Yate like this: yate -Df -vvvvv -l /var/log/yate.log. So you have logging to file activated to file yate.log in /var/log. You could have attached that (or the part of if that corresponds with the call). It's not needed anymore, but for future reference.

You said that you had configured in javascript.conf ;
Code: [Select]
[general]
routing=welcome.js

but looking at your attached javascript.conf, i see:

Code: [Select]
[general]
; General settings for the Javascript module

; scripts_dir: string: The absolute or relative path used by default to load
;  scripts if no full path is specified
;scripts_dir=${sharedpath}/scripts

; include_dir: string: The absolute or relative path used when including other
;  files via #include or #require if no full path is specified
; If the file is not found in include_dir it will be searched in scripts_dir
;include_dir=${configpath}

; routing: string: Name of the file holding the routing instructions
; Example: routing=route.js
;routing=


So you've either not attached the correct javascript.conf or the one where you've told me you made the configuration is not in the configuration path of yate.

So I will repeat this again: check that in  the javascript.conf located in the configuration path of yate (path reported by yate in configpath when you give the command status engine in telnet. The last status engine you posted said that the path is configpath=/usr/local/etc/yate, but check again) you have configured

Code: [Select]
routing=welcome.js
If after that, it still doesn't work, paste again: yate log with sniffer enabled, output of status engine, and ybts.conf and javascript.conf from the configuration path reported by yate.

64
YateBTS / Re: Could not route call to '32843'
« on: May 19, 2015, 02:32:31 AM »
Could you also post javascript.conf and yatebts.conf (the whole files) from your configuration path (which yate says it's configpath=/usr/local/etc/yate).

Also, post a full log, not a piece of it (if it's too long, you can attach it).

I still suspect a misconfiguration issue.

65
YateBTS / Re: Could not route call to '32843'
« on: May 18, 2015, 06:38:06 AM »
Please post the log corresponding with the call attempt. Please activate message sniffer also ( see http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages ) in order to be able to see through which handlers the call.route message went through.

Also, please state which version of Yate & YateBTS are you using. How are you starting Yate?

66
YateBTS / Re: Registration failed on gsm network
« on: May 15, 2015, 01:22:18 AM »
Yes, it should use subscribers.conf. And I dont know if it's a typo or not, but make sure the file is named subscribers.conf, not subscriber.conf.

First, the regexp  ^001 will never match your IMSI (log says that the IMSI of the phone trying to register starts with 510).
As for the regexp that would match everything ( .*) , make sure you're loading the configuration correctly.
You can check from where yate is loading subscribers.conf by typing status engine in the rmanager console and looking at the configpath variable. Check that you have subscribers.conf in that path, or  that the path corresponds to the folder where you've make all your configuration changes.


67
YateBTS / Re: Registration failed on gsm network
« on: May 14, 2015, 01:34:47 AM »
It looks like you haven't configured your NIB to accept registrations from that IMSI.

You can allow registration from subscribers.conf or through the NIB web interface. You can also put a regexp to allow IMSIs that match that regexp to register (but please be careful not to accept everything, as it could possibly disrupt phones around).

Take a look at:
http://wiki.yatebts.com/index.php/Javascript_NIB#subscribers.conf
http://wiki.yatebts.com/index.php/Network_in_a_Box#Web_UI_for_NIB_Management

68
YateBTS / Re: Registration failed on gsm network
« on: May 13, 2015, 06:26:13 AM »
Hi,

please attach a log from YateBTS corresponding to this registration attempt.

You can find information about logging and debugging for YateBTS here:
http://wiki.yatebts.com/index.php/Logging_and_Debugging


69
YateBTS / Re: Could not route call to '32843'
« on: May 13, 2015, 01:22:57 AM »
Regarding the "permission denied" messages, please make sure to run yate as root.

What do you mean by
Quote
with yatebts I connect in "Roaming"
?

YateBTS has 2 modes: NIB or Roaming. You can't run YateBTS in both modes at the same time. In  NIB mode you can call, if everything is configured correctly, the IVR available at 32843.
Please look throuhg the documentation available here
http://wiki.yatebts.com/index.php/Javascript_Roaming
http://wiki.yatebts.com/index.php/Javascript_NIB

Also, make sure you are loading the correct configuration. You can check that by running the
'status engine'
command in the telnet console (look for the configpath value).

If still that doesn't work, please attach a log and your configuration.

70
YateBTS / Re: Could not route call to '32843'
« on: May 11, 2015, 01:31:36 AM »
Hi,

Please make sure that in javascript.conf you have this:

[general]
routing=welcome.js





71
YateBTS / Re: cannot understand on telnet
« on: April 23, 2015, 01:13:00 AM »
Hi,

Most likely the ybts module is not loaded.
Try 'status ybts' or 'status mbts' in the rmanager console. If it's showing as a result
%%+status:ybts
%%-status

then you don't have the module loaded.
Check your configuration and that the path from where you're loading modules contains ybts.
You can check from where yate tries to load modules by typing in rmanager the command 'status engine' and look at the 'modulepath' parameter .

72
Hi,

modload controls loading of modules. When you set it to no, no modules willl be loaded by the YATE engine unles it is specified in the [modules] section. So unless you specified extmodule.yate=yes in the modules section, your script will not load.

If you want a sniffer log, you either have to set 'msgsniff' setting to yes in yate.conf or you can activate it throug telnet through command "sniffer on".

Check these pages:
http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages
http://docs.yate.ro/wiki/Debugging_in_Yate
http://docs.yate.ro/wiki/Rmanager

73
Installation from packets/SVN/.exe/AppStore / Re: starting up yate
« on: August 20, 2014, 05:57:25 AM »

The path where you installed libyate is not in the path of the dynamic loader.  In order to add that path you need to edit /etc/ld.so.conf file and add a new line with the desired path. The path where you have installed libyate is probably  /usr/local/lib or /usr/local/lib64.

After you do the editing run (also as root) the following command ldconfig and then retest if you can run yate.

74
Yate users hangout place / Re: <sip> Flood detected
« on: January 07, 2014, 02:50:11 AM »
Hi,

If you didn't alter SIP configuration, you get those warnings when the processing thread has handled more than 100 SIP events (messages) in a row without emptying its processing queue. This can happen because of the options you mentioned.

Please take a look at the floodevents configuration setting in ysipchan.conf sample for further explanation and in order to tweak the setting as to not generate so many warnings if it's caused by slow processing.



75
Yate bugs / Re: YateServer not responding
« on: October 03, 2013, 05:14:00 AM »
The path is wrong. It's not

sudo /Library/Application/Support/Yate/yate.init start

but

sudo /Library/Application\ Support/Yate/yate.init start.


Pages: 1 ... 3 4 [5] 6