Thank you Bogdan,
Ok i will open the feature request.
Mario sv
El 13 abr 2020, a la(s) 10:12, Bogdan-Andrei Iancu
escribió:
Hi Mario,
yes, you cannot use both. The dialog module is expecting the call to be handled
in proxy mode, while the B2B module expect the call to handled in
Thank you Bogdan
Mario sv
El 13 abr 2020, a la(s) 9:40, Bogdan-Andrei Iancu
escribió:
Hi Mario,
First of all, you need to pick one b2b or dialog - you cannot use both in the
same time for the same call.
Secondly, please see the B2B tutorial
Hi Brett. I am going with the 3.1 version. Exec is unusable in production.
On Mon, Apr 13, 2020 at 1:19 PM Brett Nemeroff wrote:
> While this may work, I'd caution you against using the exec module for
> anything performant. It is a heavy beast. Or rather, your spawned shell is.
> Beware.
>
>
While this may work, I'd caution you against using the exec module for
anything performant. It is a heavy beast. Or rather, your spawned shell is.
Beware.
On Mon, Apr 13, 2020 at 11:50 AM Calvin Ellison
wrote:
> On Mon, Apr 13, 2020 at 8:13 AM Saint Michael wrote:
> > I am trying to do the
On Mon, Apr 13, 2020 at 8:13 AM Saint Michael wrote:
> I am trying to do the same. The question I need to ask here is: how do you
> generate the signature from the certificate, the caller ID and the
> destination number?
> I have the API working in staging mode, but now I need to really sign a
Maybe you should first take a look at
https://blog.opensips.org/2020/01/23/shaken-not-stirred/ and
https://opensips.org/docs/modules/3.1.x/stir_shaken.html
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
I see, so I need to update my Opensips to 3.1, and then how does it work?
the module grabs my certificate and generates the signature?
Is there a command line tool that can do that meanwhile? We can always add
the signature like any other header.
Can somebody paste a sample code here so I my try?
Hi Frederico,
I'm not really sure I understand your question of "how" to generate the
signature. Are you refering to how the scripting should look like or
something else ? But anyway, it is not possible with OpenSIPS 2.4.7 as
the stir_shaken module is available starting with OpenSIPS 3.1.
You are 100% right Alexey, I was just to lure Jeff to go for 3.0 ;)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
https://www.opensips.org/events/Summit-2020Amsterdam/
On 4/13/20 6:11 PM, Alexey Vasilyev
I am trying to do the same. The question I need to ask here is: how do you
generate the signature from the certificate, the caller ID and the
destination number?
I have the API working in staging mode, but now I need to really sign a
call and send it forward with Opensips 2.4.7
Federico
On Mon,
Hi Michael,
No, it is not possible.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May 2020
https://www.opensips.org/events/Summit-2020Amsterdam/
On 4/9/20 11:43 AM, Michael Vale via Users wrote:
hi.
is it
Hi Mario,
yes, you cannot use both. The dialog module is expecting the call to be
handled in proxy mode, while the B2B module expect the call to handled
in back2back mode. So logically speaking you cannot have them both
working together.
Maybe you can open a feature request on OpenSIPS
Hi Bogdan,
Yes, of course, in 3.0 you have implemented full support for the sharing
tags. But when these commits were made, the sharing tags were only in
process of discussion. So it's absolutely temporarily solution only for 2.4
branch.
And for Jeff, there is no modparam. Just call
Hi Alexandru,
OpenSIPS is using the signature in DER encoded format (as it is directly
generated by openssl) but indeed it is not the proper format as per RFC
7518. Thanks for the report, I am working on a fix.
Regards,
Vlad Patrascu
On 10.04.2020 12:28, Alexandru Tripon wrote:
Hi,
I
Hi guys,
actually 3.0 provides a better approach to the problem, by using the
sharing tags provided by the clustering layer [1]. Only the OpenSIPS
instance having the tag active will perform the pinging/probing and
broadcast the status changes into the cluster.
Unfortunately 2.4 does not
Hi Kamlesh,
I would suspect you do something wrong in the failure_route, when
handling the FWD cases. Maybe another change over the contact hdr in the
INVITE ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Summit, Amsterdam, May
Hi Mario,
First of all, you need to pick one b2b or dialog - you cannot use both
in the same time for the same call.
Secondly, please see the B2B tutorial
(https://www.opensips.org/Documentation/Tutorials-B2BUA) - once you
started the B2B session (by the b2b_init script function), the
17 matches
Mail list logo