Messages

46

Yate users hangout place / Re: Routing a call, using a database ( register.conf / PHP ) Over 2 different Lines

« on: October 03, 2017, 01:41:11 AM »

The format of what your pgsql procedure is not right for routing.  You return multiple rows with format:
param_name=param_value
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

47

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:
 http://yate.null.ro/websvn/filedetails.php?repname=yatebts&path=%2Ftrunk%2Fnipc%2Fauth%2Fnipc_auth.sh

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

48

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.

49

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?

50

Other Yate server issues / Re: Yate Redirect SIP 300 Multiple Choices

« on: September 18, 2017, 03:58:25 AM »

Hi,

Yate doesn't implement all SIP 300 variations.

Pbxassist was not thought to work with SIP 300 requests. If you wish to use the pbxassist functioality you should configure the phones to send the dmnfs to Yate and configure the combination of digits in yate's pbxassist module. You can't combine SIP redirects with Yate's pbxassist.

51

Linux / Re: abonent information

« on: September 18, 2017, 03:48:08 AM »

If Yate is restarted then yes, list of registered users is deleted. Users continue to have service.
Do you mean something else by "online users"?

52

Linux / Re: abonent information

« on: September 13, 2017, 03:40:46 AM »

Hi,

I suppose that this is what you want:
https://wiki.yatebts.com/index.php/Javascript_NiPC#NiPC_Commands

53

YateBTS / Re: Hi I have problem with mine BladeRF

« on: September 08, 2017, 05:05:13 AM »

Hi,

You might not see it if you are too close or too far or if registration was already rejected (even if your network is correctly configured).
If registration was already rejected you have to stop phone, take sim out and insert it again and then try again.

You should also make sure your phone is in the same band as the one configured.

54

YateBTS / YateBTS NiPC - application rename

« on: August 25, 2017, 05:32:56 AM »

Hello everybody,

Due to some trademark issues we renamed the YateBTS NIB to YateBTS NiPC (YateBTS Network in a PC). The change was made in our svn and websites: yatebts.com and wiki.yatebts.com.
After an update you will probably have some problems. You will need to reinstall YateBTS or do some fixes manually. We are sorry about this. If you have problems, post then here and we'll be happy to help you update your configuration.

A short list of the major changes: nib directory & nib.js were renamed to nipc, nipc.js. The YateBTS running mode is now called: nipc.

Previous posts about this app will not be modified and information from them will continue to be valid.

Thanks & good luck ,
The Yate Team

55

Yate users hangout place / Re: Routing a call, using a database ( register.conf / PHP ) Over 2 different Lines

« on: August 09, 2017, 07:15:33 AM »

Hi,

It's normal to mix routing from external module and the handling of other messages from register.conf.

Regarding your autentication problem, you don't need to do the authentication in the external script, you just need to request it. So you don't need to install user.auth.
To do this you should  set $ev->params["error"] = "noauth" and return false to the call.route message when username param is not set. This will trgger authentication and the next call.route message you receive will have parameter "username" set (in this way you'll know the user was authenticated).

56

Yate users hangout place / Re: Routing a call, using a database ( register.conf ) Over 2 different Lines

« on: July 26, 2017, 01:53:07 AM »

Hi,

Yes, but it's more difficult.
You need to use fork syntax for Yate > 3.3.3. It allows you to set different parameters for each fork leg. You would need to return location=fork and set all the options in different parameters in the message (this is the hard part).

http://docs.yate.ro/wiki/Call_Forker

As far as I remember a stored procedure in plpgsql needs to return a fixed number of parameters. You would need define a maximum number of parameters.

When routing is this complicated we usually prefer an external module or a javascript script that does queries but allows for easier manipulation of message parameters.

57

Linux / Re: telnet 127.0.0.1 5038 not reachable

« on: July 17, 2017, 02:43:54 AM »

If you used the nib interface and saved something, yate was restarted and of course your telnet connection was closed. You need to connect again after a restart.

58

YateBTS / Re: Help to change NIB.JS

« on: July 13, 2017, 01:57:56 AM »

This looks kind of ok. It's unclear why you would need to save this and what should happen in the various cases saveUEinConf is called.

I think you didn't reload the script after the last modifications. Your code doesn't match the resulted filte. After you make a change in the code you need to restart yate and reregister the phone or at least to type this in telnet "javascript reload nib".

The supported date functions are here:
http://docs.yate.ro/wiki/Javascript_Date

59

YateBTS / Re: Help to change NIB.JS

« on: July 11, 2017, 03:09:44 AM »

What did you modify? Please post a diff of nib.js

60

Linux / MOVED: Help to change NIB.JS

« on: July 11, 2017, 03:08:31 AM »

This topic has been moved to YateBTS.

http://forum.yate.ro/index.php?topic=1444.0