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 - ky4k0b

Pages: [1]
1
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 20, 2019, 09:07:36 AM »
as far as I understand building routing rules I have to do the following

[$once]
ani=0

[default]
.*=call borsch

[borsch]
${caller}^.*\(..\)$=;ani=\1
^38\(.*\)$=line/\1;line=${ani}

or maybe I can do it with "match" but I didn't find any examples how to use it :(

2
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 20, 2019, 08:53:12 AM »
marian,

as I can see from regexroute I can split called number with regexp and use parts further after "="
But how can I split caller number the same way? I have in incoming INVITE:
Contact: <sip:295987456223@1.2.3.4:5060>
I need to route it like this:
^38\(.*\)$=line/\1;line=23
where 23 is the last 2 digits from caller number

3
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 08, 2019, 10:25:30 AM »
Line id is basically source number. Can I change caller-id on outgoing leg to selected line id?
Something like that:
^.*$=line/\0;line=$(index,$line,123,456);callername=$line

4
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 08, 2019, 04:58:03 AM »
yes, thats what I need.

can you explain what does it mean?

[$once]
line=0

5
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 08, 2019, 03:37:07 AM »
marian,

but how can I do round-robin between these two lines?
Like this:
^.*$=sip/sip:\0@$(index,$idx00,62.XXX.XX.XX0:5065,213.XX.XX.XX0:5065)
but for registered lines

6
Other Yate server issues / Re: Round Robin in regexroute.conf
« on: August 07, 2019, 10:50:31 AM »
marian,

how can I round-robin between lines configured in accfile?
for instance I have two lines :
Code: [Select]
[123]
enabled=yes
protocol=sip
username=123
password=123
registrar=sip.registrar.com:5260

[456]
enabled=yes
protocol=sip
username=456
password=456
registrar=sip.registrar.com:5260

will this line in regexroute work? I mean if I have incoming call to dnis 123 will it be routed to line 123 and dnis 456 to according line 456?
Code: [Select]
^\(.*\)$=line/\1;line=\1

7
Other Yate server issues / Re: yate doesn't proxy rtp between legs
« on: April 10, 2018, 02:50:37 AM »
thanks, marian
yes, the issue was with iptables

8
Other Yate server issues / yate doesn't proxy rtp between legs
« on: April 05, 2018, 10:53:33 AM »
Hi, I'm facing pretty same issue as described here
https://forum.yate.ro/index.php?topic=1201

I have the following setup with yate binded to two interfaces - wan and vpn


unfortunately yate doesn't pass rtp streams between legs so it causes dead air.

regexroute is very basic - send all calls to Bob(VPN)
.*$=sip/sip:${called}@172.21.42.2:5063;callername=${caller};

If you can help me that would be great. Full debug is here:
http://paste.org.ru/?5xtq93

9
Yate users hangout place / Re: yate basic configuration
« on: May 16, 2014, 05:27:23 PM »
problems faced and successfully resolved:
1) cfg was not applying
Wrong directory. Can be checked with:
Code: [Select]
telnet localhost 5038
status engine
If you install from source - default dir is /usr/local/etc/yate/
from repos - /etc/yate

2) ^001\(.*\)$=sip/sip:\1;line=test1 --- outdated
correct one was:
Code: [Select]
[default]
${username}^$=call check_addr_auth
^99991001$=tone/dial
^99991002$=tone/busy
^99991003$=tone/ring
^99991004$=tone/specdial
^99991005$=tone/congestion
^99991006$=tone/outoforder
^99991007$=tone/milliwatt
^99991008$=tone/info

^001\(.*\)$=line/\1;line=test1
^002\(.*\)$=line/\1;line=test2

[check_addr_auth]
${address}^1\.1\.1\.1:=return
.*=-;error=forbidden;reason=fuckyou
3) sip traces can be enabled by:
Code: [Select]
telnet localhost 5038
debug on
sniffer on
debug sip level 9
4) most times simple reload in rmanager doesn't work. Yate restart required.

That's all that I've learned from today.
Thanks monica and marian

10
Yate users hangout place / Re: yate basic configuration
« on: May 16, 2014, 02:59:41 AM »
Still don't see answers on my questions:
1) Is this configuration correct for my scheme?
2) Where can I find sip logs for incoming and outgoing calls
3) >For example regexroute rules are always replaced on reload.
how do you reload?
4) What yate logs available? Other than /var/log/yate
5) What happens with the calls when GW2/3 rejects registration?

11
Yate users hangout place / yate basic configuration
« on: May 15, 2014, 06:13:13 PM »
Hello yate gurus!

I just installed yate pbx on debian and need to implement simple scheme with routing based on prefixes.
         GW1 (1.1.1.1)
            ↓  (no registration, auth by ip-address only)
          yate
   ↓                 ↓ (yate registers on both GW2 and GW3)
GW2           GW3

What is done so far:
Code: (accfile.conf) [Select]
[test1]
enabled=yes
protocol=sip
username=user1
password=pw1
registrar=2.2.2.2

[test2]
enabled=yes
protocol=sip
username=user2
password=pw2
registrar=3.3.3.3

I see in /var/log/yate
Code: [Select]
20140515233120.052067 <sip:CALL> SIP line 'test1' logon success to 2.2.2.2:5060hence I suppose that I've been registered successfully.

Next in
Code: (regexroute.conf) [Select]
[default]
^99991001$=tone/dial
^99991002$=tone/busy
^99991003$=tone/ring
^99991004$=tone/specdial
^99991005$=tone/congestion
^99991006$=tone/outoforder
^99991007$=tone/milliwatt
^99991008$=tone/info

^001\(.*\)$=sip/sip:\1;line=test1
^002\(.*\)$=sip/sip:\1;line=test2
[check_addr_auth]
${address}^1\.1\.1\.1:=return
.*=-;error=forbidden;reason=fuckyou
But somehow yate keeps returning 404 for all calls.
Here're my questions:
1) Correct me pls if I made mistakes above.
2) How do I check sip call flow? Basically how can I see it online or enable traces in conf files?
3) How do you apply new configuration? For example after I edit .conf files do I need to restart yate or put any commands? Or is everything applies on fly?
4) How do I enable full non-proxy media for all calls? I need RTP packets go directly from GW1 to GW2

That's all yet. Looking forward to your answers!

Pages: [1]