1
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 26, 2019, 12:40:08 AM »
Here is an example of matching last 2 digits:
${caller}\([0-9]\{2\}\)$=;any=\1
${caller}\([0-9]\{2\}\)$=;any=\1
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.
2
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 08, 2019, 11:45:01 PM »
^.*$=line/\0;line=$(index,$line,123,456);callername=${line}
3
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 08, 2019, 05:06:48 AM »
Initialize variable.
You may take a look at regexroute.conf for any information related to sections, functions ...
You may take a look at regexroute.conf for any information related to sections, functions ...
4
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 08, 2019, 04:16:37 AM »
If you want to round robin lines no matter the called number:
[$once]
line=0
[default]
^.*$=line/\0;line=$(index,$line,123,456)
If not, please post a description of what exactly do you want to do.
[$once]
line=0
[default]
^.*$=line/\0;line=$(index,$line,123,456)
If not, please post a description of what exactly do you want to do.
5
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 07, 2019, 11:59:54 PM »
If you want to route called number to its line: yes
6
Yate bugs / Re: Routing Area Identification Not Set Correctly
« on: May 24, 2019, 08:09:11 AM »
Bug fixed: it was related to wrong handling MCC/MNC in GPRS AttachAccept
7
YateBTS / Re: yateBTS network operator name of 712712
« on: May 24, 2019, 08:08:24 AM »
Bug fixed: it was related to wrong handling MCC/MNC in GPRS AttachAccept
8
Yate users hangout place / Re: RSC message
« on: May 21, 2019, 11:49:41 PM »
Most probably the circuit is reset due to REL timeout.
9
Yate bugs / Re: Is it possible to extend timeout before YATE sends CANCEL?
« on: May 12, 2019, 11:48:47 PM »
Hi,
Try to increase the t1 timer value (default is 500ms).
This timer controls various transaction timers including INVITE timeout.
ysipchan.conf:
[general]
t1=600
Marian
Try to increase the t1 timer value (default is 500ms).
This timer controls various transaction timers including INVITE timeout.
ysipchan.conf:
[general]
t1=600
Marian
10
YateBTS / Re: Yate Failed to open usb Device
« on: February 22, 2019, 12:46:12 AM »
The device with id 2cf0:5250 is not currently detected by bladerf module as supported.
For nonce: you also don't have the bladerf module.
See the log line: Failed to create radio interface: Message not handled.
Most probably it wasn't built at all.
For nonce: you also don't have the bladerf module.
See the log line: Failed to create radio interface: Message not handled.
Most probably it wasn't built at all.
11
Yate bugs / Re: XMPP Support (windows)?
« on: February 20, 2019, 12:37:33 AM »
Seems there is an issue after TLS is started.
There may be a problem with openssl.
Unfortunately this may be investigated only by using a newer version of the library and build yate on your Windows.
I may try a connection to your server if you post here its domain name.
There may be a problem with openssl.
Unfortunately this may be investigated only by using a newer version of the library and build yate on your Windows.
I may try a connection to your server if you post here its domain name.
12
Yate bugs / Re: XMPP Support (windows)?
« on: February 14, 2019, 12:37:52 AM »
Please select Settings -> Debug window
Make sure the 'Debug Here' and 'JABBER' options are checked.
Try to connect.
Post here the contents of the output.
Make sure the 'Debug Here' and 'JABBER' options are checked.
Try to connect.
Post here the contents of the output.
13
Windows / Re: Disable external ip detection
« on: January 31, 2019, 01:36:04 AM »
Linux YateClient accounts file is:
/home/<username>/.yate/client_accounts.conf
/home/<username>/.yate/client_accounts.conf
15
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: December 18, 2018, 12:38:02 AM »
Most probably call.ringing is not forwarded on incoming call leg.