Recent Posts

Pages: 1 ... 7 8 [9] 10
81
Features requests / Support of broadcast type of message in Extmodule protocol
« Last post by Anton 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
82
Yate based projects / Re: Nodejs library compatible to javascript.yate
« Last post by Anton 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
83
Yate IVR / Re: Nodejs library compatible to javascript.yate
« Last post by Anton 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
84
Yate IVR / Re: Nodejs library compatible to javascript.yate
« Last post by Anton 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
85
Yate IVR / Re: Nodejs library compatible to javascript.yate
« Last post by cc08 on February 11, 2020, 01:37:31 PM »
Anton, can you suggest more complex use cases that reveal the benefits of this module.
Waht differens from others ?
86
Yate IVR / Re: Nodejs library compatible to javascript.yate
« Last post by Anton on February 11, 2020, 10:56:59 AM »
Library are published as npm module now.
to install run:
Code: [Select]
npm install next-yate
Best regards,
Anton

P.S.
Any suggestions and criticism are welcome
87
Yate based projects / Re: Nodejs library compatible to javascript.yate
« Last post by Anton on February 11, 2020, 10:54:27 AM »
Library are published as npm module now.
to install run:
Code: [Select]
npm install next-yate
Best regards,
Anton

P.S.
Any suggestions and criticism are welcome
88
SIP to H.323 proxy / Re: Unable to foward calls from H323 to SIP
« Last post by Tsouthwick on February 11, 2020, 06:14:21 AM »
Hi - that is not what I was asking about. I was requesting why the startRTP was showing a different IP address, the line in green and the line in red.
89
SIP to H.323 proxy / Re: Unable to foward calls from H323 to SIP
« Last post by cc08 on February 10, 2020, 03:22:02 PM »
I see one mistake in a regexroute.conf - space after a vertical slash. He should not be there. But the reason may not be that. Therefore, I recommend:

1. since the connection breaks on the x323 side, enable x323 level 10 debugging.

2. Since the gap is initiated by the remote side, look at the cause of the break there.

3. to search for the cause of the gap, make default configs with the necessary settings minimum. Do not include parameters whose purpose is unknown.

90
SIP to H.323 proxy / Re: Unable to foward calls from H323 to SIP
« Last post by Tsouthwick on February 07, 2020, 03:37:20 AM »
Attached is a zip file with the config

Pages: 1 ... 7 8 [9] 10