Recent Posts

61

YateBTS / Re: yateBTS network operator name of 712712

« Last post by kpz on May 16, 2020, 04:39:12 AM »

Great to hear this bug is fixed, it was literally driving me nuts at that time.

goodboy, I appreciate that help and will check it out when I dive back into it at somepoint just for sh!ts and giggles, thank you.

62

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

« Last post by cc08 on April 19, 2020, 04:59:19 PM »

Indeed, the conversion to the slin solved the click problems.
Thanks a lot.

63

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

« Last post by Anton 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

64

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

« Last post by cc08 on April 16, 2020, 09:16:59 AM »

Yes, today was a free day, I decided to try it.
Today's git too.
I took an example from the first page of your git, slightly modifying it.

Code: [Select]

// Core API
const { Yate, YateMessage } = require("next-yate");
let yate = new Yate({ host: "127.0.0.1", port:6030 });

yate.init(() => {console.log("Connected")}); // Initialize connection before use
yate.output("Hello World!");


A little cleared up, this error appears when the script is launched by the extmodule from yate.

If the launch is manual, then everything is clean in yate.

Second question
When playing several wav files between them I listen to clicks.
How can you deal with this?

65

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

« Last post by Anton 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

66

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

« Last post by cc08 on April 16, 2020, 08:17:50 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 ?

67

Yate based projects / Cannot connect device to BTS - Location Update Reject

« Last post by roho on April 15, 2020, 10:57:48 AM »

I have yatebts set up with a bladeRF x40. I've verified that MBTS is running and have set up nipc. I registered my sim's IMSI through nipc, and I can see the BTS when a do a search of my mobile networks on my phone. When I try to connect to the BTS it returns "Unable to connect. Try later." I checked out the network traffic on Wireshark and it always gets a "Location Updating Reject" cause 12 Location Area not allowed. When I looked at the Location Area ID my MCC and MNC were set to the test network I wanted. I tried changing the MCC and MNC back to the default (001 01), and then I tried other combinations of MCCs and MNCs I found online but nothing has worked. Is there something I'm missing in the set up that other yatebts users might be familiar with that has caused similar issues in the past?

68

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

« Last post by Anton on April 14, 2020, 12:17:19 PM »

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

Best regards,
Anton

69

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

« Last post by Anton 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

70

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

« Last post by Anton 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