Messages

1

Yate bugs / Re: [fix] Yate dialing problems...

« on: May 04, 2018, 04:18:45 PM »

ok, that helps a lot.
Not sure what the value of overriding data through inb: would be.
is there a complete list of these kind of overrides in some manual?

imho those out: & inb: overrides should be mentioned in at least accfile.conf / regfile.conf
of in some xcross-reference list the keywords for files.

At least there is a way to handle things... 

2

Yate bugs / [Fix] Yate dialing problems...

« on: May 03, 2018, 03:48:48 PM »

The osip_From:sip:mynumber@isp;   entry worked.

3

Yate bugs / Re: Yate dialing problems...

« on: May 03, 2018, 03:46:29 PM »

The first form was documented... but rejected by the ISP as the From url was the URL used for connecting the Phone -> Yate.

Thanks for the 2nd form, using the osip_From worked..., but i haven't found that in the documentation... It might need a bit better examples/ being referenced.
This means a lot of dial entries are needed depending on line chosen. + info that is IN the accfile.conf needs to be dupplicated to regexfile.conf.

Why not have an option to use the info from accfile.conf (or database profile) or registration info of the phone .. or maybe even the incoming dial info on connect through (if the ISP supports that, it wont work for me though).

4

Yate bugs / Yate loosing context?

« on: May 01, 2018, 09:00:01 AM »

[contexts]
${in_line}^\(ips1_[0-9][0-9]\}\)$=\1
${in_line}^\(isp2_[0-9][0-9]\)$=\1
${caller}^\(238[123456]\)$=x\1
.*=default


For some reason contexts don't get matched (consistently)...
(I also tried mentioning context in accfile.conf & regfile.conf  which also doesn't work consistently)
yate fresh startup it seems to work
after reload only the default context seems to be used.

5

Yate bugs / [fix] Yate dialing problems...

« on: April 29, 2018, 12:03:28 PM »

(either a bug in software, or in documentation)
I have: a few Voip Phones, Gigaset DX800 & S450-IP... the connect to yate... (no issue there).
(the connect to accounts like ext1@mydomain ..ext8@mydomain )
I have: 3 voip accounts with ISP1 and 2 with ISP2.    All accounts are basically phone accounts not gateways.
(LINE_11=phn1@isp1.domain, ... LINE_13=phn3@isp1.domains) & (LINE_21=phn1@isp2.domain & LINE_22=phn2@isp2.domain)

To dial out i need the SIP packet to have (From: phn1@isp1.domain; to: dialednumber@isp1.domain)

but the Calls generated by regex:
^012345678$=line/\1;line=LINE_11
does Become:     
SIP( From: ext1@mylocalhostname; To:dialednumber@isp1.domain)   which is halfway good....

^012345679$=line/\1;line=LINE_12;caller=phn2
does Become:
SIP( From: phn1@mylocalhostname; To:dialednumber@isp1.domain)   which is 3/4 good...
But is still rejected by the isp1..., due to the from.

dialing using the Sip extention  does n't work out as there is no way to select the right line:
^34567$=sip/sip:\1@isp1.domain    # is still missing a way to select a specific line...)
when using:
^34567$=sip/sip:\1@isp1.domain;caller=phn1    # is still missing a way to select a specific line...)
and delivers:
SIP( From: phn1@mylocalhostname; To:dialednumber@isp1.domain)   which is also 3/4 good...

If there is a right way it surely is hidden good in docs, site, ...
So i hope someone here can help out.

6

Features requests / Fix yate mailserver...

« on: April 29, 2018, 11:31:12 AM »

This is not about yate (yet)... but the (formum) mailserver.

The mail server is names ns.null.ro, but the HELO/EHLO announce is yatebts_web4.localdomain
which uses a local name & _ in the name.. where the hostname (ns.null.ro) should be used.

This will land a lot of your mail in spam folders. (or prevent delivery al together due to the _ in the HELO/EHLO announcement.)