Messages

1

Yate bugs / Unable to start SCTP listener

« on: July 20, 2023, 02:20:19 AM »

None of these examples start a SCTP listener:
https://docs.yate.ro/wiki/Configure_M2UA
https://docs.yate.ro/wiki/Configure_M3UA
https://docs.yate.ro/wiki/Miscellaneous_configurations

For example:

sigtransport.conf
-------------------
[sctp-gw]
type=sctp
stream=true
local=127.0.0.1:2904
endpoint=false <-- not affected!

ysigchan.conf
-------------------
[m3ua-gw]
type=ss7-m3ua-gateway
sig=sctp-gw

It does not start sctp listener:

#lsmod|grep sctp
sctp                  278528  2
libcrc32c              16384  1 sctp

# cat /proc/net/sctp/eps
 ENDPT     SOCK   STY SST HBKT LPORT   UID INODE LADDRS

# netstat -pnla
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1783/sshd                   
tcp        0      0 127.0.0.1:5038          0.0.0.0:*               LISTEN      1995/yate


After doing many tests, I made sure that yate successfully creates only m2pa and m3ua-client connections.
Any ideas how to make a m3ua-gateway ?

Best regards, Anton

2

Yate users hangout place / docs.yate.ro - broken links!

« on: July 19, 2023, 06:02:23 AM »

I see a lot of broken links of image files on docs.yate.ro

https://docs.yate.ro/wiki/index.php?title=Special%3AAllPages&from=&to=&namespace=6

3

Yate users hangout place / Re: Where is the Yate's community?

« on: July 28, 2021, 03:09:43 AM »

Thanks a lot

4

Yate users hangout place / Where is the Yate's community?

« on: July 26, 2021, 04:33:11 AM »

Where is the Yate's community?

Forum is inactive.
IRC cannel is closed
Mailing list is closed
Discord link is broken

Thanks

5

Yate IVR / Re: Nodejs library compatible to javascript.yate

« on: April 16, 2020, 10:33:59 AM »

I suppose you messed up something with running a script with extmodule.
If the script would be launched by extmodule there is no need to use a network connection.
For example:

extmodule.conf configuration
[scripts]
node.sh=local_connected.js

And local_connected.js could contains something like this:
let yate = new Yate();

Of course, If you really want network connected script and launched by yate you can do it in "execute" section:
extmodule.conf configuration
[listener sample]
type=tcp
addr=127.0.0.1
port=6030
role=global

[execute]
node.sh=network_connected.js

And network_connected.js:
let yate = new Yate({ host: "127.0.0.1", port:6030 });

Second answer
I've experimented with WAV files and listened artifacts per voice file too. I don’t understand why such a popular format is still ignored by Yate Team. I would recommend to you converting WAV files to a more suitable format. Here is brief guide http://docs.yate.ro/wiki/ConvertingAudio

Best regards,
Anton

6

Yate IVR / Re: Nodejs library compatible to javascript.yate

« on: April 16, 2020, 09:00:51 AM »

I try to play with your module, but this string from  example_core_api.js :

Code: [Select]

yate.init(() => console.log("Connected"));
causes an error in yate console :

Code: [Select]

<ExtModReceiver:WARN> Error: 'Connected'
this is normal ?

Something seems to be wrong.
Are you using the latest version from Git?
Outdated examples with own bugs have been removed. So, please, show the beginning of this code, if it’s not difficult for you.

Best regards.
Anton

7

Yate based projects / Re: Nodejs library compatible to javascript.yate

« on: April 14, 2020, 12:17:19 PM »

Here is next release
https://github.com/0LEG0/next-yate

Best regards,
Anton

8

Yate IVR / Re: Nodejs library compatible to javascript.yate

« on: April 14, 2020, 12:16:00 PM »

Here is next release:
- Message filter are moved to the application side.
- Method Yate.watch provided with filter like Yate.install.
- The Channel object is now available in global script mode too (+YateChannel class).
- And bug fixes of course...
https://github.com/0LEG0/next-yate

Best regards,
Anton

9

Other Yate server issues / Are compatible OpenSSL module with lets encrypt certs?

« on: April 01, 2020, 04:07:09 AM »

