Messages

346

Yate users hangout place / Re: simple sip phone dial

« on: December 09, 2014, 02:55:40 AM »

If you set the 'line' parameter the call will fail (I suppose you don't have a line '100' registered to another server).
NOTE: If you want to call on a different path a busy target you should be aware you might call again to someone that rejected the call!

If you want to fallback to another target use fork.
See http://docs.yate.ro/wiki/Call_Forker

The handler should look like this:

if ($ev->getValue("called")=="100") {
  $ev->retval = "fork";
  $ev->params["callto.1"] = $location;
  $ev->params["callto.2"] = "|";
  $ev->params["callto.3"] = PUT_HERE_THE_SECOND_TARGET;
  $ev->params["callto.1.maxcall"] = PUT_HERE_MAX_CALLING_TIME_IN_MILISECONDS;
  $ev->params["stoperror"] = "noanswer|busy^";
  $ev->params[""] = ;
  $ev->handled = true;
  $ev->Acknowledge();
  break;
}

347

Yate users hangout place / Re: simple sip phone dial

« on: December 08, 2014, 06:56:49 AM »

As noted in November 27 post a line is an account registered by yate to another server.

If you want to route a call to an user registered to yate you should either:
1. Let register route the call
2. Query the database to retrieve user location and route the call to it

348

YateBTS / Re: YateBTS with bladeRF x115: No yate.log file

« on: December 08, 2014, 05:19:41 AM »

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

349

Installation from packets/SVN/.exe/AppStore / Re: Yate not start

« on: December 08, 2014, 05:15:44 AM »

Yate i starting.
You see nothing because you are using the -d command line parameter.

Use yate --help
It would give you some help about command line parameters.

350

Yate users hangout place / Re: simple sip phone dial

« on: December 08, 2014, 05:12:02 AM »

The register appearing in handlers parameter is set when call.preroute message is handled. When call.preroute succeeds it is renamed to call.route and re-dispatched: this is the reason register appears there.

The call is routed by route.php. Priority 80.
If you want the routing to be handled nu register before route.php set a lower value priority in it (lower value means higher priority).

351

Yate users hangout place / Re: simple sip phone dial

« on: December 05, 2014, 03:15:14 AM »

Something is wrong.
Make sure you are loading the right register.conf file and restarted yate after changing register.conf.
The configured priority of call.route is 120. In the log you posted register call.route priority is 50.

352

Yate users hangout place / Re: simple sip phone dial

« on: December 04, 2014, 02:59:42 AM »

There is no database message sent by register module when routing.
Are you sure you removed comment char from register.conf, call.route section?

353

Yate users hangout place / Re: simple sip phone dial

« on: December 02, 2014, 06:18:55 AM »

Yes. 'location' is the default field name.

NOTE: You can put ${data} in any database field you want as long as you properly return it when routing.

354

Yate users hangout place / Re: simple sip phone dial

« on: November 27, 2014, 03:03:11 AM »

Looking at your post I noticed you are using different names for table and location field.
Change them in [call.route] also.

355

Yate users hangout place / Re: simple sip phone dial

« on: November 27, 2014, 03:01:22 AM »

The register module has its own route handler which route the call to registered user location when the called number matches the registered username.
All you have to do is to remove comments (the ; char) in register.conf, [call.route] section and enable the handler in register.conf:
[general]
call.route=yes

NOTE: A line (used to route calls to it) is an user yate registers to another entity. E.g. yate is the client (user) of another server.

356

Linux / Re: route not work

« on: November 19, 2014, 01:54:51 PM »

Set a lower value in regexroute call.route handler.
regexroute.conf:
[priorities]
route=90

This will allow regexroute to handle call.route before regfile.

Changed called number to 100 and let the call.route be handle by regfile:

[default]
.*=return false;called=100

357

Linux / Re: route not work

« on: November 19, 2014, 10:48:47 AM »

What do you mean by 'all incoming calls are still receives sip-user 941234567'?

Calls to 941234567 are sent to registered user '941234567'?
This is ok, regfile has its own call.route handler and route calls to registered users.

358

Linux / Re: route not work

« on: November 19, 2014, 06:27:34 AM »

The right side of the '=' in route handlers is the target to route the call to.
E.g. for sip is sip/...
What target is route/ ?
Do you have a module executing the call when the target starts with 'route/'?

359

Other Yate server issues / Re: IAX2 without listen on port 4569

« on: November 17, 2014, 05:16:51 AM »

You may change the port (in yiaxchan.conf) to a different value.
There is no 'dedicated' listener for outgoing connections.
A listener is used for both directions.
If you want to reject calls on a specific listener do it when routing incoming calls.

360

Other Yate server issues / Re: Yate & RFC-2806

« on: November 14, 2014, 09:22:37 AM »

Yes.
In this case the number in From header 'tel:' uri will be set in 'caller' parameter.