391
Linux / Re: Redirect the call
« on: July 22, 2014, 03:41:06 AM »
Can you post the log with failed call?
Including sip messages and other yate debug messages.
Including sip messages and other yate debug messages.
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.
392
Linux / Re: Redirect the call
« on: July 22, 2014, 03:04:21 AM »
Can you tell what do you want to achieve?
If you want to send an incoming call to a destination (e.g. route the call): setting the return value of call.route does the job.
If you want to send an incoming call to a destination (e.g. route the call): setting the return value of call.route does the job.
393
Linux / Re: Redirect the call
« on: July 21, 2014, 07:55:50 AM »
For external script protocol see:
http://docs.yate.ro/wiki/External_module_command_flow
You'll find there what do you need to write to socket for message params and data.
http://docs.yate.ro/wiki/External_module_command_flow
You'll find there what do you need to write to socket for message params and data.
394
Linux / Re: Redirect the call
« on: July 21, 2014, 07:32:31 AM »
If you handle call.route just set the message return value to sip target you want to call.
PHP example (assuming $ev is the handled message):
$ev->retval = "sip/sip:111@172.17.2.181:5060";
Javascript example (assuming msg is the handled message):
msg.retValue("sip/sip:111@172.17.2.181:5060");
I don't understand what kind of script you are using.
PHP example (assuming $ev is the handled message):
$ev->retval = "sip/sip:111@172.17.2.181:5060";
Javascript example (assuming msg is the handled message):
msg.retValue("sip/sip:111@172.17.2.181:5060");
I don't understand what kind of script you are using.
395
Linux / Re: Redirect the call
« on: July 21, 2014, 12:44:34 AM »
Here is the entry point for routing:
http://docs.yate.ro/wiki/Routing
If something don't work as expected please post a log with yate messages and sip signalling.
See:
http://docs.yate.ro/wiki/Starting_Yate
http://docs.yate.ro/wiki/Debugging_in_Yate
http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages
Some note:
You don't have to change callto in call.execute. Just set return value to desired target in call.route.
http://docs.yate.ro/wiki/Routing
If something don't work as expected please post a log with yate messages and sip signalling.
See:
http://docs.yate.ro/wiki/Starting_Yate
http://docs.yate.ro/wiki/Debugging_in_Yate
http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages
Some note:
You don't have to change callto in call.execute. Just set return value to desired target in call.route.
396
Yate bugs / Re: iLBC negotiation
« on: July 18, 2014, 08:57:08 AM »
This is a feature request.
You should talk to Diana about it.
You should talk to Diana about it.
397
Other Yate server issues / Re: Limit number of calls per trunk
« on: July 10, 2014, 09:09:27 AM »
Change priority or remove regex routing.
398
Other Yate server issues / Re: Limit number of calls per trunk
« on: July 10, 2014, 08:37:51 AM »
I said nothing about routing to it through external module!!!
Just add it in javascript.conf and reload the javascript module.
The javascript module will execute it.
It's a global script, not a channel one so there is no need to route to it.
Just add it in javascript.conf and reload the javascript module.
The javascript module will execute it.
It's a global script, not a channel one so there is no need to route to it.
399
Other Yate server issues / Re: Limit number of calls per trunk
« on: July 10, 2014, 03:06:51 AM »
It is not easy to do it from regexroute.
I attached a javascript example for it.
The example can be used for your purposes.
Copy the file in share directory.
Add it in javascript.conf:
[scripts]
route=route.js
A simple reload will load the script.
NOTE: If you change the script and reload it channel tracking array will be lost.
You may use shared vars instead of local variables to avoid it
I didn't checked the script. Let me know if it's working.
I attached a javascript example for it.
The example can be used for your purposes.
Copy the file in share directory.
Add it in javascript.conf:
[scripts]
route=route.js
A simple reload will load the script.
NOTE: If you change the script and reload it channel tracking array will be lost.
You may use shared vars instead of local variables to avoid it
I didn't checked the script. Let me know if it's working.
400
Other Yate server issues / Re: Limit number of calls per trunk
« on: July 10, 2014, 12:53:23 AM »
What kind of trunk?
What protocol?
If you want to limit the number of sip or iax calls you may set them in ysipchan.conf and yiaxchan.conf, [general] section, 'maxchans' option.
What protocol?
If you want to limit the number of sip or iax calls you may set them in ysipchan.conf and yiaxchan.conf, [general] section, 'maxchans' option.
401
YateBTS / Re: Help with GSM phones connecting
« on: July 09, 2014, 01:19:35 AM »
What version of YateBTS do you have?
A log would help also.
A log would help also.
402
YateBTS / Re: How do I change the location update reject code?
« on: July 04, 2014, 12:50:31 AM »
Hi,
ybts.cpp:
See YBTSMM::locUpdTerminated()
ybts.cpp:
See YBTSMM::locUpdTerminated()
403
Installation from packets/SVN/.exe/AppStore / Re: Installing Yate on Windows
« on: June 16, 2014, 05:47:23 AM »
Are you running client and server on the same machine?
Is your server started?
Is your server started?
404
Other Yate server issues / Re: CID
« on: June 10, 2014, 12:58:14 AM »
See the random function in regexroute. (explained in regexroute.conf.sample)
$(random,STRING)
Each ? char in STRING will be replaced with a random digit
E.g:
${caller}^100$=;caller=$(random,000???)
$(random,STRING)
Each ? char in STRING will be replaced with a random digit
E.g:
${caller}^100$=;caller=$(random,000???)
405
Yate bugs / Re: iLBC negotiation
« on: June 05, 2014, 08:13:24 AM »
ilbc20/ilbc30 offer/accept is configured in [codecs] section.
ilbc related options in [hacks] section are used when parsing received SDP.
SDPMedia::update() is the place where exiting media is updated from received SDP.
When the existing formats list is replaced with a new one, the first format is chosen
Some notes:
- If received formats list is empty (none offered or no acceptable format) the existing formats are not replaced
- If received formats list is not empty:
- Local rtp: the format list is not updated if the intersection with offered formats leads to an empty list
- Forward rtp: The formats list is always replaced with received formats
ilbc related options in [hacks] section are used when parsing received SDP.
SDPMedia::update() is the place where exiting media is updated from received SDP.
When the existing formats list is replaced with a new one, the first format is chosen
Some notes:
- If received formats list is empty (none offered or no acceptable format) the existing formats are not replaced
- If received formats list is not empty:
- Local rtp: the format list is not updated if the intersection with offered formats leads to an empty list
- Forward rtp: The formats list is always replaced with received formats