Hello dear Community.

I have letsencrypt certbot generated files:
privkey.pem - rsa private key,
cert.pem - signed certificate,
chain.pem - chain of letsencrypt certs,
fullchain.pem - chain of letsencript certs with cert.pem

ysipchan.conf:
ssl_certificate_file=fullchain.pem
ssl_key_file=privkey.pem
[listener SIPTLS]
enabled=yes
default=no
type=tls
addr=x.x.x.x
port=5061
sslcontext=server_context

openssl.conf
[server_context]
enable=yes
domains=*.mydomain,ip1,ip2
certificate=fullchain.pem
key=privkey.pem

regexroute.conf
[outgoing]
^123.*=sip/sip:otherserver;oip=ip1;oip_transport=tls;oconnection_id=SIPTLS

TEST
openssl s_client -connect myserver:5061 = cert is OK
openssl s_client -connect otherserver:5061 = cert is OK
call from myserver to otherserver = TIMEOUT
yate.log:
<openssl:WARN> Certificate verify error 20: UNABLE_TO_GET_ISSUER_CERT_LOCALLY

May be someone have experience with yate sip tls and letsencrypt certs?

Best regards,
Anton

10

Yate IVR / Re: Nodejs library compatible to javascript.yate

« on: February 26, 2020, 10:35:42 AM »

Hello Community.

I decided to split the project into two:
The first will be core (stable) https://github.com/0LEG0/next-yate
and the second compatible with javascript.yate (experimental) https://github.com/0LEG0/next-yate-compat
In the next "Next-Yate" update, the compatibility abstraction will be removed. If someone needs javasctipt.yate compatibility please go to "Next-Yate-Compat" https://github.com/0LEG0/next-yate-compat.

Best regards,
Anton

11

Yate based projects / Re: Nodejs library compatible to javascript.yate

« on: February 26, 2020, 10:35:09 AM »

Hello Community.

I decided to split the project into two:
The first will be core (stable) https://github.com/0LEG0/next-yate
and the second compatible with javascript.yate (experimental) https://github.com/0LEG0/next-yate-compat
In the next "Next-Yate" update, the compatibility abstraction will be removed. If someone needs javasctipt.yate compatibility please go to "Next-Yate-Compat" https://github.com/0LEG0/next-yate-compat.

Best regards,
Anton

12

Features requests / Support of broadcast type of message in Extmodule protocol

« on: February 26, 2020, 04:55:59 AM »

Dear Colleagues,

Please add the support of broadcast type of message to external module protocol.

Best regards,
Anton

13

Yate based projects / Re: Nodejs library compatible to javascript.yate

« on: February 16, 2020, 03:43:23 AM »

"Channel" support was added.

Here is example of adapted welcome.js script:
https://github.com/0LEG0/next-yate/blob/master/examples/welcome.js

Best regards,
Anton

14

Yate IVR / Re: Nodejs library compatible to javascript.yate

« on: February 16, 2020, 03:42:42 AM »

Dear Community.

"Channel" support was added.
Here is example of adapted welcome.js script:
https://github.com/0LEG0/next-yate/blob/master/examples/welcome.js

Best regards,
Anton

15

Yate IVR / Re: Nodejs library compatible to javascript.yate

« on: February 12, 2020, 01:32:03 AM »

Hello.

This library does not have obvious advantages over libraries in python, php or perl.
All advantages only over the javascript.yate module.
At the moment, I see the following problems with the javascript.yate module:
1. Low performance: slow arrays and operations with them, it is almost impossible to work with> 200 simultaneous calls.
2. Poor language constructs: it is impossible to call the function returned by the expression in without intermediate storage of the result in variable; lack of syntactic sugar.
3. There is no way to go beyond the yate sandbox.
All of these shortcomings motivated me to take up the development of a full-fledged javascript library, while the idea to preserve the original javascript.yate API seemed interesting to me.
Inside my library, all entities are connected by events and promises. Perhaps as one of the advantages over libraries in php and perl there will be no need to develop your own event reading / processing loop. This simplifies the code a bit.
Otherwise, as I said, there are no advantages over other external libraries.

Best regards,
Anton