Re: [OpenSIPS-Users] Question

2020-05-28 Thread Alex Balashov

These processes are related to the Postfix SMTP MTA.

On 5/28/20 10:38 PM, Saint Michael wrote:
I have an opensips box, and the programs  below are running. I did not 
install the box, so I am not sure what that do. Does anybody know?


├─master─┬─cleanup
         │        ├─local
         │        ├─pickup
         │        ├─qmgr
         │        └─trivial-rewrite

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



--
Alex Balashov | Principal | Evariste Systems LLC

Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free)
Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] Question

2020-05-28 Thread Saint Michael
I have an opensips box, and the programs  below are running. I did not
install the box, so I am not sure what that do. Does anybody know?

├─master─┬─cleanup
│├─local
│├─pickup
│├─qmgr
│└─trivial-rewrite
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


[OpenSIPS-Users] The calling API in OpenSIPS 3.1 - a short update

2020-05-28 Thread Bogdan-Andrei Iancu

Hi all,

I guess you all noticed that a important piece of the OpenSIPS 3.1 is 
the Call API. Still, will haven't shared so much information on that, so 
let me bring some light here (or an update on the topic).


The calling API is offered by a new separate software (external to 
OpenSIPS) called "Call API ". And 
this Call API uses OpenSIPS as a SIP stack in order to run the calls.


So, the Call API engine seats between the actual API user and OpenSIPS, 
acting as an enabler between the two sides.


On the user side, the Call API:
 * provides an WebSockets based API
 * offers commands start, terminate, mute/unmute and transfer the calls 
hosted on OpenSIPS

 * feeds back the user with events about the manged calls.

On the OpenSIPS side, the Call API:
 * talks to OpenSIPS via the MI interface (MI datagram)
 * subscribes for events via the event interface
 * uses the new "callops" module for a better grip and control over the 
calls in OpenSIPS



The OpenSIPS side was completed, as part of the OpenSIPS 3.1 release, 
but we are still working on the actual Call API to complete some logic 
on managing the calls and reporting events.


We expect the have this work completed in the next 2 weeks, with full 
documentation, usage examples/scenarios and blog posting. And of course 
with a first release of the Call API :)



Best regards,

--
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com

___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users