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 - Monica Tepelus

Pages: 1 2 [3] 4 5 ... 13
Yate users hangout place / Re: Is Yate Community dead?
« on: February 02, 2018, 09:12:12 AM »
Hi Badhills,

Yate is allve and well.

It's true that we haven't been very vocal in the opensource area in the last period of time but we've been busy building many products based on Yate. Some of the new features and the fixes are pushed to the public version of Yate as well. This are mostly related to the Javascript interpretor that we highly recommed.

The good news is that we'll soon release Yate 6.1.

Other Yate server issues / Re: Routing some calls by javascript module
« on: January 03, 2018, 04:36:24 AM »

To choose the best way you need to know the criterias for routing in js/regexroute. You can have different priorities of the call.route message. The smaller the number, the higher the priority.

You could set the javascript route first (just install the handler with priority 90). Default priority for call.route in regexroute is 100.
Route all the calls that you want from js, all those not routed (return false;  -- in code), will pass on to be routed in regexroute. If you "return true;" with/without an error, then call won't pass on to

Various combinations are possible. You can fix handling call.route/call.preroute and playing with the priorities when installing handlers.

You also need to choose the type of javascript script to use: global script/routing script. If many calls reach the script you should use a global script. The routing script allows you to route and build small ivr but it starts an instance for every call. If you just want to route, global script is more eficient.

The routing is done automatically in the nipc.js script. Regexroute is not involved at all. You leave registration with regexp (that is also done in the nipc script), and don't modify anything in the regexroute.

If the outbund connection is set and it's connected, then calls that can't be routed inside will automatically go to them. If you set in regexroute to route all calls outside, it's normal not to be able to route anything to the registered users.

Post an archive with all you configuration files and a yate log with sniffer and debug on as instructed in the previos post. Just a single screenshot doesn't help.

If the Outbound connection is up, then all calls that can't be routed inside the network (defined subscribers phone numbers - msisdns  or their short numbers) will be routed to the outbound connection.

The regexroute is wrong. You should not need to define anything in regexroute to get calls to go to the outbound connection.

Can you post a log with "sniffer on" and "debug sip level 9" from telnet?,_or_Investigation_of_messages


Did you configure the NiPC  Outbound connection? Please check the status of the registration:
Telnet to yate console and type "status accfile". If outbound connection is up you shoud see: outbound=set_username in below line

yate-sdr@ybts-UNCONFIG> status accfile

Yate users hangout place / MOVED: Can't start Yate with BladeRF
« on: November 03, 2017, 07:32:03 AM »

Linux / Re: abonent information
« on: October 25, 2017, 02:05:17 AM »
I will investigate this. Thanks for pointing it out.

Linux / Re: abonent information
« on: October 23, 2017, 01:37:11 AM »
Yes. If Yate was restarted it doesn't show them, because it looses that information at restart.

Linux / Re: YateENB
« on: October 17, 2017, 04:30:09 AM »
Hi Aldo,

The NIB web application was replaced with the LMI web application that has the features of the old NIB + new ones to configure the ENB and other small improvments.
You can follow:
From here you have links for both BTS/ENB configurations.

If you have additional questions you can post them here or in the private support tracker.

Yate users hangout place / Re: call as a registered user
« on: October 04, 2017, 01:20:58 AM »
SIP doesn't work like that. Authentication is different from placing the call. You can't do this in a single step.
Basically you want to make a call, the other party rejects the call asking for authentication, you authentify, and then you place the calls. This happends in multiple SIP messages.

Yate users hangout place / Re: call as a registered user
« on: October 03, 2017, 06:04:55 AM »
You want to call that user as well? I mean you want to make a call on the user's behalf and call the user and the other party and connect them?

The format of what your pgsql procedure is not right for routing.  You return multiple rows with format:
This is not correct. You need to have column name = param_name  and value is the one in a row. The correct format would be

param_name1  | param_name2 | param_name3 | ...
row1_value1    | row1_value2    | row1_value3   | ...
row2_value1    | row2_value2 ...

location=name_of_param that holds the actual location (Ex: param_name2)

The other columns will be added as parameters to the call.route message.
By default only the first row of result will matter, unless you activate fallback routing in register.conf

Other Yate server issues / Re: External Module Communication
« on: September 29, 2017, 06:50:48 AM »
If you wish to build an IVR start from one on the IVR examples from scripts/ directory. PHP is similar to C in syntax and you should be able to read them.

In your code I think you are missing an :. Try:

 fprintf(stdout, "%%%%<message:%s:true::\n", curToken);

This is an example from a script more complex .sh global script that handles a single message:

        if [ -n "$resp" ]; then
      echo "%%<message:$id:true:::$resp"
      echo "%%<message:$id:false::"

Other Yate server issues / Re: External Module Communication
« on: September 29, 2017, 01:21:57 AM »
You did not acknowledge the message.  Acknowledging is separate. It doesn't matter if you handled the message or not.

Linux / Re: abonent information
« on: September 25, 2017, 01:13:53 AM »
Online subscribers are those resulted with "nib list registered". Do you want current calls?

Pages: 1 2 [3] 4 5 ... 13