Re: [OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine
Apologies for keep on bugging on this issue, but would really appreciate any hints. -Original Message- From: Users On Behalf Of xa...@web.de Sent: Wednesday, May 19, 2021 1:30 PM To: 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine Hi Would appreciate any hints on how to run the new 3.2 B2B module with RTPProxy or RTPEngine. Thanks, Xaled -Original Message- From: Users On Behalf Of xa...@web.de Sent: Friday, May 14, 2021 1:34 PM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine Hi, Are the any examples of using the new B2B module in 3.2 with RTPProxy or RTPEngine? I tried adding _offer and _answer call accordingly but never saw RTPProxy or RTPEngine engaged. Even a simple example for A-B call with B2B and RTPEngine would be much appreciated. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine
Hi Would appreciate any hints on how to run the new 3.2 B2B module with RTPProxy or RTPEngine. Thanks, Xaled -Original Message- From: Users On Behalf Of xa...@web.de Sent: Friday, May 14, 2021 1:34 PM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine Hi, Are the any examples of using the new B2B module in 3.2 with RTPProxy or RTPEngine? I tried adding _offer and _answer call accordingly but never saw RTPProxy or RTPEngine engaged. Even a simple example for A-B call with B2B and RTPEngine would be much appreciated. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] b2b_client_new ; transport=xxx string in dest_uri parameter
Any hints on how to set the outgoing transport protocol with b2b_client_new (OpenSIPS 3.2) if ;transport=xxx string does not work? From: Users On Behalf Of xa...@web.de Sent: Wednesday, May 12, 2021 2:29 AM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] b2b_client_new ; transport=xxx string in dest_uri parameter Hi, It seems like b2b_client_new function ignores the ;transport=xxx string in dest_uri parameter. Is this true, or am I missing something? Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] opensips 3.2 B2B module and RTPProxy/RTPEngine
Hi, Are the any examples of using the new B2B module in 3.2 with RTPProxy or RTPEngine? I tried adding _offer and _answer call accordingly but never saw RTPProxy or RTPEngine engaged. Even a simple example for A-B call with B2B and RTPEngine would be much appreciated. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] b2b_client_new ; transport=xxx string in dest_uri parameter
Hi, It seems like b2b_client_new function ignores the ;transport=xxx string in dest_uri parameter. Is this true, or am I missing something? Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] $b2b_logic.entity(id) in [reply_route] B2B module opensips 3.2
Hi,
I'm not getting the $b2b_logic.entity(id) in B2B [reply_route]. The log shows
Is this variable not available in the B2B [reply_route]?
route[b2b_announce_response] {
if ($rs != 500)
{
xlog("B2B REPLY: [$rs $rm] from entity: $b2b_logic.entity(id)\n");
b2b_handle_reply();
exit;
}
B2B REPLY: [183 INVITE] from entity:
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS 3.2 B2B tutorial pre-paid example
Hi Răzvan, Thank you for the reply. Indeed I was able to get the prepaid B2B scenario running with all the needed headers once I understood the mechanics of B2B module. Thank you and the team for the great module that will allow me to implement some very interesting scenarios! Greetings, Xaled -Original Message- From: Users On Behalf Of Razvan Crainea Sent: Wednesday, April 14, 2021 3:25 PM To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] OpenSIPS 3.2 B2B tutorial pre-paid example Hi, Xaled! No, there should bot be an SDP, because you don't have an SDP (the media server is gone, and you don't know the callee's SDP). Instead, the module is doing a late negotiation to find out advertised caller's SDP, and present it to the new callee. Best regards, Răzvan Crainea OpenSIPS Core Developer http://www.opensips-solutions.com On 4/14/21 3:17 PM, xa...@web.de wrote: > Hi, > > could somebody please shed some light on this scenario? > > Thanks, > Xaled > > -Original Message- > From: Users On Behalf Of > xa...@web.de > Sent: Sunday, April 11, 2021 11:59 PM > To: 'OpenSIPS users mailling list' > Subject: [OpenSIPS-Users] OpenSIPS 3.2 B2B tutorial pre-paid example > > Hi, > > I tested the 3.2 Prepaid example from B2B tutorial > > https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2 > > In Scenario Schema there is a first reinvite from OpenSIPS B2B to caller - > this reINVITE in my tests comes without SDP. Should not there be an SDP, or > am I missing something in this scenario? > > INVITE sip:TEST001@1.2.3.201:5060;transport=tcp SIP/2.0 > Via: SIP/2.0/TCP 1.2.5.183:5060;branch=z9hG4bKb5b7.1ffbf7b1.0 > To: ;tag=f79aacce > From: > ;tag=B2B.81.186.1618177460 > CSeq: 3 INVITE > Call-ID: 80a9a9cfbe9920f8@1.2.3.201 > Max-Forwards: 70 > Content-Length: 0 > Contact: > > Thanks, > Xaled > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > > ___ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] OpenSIPS 3.2 B2B tutorial pre-paid example
Hi, could somebody please shed some light on this scenario? Thanks, Xaled -Original Message- From: Users On Behalf Of xa...@web.de Sent: Sunday, April 11, 2021 11:59 PM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] OpenSIPS 3.2 B2B tutorial pre-paid example Hi, I tested the 3.2 Prepaid example from B2B tutorial https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2 In Scenario Schema there is a first reinvite from OpenSIPS B2B to caller - this reINVITE in my tests comes without SDP. Should not there be an SDP, or am I missing something in this scenario? INVITE sip:TEST001@1.2.3.201:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 1.2.5.183:5060;branch=z9hG4bKb5b7.1ffbf7b1.0 To: ;tag=f79aacce From: ;tag=B2B.81.186.1618177460 CSeq: 3 INVITE Call-ID: 80a9a9cfbe9920f8@1.2.3.201 Max-Forwards: 70 Content-Length: 0 Contact: Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi Bogdan,
I understood and got it working with extra_hdrs and extra_hdr_bodies.
Thank you,
Xaled
-Original Message-
From: xa...@web.de
Sent: Wednesday, April 14, 2021 1:54 PM
To: 'Bogdan-Andrei Iancu' ; 'users@lists.opensips.org'
Subject: RE: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi Bogdan,
I got it, the actual question is how can I add new headers (not only Route, but
any header) with values to the outgoing B2B INVITE request. Please see my other
mail.
Thanks,
Xaled
-Original Message-
From: Bogdan-Andrei Iancu
Sent: Wednesday, April 14, 2021 12:30 PM
To: xa...@web.de; users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi Xaled,
The record routing is incompatible with the b2b, by SIP definition. The record
routing is done only by a SIP proxy, not by a SIP b2b2.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 2021 online
https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 4/11/21 9:32 PM, xa...@web.de wrote:
> Hi,
>
> would it be possible to respect loose routing on the caller side of
> B2B module and set route header on the callee side accordingly
>
> Something like this:
>
> Incoming INVITE:
>
> INVITE sip:+12345678@1.2.3.4;user=phone SIP/2.0
> Via: SIP/2.0/TCP
> 4.3.2.1:5060;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
> Route: ,
>
>
> Wanted outgoing INVITE:
>
> INVITE sip:+87654321@1.1.1.1;user=phone SIP/2.0
> Via: SIP/2.0/TCP
> test.com;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
> Route:
>
> I tried setting loose_route in both the original route and in the resulting
> b2b route but without success.
>
> route[b2b_test_logic] {
>
> <-->loose_route();
>
> if ($rm != "BYE") {
> # for requests other than BYE, no special actions needs to be done,
> # just pass the request to the peer
> b2b_pass_request();
> exit;
> }
> ...
>
> Thanks,
> Xaled
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi Bogdan,
I got it, the actual question is how can I add new headers (not only Route, but
any header) with values to the outgoing B2B INVITE request. Please see my other
mail.
Thanks,
Xaled
-Original Message-
From: Bogdan-Andrei Iancu
Sent: Wednesday, April 14, 2021 12:30 PM
To: xa...@web.de; users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi Xaled,
The record routing is incompatible with the b2b, by SIP definition. The record
routing is done only by a SIP proxy, not by a SIP b2b2.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS Bootcamp 2021 online
https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 4/11/21 9:32 PM, xa...@web.de wrote:
> Hi,
>
> would it be possible to respect loose routing on the caller side of
> B2B module and set route header on the callee side accordingly
>
> Something like this:
>
> Incoming INVITE:
>
> INVITE sip:+12345678@1.2.3.4;user=phone SIP/2.0
> Via: SIP/2.0/TCP
> 4.3.2.1:5060;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
> Route: ,
>
>
> Wanted outgoing INVITE:
>
> INVITE sip:+87654321@1.1.1.1;user=phone SIP/2.0
> Via: SIP/2.0/TCP
> test.com;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
> Route:
>
> I tried setting loose_route in both the original route and in the resulting
> b2b route but without success.
>
> route[b2b_test_logic] {
>
> <-->loose_route();
>
> if ($rm != "BYE") {
> # for requests other than BYE, no special actions needs to be done,
> # just pass the request to the peer
> b2b_pass_request();
> exit;
> }
> ...
>
> Thanks,
> Xaled
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi,
Could somebody provide any advice on the issue?
Thanks,
Xaled
-Original Message-
From: Users On Behalf Of xa...@web.de
Sent: Sunday, April 11, 2021 11:36 PM
To: 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi,
I tried to use the extra_hdrs variable of b2b_client_new to set up the Route
header extra_hdrs (var, optional) - AVP variable holding a list of extra
headers (the header names) to be added for any request sent to this entity.
But was confused by the "header names" part and it looks like that it will not
accept headers with values. What is then the use of the variable?
xlog("INFO: B2B $b2b_logic.ctx(next_route)");
INFO: B2B Route:
$avp(route_header) = $b2b_logic.ctx(next_route); b2b_client_new("media",
"sip:+87654321@1.1.1.1;user=phone", "sip:$b2b_logic.ctx(server_ip)",
,$avp(route_header));
ERROR:b2b_logic:b2bl_entity_new: header names without values!
The need to have an avp for extra_hdrs is an unnecessary limitation, or is
there a specific reason for it?
Thanks,
Xaled
-Original Message-
From: Users On Behalf Of xa...@web.de
Sent: Sunday, April 11, 2021 8:33 PM
To: 'OpenSIPS users mailling list'
Subject: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi,
would it be possible to respect loose routing on the caller side of B2B module
and set route header on the callee side accordingly
Something like this:
Incoming INVITE:
INVITE sip:+12345678@1.2.3.4;user=phone SIP/2.0
Via: SIP/2.0/TCP
4.3.2.1:5060;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route: ,
Wanted outgoing INVITE:
INVITE sip:+87654321@1.1.1.1;user=phone SIP/2.0
Via: SIP/2.0/TCP
test.com;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route:
I tried setting loose_route in both the original route and in the resulting b2b
route but without success.
route[b2b_test_logic] {
<-->loose_route();
if ($rm != "BYE") {
# for requests other than BYE, no special actions needs to be done,
# just pass the request to the peer
b2b_pass_request();
exit;
}
...
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] OpenSIPS 3.2 B2B tutorial pre-paid example
Hi, I tested the 3.2 Prepaid example from B2B tutorial https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2 In Scenario Schema there is a first reinvite from OpenSIPS B2B to caller - this reINVITE in my tests comes without SDP. Should not there be an SDP, or am I missing something in this scenario? INVITE sip:TEST001@1.2.3.201:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 1.2.5.183:5060;branch=z9hG4bKb5b7.1ffbf7b1.0 To: ;tag=f79aacce From: ;tag=B2B.81.186.1618177460 CSeq: 3 INVITE Call-ID: 80a9a9cfbe9920f8@1.2.3.201 Max-Forwards: 70 Content-Length: 0 Contact: Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi,
I tried to use the extra_hdrs variable of b2b_client_new to set up the Route
header
extra_hdrs (var, optional) - AVP variable holding a list of extra headers (the
header names) to be added for any request sent to this entity.
But was confused by the "header names" part and it looks like that it will not
accept headers with values. What is then the use of the variable?
xlog("INFO: B2B $b2b_logic.ctx(next_route)");
INFO: B2B Route:
$avp(route_header) = $b2b_logic.ctx(next_route);
b2b_client_new("media", "sip:+87654321@1.1.1.1;user=phone",
"sip:$b2b_logic.ctx(server_ip)", ,$avp(route_header));
ERROR:b2b_logic:b2bl_entity_new: header names without values!
The need to have an avp for extra_hdrs is an unnecessary limitation, or is
there a specific reason for it?
Thanks,
Xaled
-Original Message-
From: Users On Behalf Of xa...@web.de
Sent: Sunday, April 11, 2021 8:33 PM
To: 'OpenSIPS users mailling list'
Subject: [OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi,
would it be possible to respect loose routing on the caller side of B2B module
and set route header on the callee side accordingly
Something like this:
Incoming INVITE:
INVITE sip:+12345678@1.2.3.4;user=phone SIP/2.0
Via: SIP/2.0/TCP
4.3.2.1:5060;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route: ,
Wanted outgoing INVITE:
INVITE sip:+87654321@1.1.1.1;user=phone SIP/2.0
Via: SIP/2.0/TCP
test.com;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route:
I tried setting loose_route in both the original route and in the resulting b2b
route but without success.
route[b2b_test_logic] {
<-->loose_route();
if ($rm != "BYE") {
# for requests other than BYE, no special actions needs to be done,
# just pass the request to the peer
b2b_pass_request();
exit;
}
...
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] loose_route with opensips 3.2 B2B module
Hi,
would it be possible to respect loose routing on the caller side of B2B module
and set route header on the callee side accordingly
Something like this:
Incoming INVITE:
INVITE sip:+12345678@1.2.3.4;user=phone SIP/2.0
Via: SIP/2.0/TCP
4.3.2.1:5060;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route: ,
Wanted outgoing INVITE:
INVITE sip:+87654321@1.1.1.1;user=phone SIP/2.0
Via: SIP/2.0/TCP
test.com;branch=z9hG4bK40365b83fb9732a054d124bb46252151.7242beeb
Route:
I tried setting loose_route in both the original route and in the resulting b2b
route but without success.
route[b2b_test_logic] {
<-->loose_route();
if ($rm != "BYE") {
# for requests other than BYE, no special actions needs to be done,
# just pass the request to the peer
b2b_pass_request();
exit;
}
...
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] use of scenario_id in b2b_init_request
Hi Vlad,
thank you, I missed the $b2b_logic.scenario variable that can be used to
differentiate logic within route[b2b_logic_request]. Now it is clear to me.
It would be good to include it as an example in the B2B tutorial or B2B module
documentation.
Greetings,
Xaled
-Original Message-
From: Users On Behalf Of Vlad Patrascu
Sent: Friday, April 9, 2021 7:12 PM
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] use of scenario_id in b2b_init_request
Hi Xaled,
The scenario ID is just a transparent identifier for the current B2B session.
You may use it to identify which session belongs to which of your B2B
scenarios. You can see this value in the output of b2b_list MI function and
also you can retrieve it in the script with $b2b_logic.scenario (this may be
useful if you use a single B2B request route, as in the example here: [1]).
Another purpose of the "scenario_id" parameter of b2b_init_request() is to be
able to choose the internal topology hiding scenario, by providing the special
value "top hiding".
[1]
https://opensips.org/docs/modules/3.2.x/b2b_logic.html#b2b_logic.scenario
Regards,
--
Vlad Patrascu
OpenSIPS Developer
http://www.opensips-solutions.com
On 09.04.2021 18:49, xa...@web.de wrote:
> Hi,
>
> I'm trying to understand the B2B module in 3.2 and don't quite get the
> meaning of scenario_id in b2b_init_request function.
>
> There are multiple examples that use different values in scenario_id
> https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2
>
> b2b_init_request("prepaid"); or b2b_init_request("refer"); but the values
> "prepaid" or "refer" not used to differentiate anything within
> route[b2b_logic_request] or anywhere else in documentation.
>
> I get the meaning of req_route parameter of b2b_init_request function to
> address different B2b logic using different routes, but what does the
> scenario_id used for?
>
> Thanks,
> Xaled
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] use of scenario_id in b2b_init_request
Hi,
I'm trying to understand the B2B module in 3.2 and don't quite get the meaning
of scenario_id in b2b_init_request function.
There are multiple examples that use different values in scenario_id
https://www.opensips.org/Documentation/Tutorials-B2BUA-3-2
b2b_init_request("prepaid"); or b2b_init_request("refer"); but the values
"prepaid" or "refer" not used to differentiate anything within
route[b2b_logic_request] or anywhere else in documentation.
I get the meaning of req_route parameter of b2b_init_request function to
address different B2b logic using different routes, but what does the
scenario_id used for?
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] use of . dot and colon : in XML node names
Any ideas? Without . dot support in XML item names the opensips XML implementation is useless for IETF RFC conform XML documents. -Original Message- From: Users On Behalf Of xa...@web.de Sent: Monday, February 22, 2021 12:58 PM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] use of . dot and colon : in XML node names Hi, I'm trying to encode an XML MIME body according to rfc7852 and need to use dot and colon in XML node names. Unfortunately I'm getting errors as dot is considered to be aprecial character for .attr and .val. is there are any ways to escape the dot? https://tools.ietf.org/html/rfc7852#section-4.1.10 $xml(ProviderInfo) = ""; $xml(ProviderInfo/emergencyCall.ProviderInfo.attr/xmlns) = "urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"; Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] set value of XML item using variable
Hi, is there a way to directly set XML item value using variable. It works for static values $xml(my_doc/doc/list) = "test"; But something like this does not work: $xml(my_doc/doc/list) = "$var(value)"; The only workaround I found it to use .val. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Timestamp in date format
Hi Ben,
thanks for comments and ideas. I was also thinking about something along the
lines.
There is a somewhat similar discussion on the opensips github on extending
$time functionality but unfortunately it did not progress since 2014:
https://github.com/OpenSIPS/opensips/issues/378#issuecomment-61608369
Thanks,
Xaled
From: Users On Behalf Of Ben Newlin
Sent: Tuesday, February 23, 2021 2:25 AM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Timestamp in date format
That function only uses the current time. As far as I know there are no
generic time string format functions in OpenSIPS. The only options are to
manipulate the current time only.
You could use exec or one of the language modules like python to do this. Or
you could write to the XML as a timestamp and convert it outside of
OpenSIPS. The latter would be my recommendation if possible.
Ben Newlin
From: Users mailto:users-boun...@lists.opensips.org> > on behalf of xa...@web.de
<mailto:xa...@web.de> mailto:xa...@web.de> >
Date: Monday, February 22, 2021 at 5:25 PM
To: 'OpenSIPS users mailling list' mailto:users@lists.opensips.org> >
Subject: Re: [OpenSIPS-Users] Timestamp in date format
Hi Ben,
found that as well, thank you.
Is there a way to add for example a week to the current datetime to have a
datetime that can be used to say that something is valid until one week in
the future?
If 2013-08-01T12:00:00Z is now then to have 2013-08-08T12:00:00Z
Thanks,
Xaled
From: Users mailto:users-boun...@lists.opensips.org> > On Behalf Of Ben Newlin
Sent: Monday, February 22, 2021 10:09 PM
To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >
Subject: Re: [OpenSIPS-Users] Timestamp in date format
> I know that there is a get_timestamp function but I need the result to be
formatted as date.
You can use the $time variable.
https://www.opensips.org/Documentation/Script-CoreVar-3-1#toc93
$time("%Y-%m-%dT%TZ")
Ben Newlin
From: Users mailto:users-boun...@lists.opensips.org> > on behalf of xa...@web.de
<mailto:xa...@web.de> mailto:xa...@web.de> >
Date: Monday, February 22, 2021 at 4:01 PM
To: 'OpenSIPS users mailling list' mailto:users@lists.opensips.org> >
Subject: [OpenSIPS-Users] Timestamp in date format
Hi,
I need to create a timestamp node in an XML body like shown below
2013-08-01T12:00:00Z
I know that there is a get_timestamp function but I need the result to be
formatted as date.
BTW, is there a way to directly define XML item value using variable
Something like:
$xml(my_doc/doc/list) = "$var(value)";
Unfortunately it does not work like this
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Timestamp in date format
Hi Ben,
found that as well, thank you.
Is there a way to add for example a week to the current datetime to have a
datetime that can be used to say that something is valid until one week in
the future?
If 2013-08-01T12:00:00Z is now then to have 2013-08-08T12:00:00Z
Thanks,
Xaled
From: Users On Behalf Of Ben Newlin
Sent: Monday, February 22, 2021 10:09 PM
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Timestamp in date format
> I know that there is a get_timestamp function but I need the result to be
formatted as date.
You can use the $time variable.
https://www.opensips.org/Documentation/Script-CoreVar-3-1#toc93
$time("%Y-%m-%dT%TZ")
Ben Newlin
From: Users mailto:users-boun...@lists.opensips.org> > on behalf of xa...@web.de
<mailto:xa...@web.de> mailto:xa...@web.de> >
Date: Monday, February 22, 2021 at 4:01 PM
To: 'OpenSIPS users mailling list' mailto:users@lists.opensips.org> >
Subject: [OpenSIPS-Users] Timestamp in date format
Hi,
I need to create a timestamp node in an XML body like shown below
2013-08-01T12:00:00Z
I know that there is a get_timestamp function but I need the result to be
formatted as date.
BTW, is there a way to directly define XML item value using variable
Something like:
$xml(my_doc/doc/list) = "$var(value)";
Unfortunately it does not work like this
Thanks,
Xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Timestamp in date format
Hi, I need to create a timestamp node in an XML body like shown below 2013-08-01T12:00:00Z I know that there is a get_timestamp function but I need the result to be formatted as date. BTW, is there a way to directly define XML item value using variable Something like: $xml(my_doc/doc/list) = "$var(value)"; Unfortunately it does not work like this Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] use of . dot and colon : in XML node names
Hi, I'm trying to encode an XML MIME body according to rfc7852 and need to use dot and colon in XML node names. Unfortunately I'm getting errors as dot is considered to be aprecial character for .attr and .val. is there are any ways to escape the dot? https://tools.ietf.org/html/rfc7852#section-4.1.10 $xml(ProviderInfo) = ""; $xml(ProviderInfo/emergencyCall.ProviderInfo.attr/xmlns) = "urn:ietf:params:xml:ns:emergencyCall.ProviderInfo"; Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Segfault bei TLS certificates in MySQL DB
Hi, I got server and client tls config working in opensips.cfg and now trying to get it running with mysql DB. I tried to use the latest opensips-cp (I know that 3.1 is not officially supported) to import client certificate data that I created using opensips-cli and getting a segfault. I can see the imported certificate using MySQL cli. Maybe I should try importing client cert from cli? What would be the correct way to import certificate in to OpenSIPS mysql table from linux shell? 9 02:29:30 test /usr/sbin/opensips[8551]: INFO:tls_mgm:init_tls_dom: Processing TLS domain 'test-cli' Jul 9 02:29:30 test /usr/sbin/opensips[8551]: DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'test-cli' defined, using default '(null)' Jul 9 02:29:30 test /usr/sbin/opensips[8551]: NOTICE:tls_mgm:init_tls_dom: No EC curve defined Jul 9 02:29:30 test /usr/sbin/opensips[8551]: DBG:tls_mgm:init_tls_dom: cipher list null ... setting default Jul 9 02:29:30 test /usr/sbin/opensips[8551]: INFO:tls_mgm:get_ssl_ctx_verify_mode: server verification activated. Jul 9 02:29:30 test /usr/sbin/opensips[8551]: NOTICE:tls_mgm:init_tls_dom: no CA dir for tls 'test-cli' defined, using default '/etc/pki/CA/' Jul 9 02:29:30 test /usr/sbin/opensips[8551]: NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none Jul 9 02:29:30 test /usr/sbin/opensips[8551]: DBG:core:count_module_procs: modules require 2 extra processes Jul 9 02:29:30 test /usr/sbin/opensips[8551]: CRITICAL:core:sig_usr: segfault in attendant (starter) process! Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] [OpenSIPS 3.1] Stable Release Date
Hi Bogdan, Great news! Will 3.1 Release also include updated control panel or will it come later? Thanks, Xaled Hello everyone, On 27th of May we had the beta release for OpenSIPS 3.1 . There was a lot of extra testing, many reports, a lot of feedback. All these translated in many fixes that made 3.1 more and more stable by the day. So, we are almost there :) - heads up, the *OpenSIPS 3.1 LTS stable release is **scheduled for 22th of July* ! You still have time to fill reports (if the case), to bring your personal contribution to the value of the 3.1 release. Otherwise, sit tight , the 3.1 stable is coming ! 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
[OpenSIPS-Users] Multidomain TLS with opensips 3.1 part 2
Hi, I got server and client tls config working in opensips.cfg and now trying to get it running with mysql DB. I tried to use the latest opensips-cp (I know that 3.1 is not officially supported) to import client certificate data that I created using opensips-cli and getting a segfault. Maybe I should try importing client cert from cli? What would be the correct way to import certificate in to mysql from linux shell? 9 02:29:30 test /usr/sbin/opensips[8551]: INFO:tls_mgm:init_tls_dom: Processing TLS domain 'test-cli' Jul 9 02:29:30 test /usr/sbin/opensips[8551]: DBG:tls_mgm:init_tls_dom: no DH params file for tls domain 'test-cli' defined, using default '(null)' Jul 9 02:29:30 test /usr/sbin/opensips[8551]: NOTICE:tls_mgm:init_tls_dom: No EC curve defined Jul 9 02:29:30 test /usr/sbin/opensips[8551]: DBG:tls_mgm:init_tls_dom: cipher list null ... setting default Jul 9 02:29:30 test /usr/sbin/opensips[8551]: INFO:tls_mgm:get_ssl_ctx_verify_mode: server verification activated. Jul 9 02:29:30 test /usr/sbin/opensips[8551]: NOTICE:tls_mgm:init_tls_dom: no CA dir for tls 'test-cli' defined, using default '/etc/pki/CA/' Jul 9 02:29:30 test /usr/sbin/opensips[8551]: NOTICE:tls_mgm:init_tls_dom: no crl for tls, using none Jul 9 02:29:30 test /usr/sbin/opensips[8551]: DBG:core:count_module_procs: modules require 2 extra processes Jul 9 02:29:30 test /usr/sbin/opensips[8551]: CRITICAL:core:sig_usr: segfault in attendant (starter) process! Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] multi domain TLS in opensips 3.1
Thank you Răzvan, that solved it! In OpenSIPS 3.1, the tls_handshake_timeout is no longer specified in the tls_module, but in each module that uses tls[1]. Therefore, most likely, you are looking at this parameter[2]. [1] https://www.opensips.org/Documentation/Migration-3-0-0-to-3-1-0#toc15 [2] https://opensips.org/docs/modules/3.1.x/proto_tls.html#param_tls_handshake_timeout Best regards, ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] multi domain TLS in opensips 3.1
Hi,
I'm trying to get multi domain TLS with MS Teams going and kind of stuck at the
beginning.
According to MS Teams interconnect tutorial tls_handshake_timeout shall be set
to 300. Setting this parameter independent from TLS domain gives an error that
parameter is not found.
#modparam("tls_mgm", "tls_handshake_timeout", "300")
# generic TLS server domain, if the client does not provide SNI
modparam("tls_mgm", "server_domain", "test")
modparam("tls_mgm", "match_ip_address", "[test]*")
modparam("tls_mgm", "match_sip_domain", "[test]none")
modparam("tls_mgm", "certificate", "[test]/etc/ssl/private/test.crt")
modparam("tls_mgm", "private_key", "[test]/etc/ssl/private/test.key")
modparam("tls_mgm", "ca_list", "[test]/etc/ssl/private/test-ca.pem")
modparam("tls_mgm", "tls_method", "[test]TLSv1-")
modparam("tls_mgm", "verify_cert", "[test]0")
modparam("tls_mgm", "require_cert", "[test]0")
# MS Teams TLS config
modparam("tls_mgm", "server_domain", "test_dom")
modparam("tls_mgm", "match_ip_address", "[test_dom]*")
modparam("tls_mgm", "match_sip_domain", "[test_dom]sip4teams.test.com")
#modparam("tls_mgm", "tls_handshake_timeout", [test_dom]300)
modparam("tls_mgm", "certificate", "[test_dom]/etc/ssl/private/test.crt")
modparam("tls_mgm", "private_key", "[test_dom]/etc/ssl/private/test.key")
modparam("tls_mgm", "ca_list", "[test_dom]/etc/ssl/private/test-ca.pem")
modparam("tls_mgm", "tls_method", "[test_dom]TLSv1_2")
modparam("tls_mgm", "verify_cert", "[test_dom]1")
modparam("tls_mgm", "require_cert", "[test_dom]1")
Jul 4 22:17:34 sip4teams opensips: INFO:tls_mgm:mod_load: openssl version:
OpenSSL 1.1.1d 10 Sep 2019
Jul 4 22:17:34 sip4teams opensips: ERROR:core:set_mod_param_regex: parameter
not found in module
Jul 4 22:17:34 sip4teams opensips: Traceback (last included file at the
bottom):
Jul 4 22:17:34 sip4teams opensips: 0. /etc/opensips/opensips.cfg
Jul 4 22:17:34 sip4teams opensips: CRITICAL:core:yyerror: parse error in
/etc/opensips/opensips.cfg:61:21-22: Parameter not found in module - can't set
Jul 4 22:17:34 sip4teams opensips: #set global tls parameters
Jul 4 22:17:34 sip4teams opensips:
Jul 4 22:17:34 sip4teams opensips: modparam("tls_mgm",
"tls_handshake_timeout", 300)
Jul 4 22:17:34 sip4teams opensips: ^~
Jul 4 22:17:34 sip4teams opensips:
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Access to parameters from generic headers
Hi Bogdan,
works perfectly, dunno why I did not find it earlier.
Thanks!
-Original Message-
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Wednesday, April 08, 2020 12:20 PM
To: OpenSIPS users mailling list ; xaled
Subject: Re: [OpenSIPS-Users] Access to parameters from generic headers
Hi,
Try to use the param transformation
https://opensips.org/Documentation/Script-Tran-3-0#toc60
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/8/20 12:32 PM, xaled wrote:
> Hi,
>
> I'm having problems with accessing values of header parameters. I tried to
> use regex to extract cause value from Reason header, but it does not work
> properly. I'm not an regex expert so the regex could wrong. It would be good
> to have a generic mechanism for this type of values extraction from header
> parameters.
>
> Reason: Q.850;cause=1;text="Unallocated (unassigned) number",
> SIP;cause=500;text="Server internal error"
>
> $var(cause_reg) = "/(.*)cause=(.*);(.*)/\2/i";
> $var(cause) = $(hdr(Reason){re.subst,$var(cause_reg)});
>
> I added a feature request some time ago for this issue:
> https://github.com/OpenSIPS/opensips/issues/1289
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Access to parameters from generic headers
Hi,
I'm having problems with accessing values of header parameters. I tried to use
regex to extract cause value from Reason header, but it does not work properly.
I'm not an regex expert so the regex could wrong. It would be good to have a
generic mechanism for this type of values extraction from header parameters.
Reason: Q.850;cause=1;text="Unallocated (unassigned) number",
SIP;cause=500;text="Server internal error"
$var(cause_reg) = "/(.*)cause=(.*);(.*)/\2/i";
$var(cause) = $(hdr(Reason){re.subst,$var(cause_reg)});
I added a feature request some time ago for this issue:
https://github.com/OpenSIPS/opensips/issues/1289
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Use of multiple outgoing TCP Trunks with B2B
Hello, We have a use case with some specific requirements on the TCP connection usage by the outgoing register trunk. Requirements are imposed by the service provider and cannot be modified by us. a) Trunk must use TCP. b) There has to be a registration over an established TCP connection. c) INVITEs can be send only over established TCP connection that was previously used for successful registration. I managed to get around this limitations by using uac_registrant and b2b modules. I also set tcp_connection_lifetime=3600 to have the TCP connection open for a pretty long time between possible SIP communications. B2B module reuses TCP connection established by uac_registrant and it works so far. Now there is another limitation on this trunk and it is the number of parallel calls. We need more parallel calls then a single trunk is allowed to have. We can have additional trunks and multiply the capacity. I added additional trunk credentials to the uac_registrant DB and multiple registrations are successfully established. Here come the problems: 1) outgoing INVITE does not reuse any of the established TCP connection. Instead the new TCP connection is established. 2) Even if INVITE would reuse one of the established TCP connections the credentials used by INVITE have to match the ones that were used during the registration. Is there anything that can be done to correlate TCP connections and credentials between uac_registrant and B2B modules? In our case It would be enough to have a random pick of registered trunk with established TCP connection and relevant credentials for every forwarded INVITE to use additional capacity given by additional trunks. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi Bogdan,
I found the source of the problem. It is the use of localhost to connect to
local postgresql database.
I changed it to 127.0.0.1 and opensips starts fast and without warnings.
before:
modparam("db_virtual", "db_urls", "postgres://user:pass@localhost/db")
after:
modparam("db_virtual", "db_urls", "postgres://user:pass@127.0.0.1/db")
There is this warning I don’t understand:
Nov 8 09:52:40 fra-appsrv01 /usr/local/sbin/opensips[12635]:
WARNING:avpops:avpops_db_bind: async() calls for
DB URL [default] will work in normal mode due to driver limitations
And once or twice a day I get timer warnings, but it is way better than it was
before.
Nov 8 09:59:45 fra-appsrv01 /usr/local/sbin/opensips[12640]:
WARNING:core:handle_timer_job: timer job has a 7 us delay in execution
Nov 8 09:59:45 fra-appsrv01 /usr/local/sbin/opensips[12641]:
WARNING:core:handle_timer_job: timer job has a 7 us delay in execution
Nov 8 18:10:10 fra-appsrv01 /usr/local/sbin/opensips[12640]:
WARNING:core:handle_timer_job: timer job has a 6 us delay in execution
Nov 8 18:10:10 fra-appsrv01 /usr/local/sbin/opensips[12640]:
WARNING:core:handle_timer_job: timer job has a 6 us delay in execution
Nov 8 18:10:10 fra-appsrv01 /usr/local/sbin/opensips[12640]:
WARNING:core:handle_timer_job: timer job has a 6 us delay in execution
Thanks,
Xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Friday, November 09, 2018 3:00 PM
To: xaled ; users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi Xaled,
(switching back to the list)
Again, it seems to be related to your postgres server - the backtrace shows
that all opensips procs are stuck while trying to connect to the postgres
server. Why the connect phase takes so long? not sure, it is a postgres stuff.
Try setting this param to 1 or 2:
http://www.opensips.org/html/docs/modules/2.4.x/db_postgres.html#param_timeout
And see how it works.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
http://opensips.org/training/OpenSIPS_Bootcamp_2018/
On 11/08/2018 12:14 PM, xaled wrote:
Hi Bogdan,
here is the compiled version from git sources:
root@fra-appsrv01:/usr/local/etc/opensips# /usr/local/sbin/opensips -V
version: opensips 2.4.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: a9b9169
main.c compiled on 19:30:38 Nov 7 2018 with gcc 4.9.2
and here is the debian repo version:
root@fra-appsrv01:/usr/local/etc/opensips# /usr/sbin/opensips -V
version: opensips 2.4.2 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
main.c compiled on with gcc 4.9.2
Greetings,
Xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Thursday, November 08, 2018 10:21 AM
To: xaled <mailto:xa...@web.de>
Subject: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi Xaled,
What's the exact version / revision of OpenSIPS you are using ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
http://opensips.org/training/OpenSIPS_Bootcamp_2018/
On 11/08/2018 01:44 AM, xaled wrote:
Hi Bogdan,
Is there something you can recommend to debug and fix it?
The database is in the same VM as opensips and there are never time out
warnings during the actual database access. Warnings come either at startup, or
randomly if opensips gets through startup phase.
I will take a closer look at the database connection performance. It makes no
sense to me though, that warning flood started after migrating the opensips VM
to a newer hardware without changing anything else and then partially stopped
after using compiled version of opensips vs installed from Debian repo on the
same VM.
The older Debian VM with the same opensips/db setup on a different physical
server does not have the startup warning flood at all. Only random warning
during run time.
Appreciate your time,
Xaled
On Nov 7, 2018 22:18, Bogdan-Andrei Iancu <mailto:bog...@opensips.org>
wrote:
Hi Xaled,
As I suspected, all the worker processes in OpenSIPS are blocked in the
startup sequence (so called child_init routine) trying to connect to the
postgres database. This is holding up without rejecting or accepting the
connection from Ope
Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi Johan, I used standard Debian repos for the installation. Things were ok until vm was migrated to new hardware. thanks, xaled On Johan De Clercq , Oct 30, 2018 19:13 wrote: Xaled, Please use the correct default and init.d package for your distro. They are in your src/opensips/packages I believe Outlook voor iOS downloaden  Van: Users namens Bogdan-Andrei Iancu Verzonden: dinsdag, oktober 30, 2018 6:06 PM Aan: OpenSIPS users mailling list; xaled Onderwerp: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task  Hi Xaled, Do you use a startup route where you do some some long-lasting ops ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Bootcamp 2018 http://opensips.org/training/OpenSIPS_Bootcamp_2018/ On 10/30/2018 06:52 PM, xaled wrote: > Hi, > > changed the avp_db_query to async mode and it did not help. I also get the "calls for DB URL [default] will work in normal mode due to driver limitations" warning that I don’t quite understand. Does it mean that async mode will not work? If yes then why? > > Oct 30 17:46:32 fra-appsrv01 /usr/sbin/opensips[17100]: WARNING:avpops:avpops_db_bind: async() calls for DB URL [default] will work in normal mode due to driver limitations > ... > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 490 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 590 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 680 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 780 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 880 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 980 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1080 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1180 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1280 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1380 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1480 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1580 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1680 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1780 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1870 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1970 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:timer_ticker: timer task already scheduled for 980 ms (now 1970 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:timer_ticker: timer task already scheduled for 980 ms (now 1970 ms), it may overlap > .. > > Thanks, > xaled > -Original Message- > From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of xaled > Sent: Tuesday, October 30, 2018 3:08 PM > To: 'OpenSIPS users mailling list' > Subject: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task > > Hi, > > any hints on
Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi Bogdan, no. Thanks xaled -Original Message- From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Tuesday, October 30, 2018 6:04 PM To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task Hi Xaled, Do you use a startup route where you do some some long-lasting ops ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Bootcamp 2018 http://opensips.org/training/OpenSIPS_Bootcamp_2018/ On 10/30/2018 06:52 PM, xaled wrote: > Hi, > > changed the avp_db_query to async mode and it did not help. I also get the > "calls for DB URL [default] will work in normal mode due to driver > limitations" warning that I don’t quite understand. Does it mean that async > mode will not work? If yes then why? > > Oct 30 17:46:32 fra-appsrv01 /usr/sbin/opensips[17100]: > WARNING:avpops:avpops_db_bind: async() calls for DB URL [default] will work > in normal mode due to driver limitations > ... > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 290 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 390 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 490 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 590 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 680 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 780 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 880 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 980 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1080 ms), it may overlap.. > Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1180 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1280 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1380 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1480 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1580 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1680 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1780 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1870 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:utimer_ticker: utimer task already scheduled for 190 > ms (now 1970 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:timer_ticker: timer task already scheduled for 980 ms > (now 1970 ms), it may overlap.. > Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: > WARNING:core:timer_ticker: timer task already scheduled for > 980 ms (now 1970 ms), it may overlap > .. > > Thanks, > xaled > -Original Message- > From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of xaled > Sent: Tuesday, October 30, 2018 3:08 PM > To: 'OpenSIPS users mailling list' > Subject: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task > > > Hi, > > any hints on this issue? > > Thanks, > xaled > > -Original Message
Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi, changed the avp_db_query to async mode and it did not help. I also get the "calls for DB URL [default] will work in normal mode due to driver limitations" warning that I don’t quite understand. Does it mean that async mode will not work? If yes then why? Oct 30 17:46:32 fra-appsrv01 /usr/sbin/opensips[17100]: WARNING:avpops:avpops_db_bind: async() calls for DB URL [default] will work in normal mode due to driver limitations ... Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 490 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 590 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 680 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 780 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 880 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 980 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1080 ms), it may overlap.. Oct 30 17:46:33 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1180 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1280 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1380 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1480 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1580 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1680 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1780 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1870 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 1970 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:timer_ticker: timer task already scheduled for 980 ms (now 1970 ms), it may overlap.. Oct 30 17:46:34 fra-appsrv01 /usr/sbin/opensips[17103]: WARNING:core:timer_ticker: timer task already scheduled for 980 ms (now 1970 ms), it may overlap .. Thanks, xaled -Original Message- From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of xaled Sent: Tuesday, October 30, 2018 3:08 PM To: 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task Hi, any hints on this issue? Thanks, xaled -Original Message- From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of xaled Sent: Wednesday, October 10, 2018 7:05 PM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task Hi, we are having a problem with warning messages that are flooding the log since we migrated the VM with opensips to a newer hardware. We had the same warnings on the previous hardware but they were coming 10 times a day and did not bother us. What we found is that the warning go away if we comment out the single avp_db_query that is being used in our config. The avp_db_query is not executed at the start, but only when specific header is present. Yet the fooding start immediately after opensips start. The mere presence of the avp_db_query function in config without execution is enough to have the issue. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.
Re: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi, any hints on this issue? Thanks, xaled -Original Message- From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of xaled Sent: Wednesday, October 10, 2018 7:05 PM To: 'OpenSIPS users mailling list' Subject: [OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task Hi, we are having a problem with warning messages that are flooding the log since we migrated the VM with opensips to a newer hardware. We had the same warnings on the previous hardware but they were coming 10 times a day and did not bother us. What we found is that the warning go away if we comment out the single avp_db_query that is being used in our config. The avp_db_query is not executed at the start, but only when specific header is present. Yet the fooding start immediately after opensips start. The mere presence of the avp_db_query function in config without execution is enough to have the issue. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. root@fra-appsrv01:/var/log/opensips# opensips -V version: opensips 2.4.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll, sigio_rt, select. main.c compiled on with gcc 4.9.2 Thanks, xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] WARNING:core:utimer_ticker: utimer task
Hi, we are having a problem with warning messages that are flooding the log since we migrated the VM with opensips to a newer hardware. We had the same warnings on the previous hardware but they were coming 10 times a day and did not bother us. What we found is that the warning go away if we comment out the single avp_db_query that is being used in our config. The avp_db_query is not executed at the start, but only when specific header is present. Yet the fooding start immediately after opensips start. The mere presence of the avp_db_query function in config without execution is enough to have the issue. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 290 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. Oct 10 11:47:28 fra-appsrv01 /usr/sbin/opensips[30461]: WARNING:core:utimer_ticker: utimer task already scheduled for 190 ms (now 390 ms), it may overlap.. root@fra-appsrv01:/var/log/opensips# opensips -V version: opensips 2.4.2 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll, sigio_rt, select. main.c compiled on with gcc 4.9.2 Thanks, xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Postgres and virtual DB errors during restart
Hi Bogdan, Ok, thanks. XaledOn Mar 2, 2018 11:25, Bogdan-Andrei Iancu wrote: Hi, Well, when you restart OpenSIPS all the DB connections will be terminated (killed by OpenSIPS) - and the effect you get on the server side are the logs you see. I agree that OpenSIPS should do a graceful DB conn termination, but this is a simple beautification at this point. Still, we have it on the plan. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 03/01/2018 05:52 PM, xaled wrote: Hi, I’m using postgres with virtual_db module and after opensips restarts I’m getting “Connection reset by peer” errors in postgres logs. The errors don’t not seem to influence the DB connection after restart, but still kind of annoying. Is there something I could do about it? 2018-03-01 15:41:47.599 CET [14600] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.603 CET [14604] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.603 CET [14590] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.605 CET [14603] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.605 CET [14588] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.606 CET [14607] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.607 CET [14601] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.609 CET [14592] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.610 CET [14606] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.611 CET [14597] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.611 CET [14591] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.612 CET [14595] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.614 CET [14605] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.614 CET [14576] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.616 CET [14585] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.617 CET [14580] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.617 CET [14596] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.619 CET [14594] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.619 CET [14598] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.620 CET [14567] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.620 CET [14593] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.621 CET [14608] user@sipapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.622 CET [14587] user@webapp LOG: could not receive data from client: Connection reset by peer 2018-03-01 15:41:47.623 CET [14574] user@webapp LOG: could not receive data from client: Connection reset by
[OpenSIPS-Users] Postgres and virtual DB errors during restart
postgres: 10/main: user webapp 127.0.0.1(40702) idle 14671 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40704) idle 14672 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40706) idle 14673 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40708) idle 14674 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40710) idle 14675 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40712) idle 14676 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40714) idle 14677 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40716) idle 14678 ?Ss 0:00 postgres: 10/main: user webapp 127.0.0.1(40718) idle 14679 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40720) idle 14680 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40722) idle 14681 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40724) idle 14682 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40726) idle 14683 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40728) idle 14684 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40730) idle 14685 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40732) idle 14686 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40734) idle 14687 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40736) idle 14688 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40738) idle 14689 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40740) idle 14690 ?Ss 0:00 postgres: 10/main: user sipapp 127.0.0.1(40742) idle version: opensips 2.3.3 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. main.c compiled on with gcc 6.3.0 PostgreSQL 10.2 (Debian 10.2-1.pgdg90+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 6.3.0-18) 6.3.0 20170516, 64-bit SET:: i=0 name=set1 mode=FAILOVER DB:: j=0 name=postgres://user:xxx@127.0.0.1/webapp can=1 may=1 r_rec=0 SET:: i=1 name=set2 mode=FAILOVER DB:: j=0 name=postgres://user:xxx@127.0.0.1/sipapp can=1 may=1 r_rec=0 Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Wrong number of children
Hi Bodgan, thanks, now there are no unwanted TCP children ;) Number of SIP receiver UDP children matches the children param value. ivr01:/usr/local/etc/opensips # /usr/local/sbin/opensipsctl fifo ps Process:: ID=0 PID=12872 Type=attendant Process:: ID=1 PID=12873 Type=MI FIFO Process:: ID=2 PID=12874 Type=time_keeper Process:: ID=3 PID=12875 Type=timer Process:: ID=4 PID=12876 Type=SIP receiver udp: x.x.x.x:5060 Process:: ID=5 PID=12878 Type=SIP receiver udp: x.x.x.x:5060 Process:: ID=6 PID=12879 Type=SIP receiver udp: x.x.x.x:5060 Process:: ID=7 PID=12880 Type=SIP receiver udp: x.x.x.x:5060 Process:: ID=8 PID=12881 Type=Timer handler Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Tuesday, February 27, 2018 6:39 PM To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] Wrong number of children Ok, thanks to Razvan, we have an fix for this: https://github.com/OpenSIPS/opensips/commit/b022ad5a7c1c24aa9cf3ddf22d5f50510807c9f4 Please update from GIT and give it a try. Many Thanks, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/27/2018 06:38 PM, Bogdan-Andrei Iancu wrote: Thank you Xaled, Based on the output you provided I managed to identify the issue. There is a tricky internal test that actually forces the TCP layer to start more or less all the time. Let us have this fixed !! I will update you Best regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/27/2018 06:30 PM, xaled wrote: Hi Bogdan, It’s a different server, but the same tcp issue: 2018-02-27T17:19:29.939207+01:00 dus-ivr01 opensips: DBG:core:main: Loaded 1 transport protocols 2018-02-27T17:19:29.939411+01:00 dus-ivr01 opensips: DBG:core:socket2str: 2018-02-27T17:19:29.939630+01:00 dus-ivr01 opensips: INFO:core:tcp_init: enabling TCP for proto 5 2018-02-27T17:19:29.939842+01:00 dus-ivr01 opensips: DBG:core:ipc_register_handler: IPC type 0 [TCP reporting] registered with handler 0x5f9fee 2018-02-27T17:19:29.940120+01:00 dus-ivr01 opensips: DBG:core:create_status_pipe: pipe created ? rc = 0, errno = Success 2018-02-27T17:19:29.940326+01:00 dus-ivr01 opensips: DBG:core:daemonize: waiting for status code from children 2018-02-27T17:19:29.940526+01:00 dus-ivr01 opensips: DBG:core:count_init_children: 15 children are going to be inited 2018-02-27T17:19:29.940724+01:00 dus-ivr01 /usr/local/sbin/opensips[13076]: DBG:core:set_core_dump: core dump limits set to 18 446744073709551615 2018-02-27T17:19:29.940951+01:00 dus-ivr01 /usr/local/sbin/opensips[13076]: NOTICE:core:main: version: opensips 2.3.3 (x86_64/ linux) Do you need full logs, or is this enough? Thanks, Xale From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, February 26, 2018 10:38 PM To: xaled <mailto:xa...@web.de> Subject: Re: [OpenSIPS-Users] Wrong number of children Please apply the below patch, recompile and send again the startup logs: diff --git a/net/net_tcp.c b/net/net_tcp.c index 2dbea49..2d63940 100644 --- a/net/net_tcp.c +++ b/net/net_tcp.c @@ -1624,7 +1624,7 @@ int tcp_init(void) /* first we do auto-detection to see if there are any TCP based * protocols loaded */ for ( i=PROTO_FIRST ; ihttp://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/26/2018 08:14 PM, xaled wrote: Hi Bogdan, would a full debug log will be sufficient? The config is spread across quite a few files. Thanks, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, February 26, 2018 5:25 PM To: xaled <mailto:xa...@web.de> ; 'OpenSIPS users mailling list' <mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] Wrong number of children Hmm that is strange. Could you send me (off list) your cfg to give it a try - I see you use the 2.3.3 version , right ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/26/2018 06:27 PM, xaled wrote: Nothing root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps Process:: ID=0 PID=14966 Type=attendant Process:: ID=1 PID=14967 Type=MI FIFO Process:: ID=2 PID=14968 Type=time_keeper Process:: ID=3 PID=14969 Type=timer Process:: ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=8 PID=14978 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=9 PID=14979 Type=TCP receiver Pro
Re: [OpenSIPS-Users] Wrong number of children
Hi Bogdan,
Glad I could help with this one.
XaledOn Feb 27, 2018 17:39, Bogdan-Andrei Iancu wrote:
Thank you Xaled,
Based on the output you provided I managed to identify the issue.
There is a tricky internal test that actually forces the TCP layer
to start more or less all the time.
Let us have this fixed !! I will update you
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 02/27/2018 06:30 PM, xaled wrote:
Hi Bogdan,
It’s a different server, but the same tcp
issue:
2018-02-27T17:19:29.939207+01:00 dus-ivr01
opensips: DBG:core:main: Loaded 1 transport protocols
2018-02-27T17:19:29.939411+01:00 dus-ivr01
opensips: DBG:core:socket2str:
2018-02-27T17:19:29.939630+01:00 dus-ivr01
opensips: INFO:core:tcp_init: enabling TCP for proto 5
2018-02-27T17:19:29.939842+01:00 dus-ivr01
opensips: DBG:core:ipc_register_handler: IPC type 0 [TCP
reporting] registered with
handler 0x5f9fee
2018-02-27T17:19:29.940120+01:00 dus-ivr01
opensips: DBG:core:create_status_pipe: pipe created ? rc =
0, errno = Success
2018-02-27T17:19:29.940326+01:00 dus-ivr01
opensips: DBG:core:daemonize: waiting for status code from
children
2018-02-27T17:19:29.940526+01:00 dus-ivr01
opensips: DBG:core:count_init_children: 15 children are
going to be inited
2018-02-27T17:19:29.940724+01:00 dus-ivr01
/usr/local/sbin/opensips[13076]: DBG:core:set_core_dump:
core dump limits set to 18
446744073709551615
2018-02-27T17:19:29.940951+01:00 dus-ivr01
/usr/local/sbin/opensips[13076]: NOTICE:core:main: version:
opensips 2.3.3 (x86_64/
linux)
Do you need full logs, or is this enough?
Thanks,
Xale
From: Bogdan-Andrei Iancu
[mailto:bog...@opensips.org]
Sent: Monday, February 26, 2018 10:38 PM
To: xaled
Subject: Re: [OpenSIPS-Users] Wrong number of
children
Please
apply the below patch, recompile and send again the
startup logs:
diff --git a/net/net_tcp.c b/net/net_tcp.c
index 2dbea49..2d63940 100644
--- a/net/net_tcp.c
+++ b/net/net_tcp.c
@@ -1624,7 +1624,7 @@ int tcp_init(void)
/* first we do auto-detection to see if there
are any TCP based
* protocols loaded */
for ( i=PROTO_FIRST ; i
- if (is_tcp_based_proto(i))
{tcp_disabled=0;break;}
+ if (is_tcp_based_proto(i))
{LM_INFO("enabling TCP for proto
%d\n",i);tcp_disabled=0;break;}
if (tcp_disabled)
return 0;
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 02/26/2018 08:14 PM, xaled wrote:
Hi
Bogdan,
would a full debug log will be sufficient?
The config is spread across quite a few
files.
Thanks,
Xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Monday, February 26, 2018 5:25 PM
To: xaled ;
'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] Wrong number of
children
Hmm that is strange.
Could you send me (off list) your cfg to give it a try - I
see you use the 2.3.3 version , right ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 02/26/2018 0
Re: [OpenSIPS-Users] Wrong number of children
Nothing root@dus-appsrv01:/etc/opensips# opensipsctl fifo ps Process:: ID=0 PID=14966 Type=attendant Process:: ID=1 PID=14967 Type=MI FIFO Process:: ID=2 PID=14968 Type=time_keeper Process:: ID=3 PID=14969 Type=timer Process:: ID=4 PID=14970 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=5 PID=14975 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=6 PID=14976 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=7 PID=14977 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=8 PID=14978 Type=SIP receiver udp:1.2.3.4:5060 Process:: ID=9 PID=14979 Type=TCP receiver Process:: ID=10 PID=14982 Type=TCP receiver Process:: ID=11 PID=14984 Type=TCP receiver Process:: ID=12 PID=14985 Type=TCP receiver Process:: ID=13 PID=14986 Type=TCP receiver Process:: ID=14 PID=14987 Type=TCP receiver Process:: ID=15 PID=14988 Type=TCP receiver Process:: ID=16 PID=14989 Type=TCP receiver Process:: ID=17 PID=14991 Type=Timer handler Process:: ID=18 PID=14992 Type=TCP main root@srv01:/etc/opensips# netstat -tlnp | grep opensips root@srv01:/etc/opensips# Thanks, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, February 26, 2018 4:57 PM To: xaled ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] Wrong number of children If you do "netstat -tlnp | grep opensips", what do you get ? The TCP layer automatically enable itself if a TCP-based protocol is used from the OpenSIPS config (as listener), like SIP TCP/TLS/WS/WSS , HEP or BIN. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/26/2018 05:53 PM, xaled wrote: Hi Bogdan, nope, non of them. Greetings, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, February 26, 2018 4:41 PM To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> ; xaled <mailto:xa...@web.de> Subject: Re: [OpenSIPS-Users] Wrong number of children Hi Xaled, Do you use HEP for tracing or BIN for replication ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/26/2018 01:36 PM, xaled wrote: Hi Callum, that helped thanks. I have 8 TCP receivers and one TCP main process that I did not expected as I only listen on udp. Will have to understand the TCP spawn logic. Greetings, Xaled From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy Sent: Friday, February 23, 2018 2:42 PM To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] Wrong number of children Hi Xaled, If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the instance to see full details of each process. https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7 Hope that helps, Callum On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti mailto:daniel.zanu...@gmail.com> > wrote: Hi You should have 5 per interface + some internal control threads. I'm not sure exactly. Regards On Fri, Feb 23, 2018 at 9:25 AM, xaled mailto:xa...@web.de> > wrote: Hi I have configured 5 children in opensips.cfg, but 16 get logged and 18 initiated what could be the cause of it? I search for word children in opensips directory and it only comes ones in opensips.conf. children=5 Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code from children Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are going to be inited root@dus-appsrv01:/var/log/opensips# ps ax|grep sips 14854 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14856 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14857 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14858 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14861 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14862 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14863 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14864 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14865 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14867 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/
Re: [OpenSIPS-Users] Wrong number of children
Hi Bogdan, nope, non of them. Greetings, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Monday, February 26, 2018 4:41 PM To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] Wrong number of children Hi Xaled, Do you use HEP for tracing or BIN for replication ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/26/2018 01:36 PM, xaled wrote: Hi Callum, that helped thanks. I have 8 TCP receivers and one TCP main process that I did not expected as I only listen on udp. Will have to understand the TCP spawn logic. Greetings, Xaled From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy Sent: Friday, February 23, 2018 2:42 PM To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> Subject: Re: [OpenSIPS-Users] Wrong number of children Hi Xaled, If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the instance to see full details of each process. https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7 Hope that helps, Callum On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti mailto:daniel.zanu...@gmail.com> > wrote: Hi You should have 5 per interface + some internal control threads. I'm not sure exactly. Regards On Fri, Feb 23, 2018 at 9:25 AM, xaled mailto:xa...@web.de> > wrote: Hi I have configured 5 children in opensips.cfg, but 16 get logged and 18 initiated what could be the cause of it? I search for word children in opensips directory and it only comes ones in opensips.conf. children=5 Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code from children Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are going to be inited root@dus-appsrv01:/var/log/opensips# ps ax|grep sips 14854 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14856 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14857 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14858 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14861 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14862 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14863 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14864 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14865 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14867 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14869 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14870 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14871 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14872 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14874 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14875 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14876 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14877 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 With commended children parameter I get 19 children in the log and 21 in reality: Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for status code from children Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19 children are going to be inited root@srv01:/var/log/opensips# ps ax|grep sips 14723 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14725 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14726 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14727 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14730 ?
Re: [OpenSIPS-Users] Wrong number of children
Hi Callum, that helped thanks. I have 8 TCP receivers and one TCP main process that I did not expected as I only listen on udp. Will have to understand the TCP spawn logic. Greetings, Xaled From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Callum Guy Sent: Friday, February 23, 2018 2:42 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Wrong number of children Hi Xaled, If you have the FIFO module loaded you can run "opensipsctl fifo ps" on the instance to see full details of each process. https://www.opensips.org/Documentation/Interface-CoreMI-2-2#toc7 Hope that helps, Callum On Fri, Feb 23, 2018 at 1:35 PM Daniel Zanutti mailto:daniel.zanu...@gmail.com> > wrote: Hi You should have 5 per interface + some internal control threads. I'm not sure exactly. Regards On Fri, Feb 23, 2018 at 9:25 AM, xaled mailto:xa...@web.de> > wrote: Hi I have configured 5 children in opensips.cfg, but 16 get logged and 18 initiated what could be the cause of it? I search for word children in opensips directory and it only comes ones in opensips.conf. children=5 Feb 23 13:07:09 srv01 opensips: DBG:core:daemonize: waiting for status code from children Feb 23 13:07:09 srv01 opensips: DBG:core:count_init_children: 16 children are going to be inited root@dus-appsrv01:/var/log/opensips# ps ax|grep sips 14854 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14856 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14857 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14858 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14861 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14862 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14863 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14864 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14865 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14867 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14869 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14870 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14871 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14872 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14874 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14875 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14876 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14877 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 With commended children parameter I get 19 children in the log and 21 in reality: Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:daemonize: waiting for status code from children Feb 23 13:13:24 dus-appsrv01 opensips: DBG:core:count_init_children: 19 children are going to be inited root@srv01:/var/log/opensips# ps ax|grep sips 14723 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14725 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14726 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14727 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14730 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14731 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14732 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14733 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14734 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4
[OpenSIPS-Users] Wrong number of children
/run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14748 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14749 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 14750 ?S 0:00 /usr/sbin/opensips -P /run/opensips/opensips.pid -f /etc/opensips/opensips.cfg -m 64 -M 4 root@srv01:/etc/opensips# opensips -V version: opensips 2.3.3 (x86_64/linux) flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC, FAST_LOCK-ADAPTIVE_WAIT ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535 poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. main.c compiled on with gcc 6.3.0 Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Per phone number statistics
Hello Ben, thank you for the advice. I will take a look at the module. Never actually used it bevor. Thanks, Xaled From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Ben Newlin Sent: Wednesday, February 21, 2018 5:34 PM To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Per phone number statistics I would recommend using Dialog profiling. http://www.opensips.org/html/docs/modules/2.3.x/dialog.html#idp158208 Ben Newlin From: Users mailto:users-boun...@lists.opensips.org> > on behalf of xaled mailto:xa...@web.de> > Reply-To: OpenSIPS users mailling list mailto:users@lists.opensips.org> > Date: Wednesday, February 21, 2018 at 11:13 AM To: 'OpenSIPS users mailling list' mailto:users@lists.opensips.org> > Subject: [OpenSIPS-Users] Per phone number statistics Hello, What is a good way of collecting and accessing per phone number (A or B side) statistics? For example current number of simultaneous calls to a particular phone number. The best I could come up is to use radius accounting and then do SQL queries on the accounting data. SNMP stats don’t seem to allow per number statistic collection. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Per phone number statistics
Hello, What is a good way of collecting and accessing per phone number (A or B side) statistics? For example current number of simultaneous calls to a particular phone number. The best I could come up is to use radius accounting and then do SQL queries on the accounting data. SNMP stats don't seem to allow per number statistic collection. Thanks, Xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] history-Info header manipulation
Hi Bogdan, ok, thank you for the info. It would be great to have a generic method of accessing such multipart headers. Greetings, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Wednesday, February 21, 2018 3:57 PM To: xaled ; 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] history-Info header manipulation Hi Xaled, There were recently some fixes in regards to such headers - multi body name-addr like. Internally the parser is able to handle it (the fixes I mentioned were related to PAI/PPI hdr parsing). Still, from script level there is no way (yet) to get access to each body part, via variables or transformations :( Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/20/2018 02:51 PM, xaled wrote: Hi Bogdan, Mostly yes - single HI Header with multiple hi-entries. A general solution/advice that would work with both single and multiple HI headers would be much appreciated. Thanks, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Tuesday, February 20, 2018 1:15 PM To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> ; xaled <mailto:xa...@web.de> Subject: Re: [OpenSIPS-Users] history-Info header manipulation Hi Xaled, You mean if a single History header contains multiple hi-entry instances ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/19/2018 02:39 PM, xaled wrote: Hi, Is there any other/better way for the history-Info header manipulation like adding or removing a hi-entry except subst? Thanks, xaled ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] history-Info header manipulation
Hi Bogdan, Mostly yes - single HI Header with multiple hi-entries. A general solution/advice that would work with both single and multiple HI headers would be much appreciated. Thanks, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Tuesday, February 20, 2018 1:15 PM To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] history-Info header manipulation Hi Xaled, You mean if a single History header contains multiple hi-entry instances ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/19/2018 02:39 PM, xaled wrote: Hi, Is there any other/better way for the history-Info header manipulation like adding or removing a hi-entry except subst? Thanks, xaled ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] history-Info header manipulation
Hi, Is there any other/better way for the history-Info header manipulation like adding or removing a hi-entry except subst? Thanks, xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] call_center module and loose routing
Hi Bogdan, thanks for an idea. I will try. Greetings, Xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Wednesday, November 22, 2017 6:17 PM To: Xaled Cc: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] call_center module and loose routing Have you tried to use the local route to identify the call to the agents (based on RURI ?) and force the SIPSERVER address in the $du ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 11/22/2017 05:44 PM, Xaled wrote: Hi Correct. Thanks, Xaled On 22 Nov 2017, at 16:09, Bogdan-Andrei Iancu mailto:bog...@opensips.org> > wrote: Hi, So you use pre-loaded route in order to send initial INVITEs from SIPSERVER to OPENSIPS, right ? And what you want to achieve is to have all the calls generated by OpenSIPS Call Center (to agents, to announcements) to actually go again via the SIPSERVER ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 11/21/2017 12:30 PM, xaled wrote: Hi Bogdan, I use opensips in an scenario where OPENSIPS is addressed from the main SIPSERVER using Route header. OPENSIPS performs different modifications on the INVITE request and gives the INVITE back to the main SIPSERVER. This works fine with the loose_route() so far. Now I want to use the call_center module for RURI agent addressing, queues, etc while still preserving the Route header based next hop routing between main SIPSERVER and OPENSIPS. Would manually parsing the Route Header at OPENSIPS, deleting first route header, saving the hostport value of the second Route header to some variable and provide it as a kind of $du to the call_center module for the next hop routing back to SIPSERVER work? For my scenario to work the Route header with the second Route header value has not to be deleted or modified by the call_center module. Here is the table showing the pseudo values of the RURI and the Route Header at the ingress of SIPSERVER and OPENSIPS respectively. SIPSERVER -> OPENSIPS -> SIPSERVER-> AGENT RURI:0800CallCenter 0800CallCenteragent agent Route: opensips, sipserver sipserver Does this make it a bit more clearer? Thanks, xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Tuesday, November 21, 2017 10:55 AM To: users@lists.opensips.org <mailto:users@lists.opensips.org> ; xaled <mailto:xa...@web.de> Subject: Re: [OpenSIPS-Users] call_center module and loose routing Hi, The routing in Call Center module is not compatible with the loose_route(). The loose_route is a mechanism used by a SIP proxy staying in the middle of a SIP session. On the other hand, the Call Center is using a SIP Back-2-Back engine in order to implement the queuing. Better try to explain what are you trying to achieve here. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 11/20/2017 04:46 PM, xaled wrote: Hi I want to use opensips with call_center module in a loose route scenario where the INVITE has to be routed by opensips to the next hop (sipserver) based on what is left from Route header after loose_route() is performed. The call_center module has to update the RURI with agent location and let the next hop from the route header perform the actual routing to the agent. Here are the expected route and RURI header values at the opensips, sipserver and agent: opensips sipserver agent RURI:0800CallCenter agentagent Route: opensips, sipserversipserver Will something like this work as described above: loose_route(); cc_handle_call(test_flow); Thanks, xaled ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] call_center module and loose routing
Hi Correct. Thanks, Xaled > On 22 Nov 2017, at 16:09, Bogdan-Andrei Iancu wrote: > > Hi, > > So you use pre-loaded route in order to send initial INVITEs from SIPSERVER > to OPENSIPS, right ? > > And what you want to achieve is to have all the calls generated by OpenSIPS > Call Center (to agents, to announcements) to actually go again via the > SIPSERVER ? > > Regards, > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com >> On 11/21/2017 12:30 PM, xaled wrote: >> Hi Bogdan, >> >> I use opensips in an scenario where OPENSIPS is addressed from the main >> SIPSERVER using Route header. OPENSIPS performs different modifications on >> the INVITE request and gives the INVITE back to the main SIPSERVER. This >> works fine with the loose_route() so far. >> >> Now I want to use the call_center module for RURI agent addressing, queues, >> etc while still preserving the Route header based next hop routing between >> main SIPSERVER and OPENSIPS. >> Would manually parsing the Route Header at OPENSIPS, deleting first route >> header, saving the hostport value of the second Route header to some >> variable and provide it as a kind of $du to the call_center module for the >> next hop routing back to SIPSERVER work? >> For my scenario to work the Route header with the second Route header value >> has not to be deleted or modified by the call_center module. >> >> Here is the table showing the pseudo values of the RURI and the Route Header >> at the ingress of SIPSERVER and OPENSIPS respectively. >> >> SIPSERVER -> OPENSIPS -> >> SIPSERVER-> AGENT >> RURI:0800CallCenter 0800CallCenteragent >> agent >> Route: >> opensips, sipserver sipserver >> >> Does this make it a bit more clearer? >> >> Thanks, >> xaled >> >> >> From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] >> Sent: Tuesday, November 21, 2017 10:55 AM >> To: users@lists.opensips.org; xaled >> Subject: Re: [OpenSIPS-Users] call_center module and loose routing >> >> Hi, >> >> The routing in Call Center module is not compatible with the loose_route(). >> >> The loose_route is a mechanism used by a SIP proxy staying in the middle of >> a SIP session. >> >> On the other hand, the Call Center is using a SIP Back-2-Back engine in >> order to implement the queuing. >> >> Better try to explain what are you trying to achieve here. >> >> Regards, >> >> Bogdan-Andrei Iancu >> OpenSIPS Founder and Developer >> http://www.opensips-solutions.com >> On 11/20/2017 04:46 PM, xaled wrote: >> Hi >> >> I want to use opensips with call_center module in a loose route scenario >> where the INVITE has to be routed by opensips to the next hop (sipserver) >> based on what is left from Route header after loose_route() is performed. >> The call_center module has to update the RURI with agent location and let >> the next hop from the route header perform the actual routing to the agent. >> >> Here are the expected route and RURI header values at the opensips, >> sipserver and agent: >> >> opensips sipserver >> agent >> RURI:0800CallCenter agentagent >> Route: opensips, sipserversipserver >> >> Will something like this work as described above: >> >> loose_route(); >> cc_handle_call(test_flow); >> >> Thanks, >> xaled >> >> >> >> ___ >> Users mailing list >> Users@lists.opensips.org >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users > ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] call_center module and loose routing
Hi Bogdan, I use opensips in an scenario where OPENSIPS is addressed from the main SIPSERVER using Route header. OPENSIPS performs different modifications on the INVITE request and gives the INVITE back to the main SIPSERVER. This works fine with the loose_route() so far. Now I want to use the call_center module for RURI agent addressing, queues, etc while still preserving the Route header based next hop routing between main SIPSERVER and OPENSIPS. Would manually parsing the Route Header at OPENSIPS, deleting first route header, saving the hostport value of the second Route header to some variable and provide it as a kind of $du to the call_center module for the next hop routing back to SIPSERVER work? For my scenario to work the Route header with the second Route header value has not to be deleted or modified by the call_center module. Here is the table showing the pseudo values of the RURI and the Route Header at the ingress of SIPSERVER and OPENSIPS respectively. SIPSERVER -> OPENSIPS -> SIPSERVER-> AGENT RURI:0800CallCenter 0800CallCenteragent agent Route: opensips, sipserver sipserver Does this make it a bit more clearer? Thanks, xaled From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Tuesday, November 21, 2017 10:55 AM To: users@lists.opensips.org; xaled Subject: Re: [OpenSIPS-Users] call_center module and loose routing Hi, The routing in Call Center module is not compatible with the loose_route(). The loose_route is a mechanism used by a SIP proxy staying in the middle of a SIP session. On the other hand, the Call Center is using a SIP Back-2-Back engine in order to implement the queuing. Better try to explain what are you trying to achieve here. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 11/20/2017 04:46 PM, xaled wrote: Hi I want to use opensips with call_center module in a loose route scenario where the INVITE has to be routed by opensips to the next hop (sipserver) based on what is left from Route header after loose_route() is performed. The call_center module has to update the RURI with agent location and let the next hop from the route header perform the actual routing to the agent. Here are the expected route and RURI header values at the opensips, sipserver and agent: opensips sipserver agent RURI:0800CallCenter agentagent Route: opensips, sipserversipserver Will something like this work as described above: loose_route(); cc_handle_call(test_flow); Thanks, xaled ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] call_center module and loose routing
Hi I want to use opensips with call_center module in a loose route scenario where the INVITE has to be routed by opensips to the next hop (sipserver) based on what is left from Route header after loose_route() is performed. The call_center module has to update the RURI with agent location and let the next hop from the route header perform the actual routing to the agent. Here are the expected route and RURI header values at the opensips, sipserver and agent: opensips sipserver agent RURI:0800CallCenter agentagent Route: opensips, sipserversipserver Will something like this work as described above: loose_route(); cc_handle_call(test_flow); Thanks, xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Feature request? Script Var / AVP variables in route function.
There could be a constrain in OpenSIPS that the route name should be defined at the start of opensips process. Otherwise if a variable value for some reason does not match any defined route there will be a problem. Greetings, xaled From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Jim DeVito Sent: Donnerstag, 21. September 2017 14:58 To: OpenSIPS users mailling list Subject: Re: [OpenSIPS-Users] Feature request? Script Var / AVP variables in route function. Hmmm. I want to use the contents of $avp(carrier_id) as the route name. So if $avp(carrier_id) is 25 I want it to call the routing block route[25]. On Thu, Sep 21, 2017 at 8:52 AM, Răzvan Crainea mailto:raz...@opensips.org> > wrote: Hi, Jim! You should have a name for the route, such as: route(route_name, $avp(carrier_id)); Best regards, Răzvan Crainea OpenSIPS Developer www.opensips-solutions.com <http://www.opensips-solutions.com> On 09/21/2017 03:43 PM, Jim DeVito wrote: Hi Razvan, So what am I doing wrong with route($avp(carrier_id)); It produces... ...line 318, column 53-54: bad routeargument Thanks!! On Thu, Sep 21, 2017 at 8:31 AM, Răzvan Crainea mailto:raz...@opensips.org> > wrote: Hi, Jim! Script variables or AVPs are PV (pseudo-variables) themselves, so you should be able to use them. Best regards, Răzvan Crainea OpenSIPS Developer www.opensips-solutions.com <http://www.opensips-solutions.com> On 09/21/2017 03:14 PM, Jim DeVito wrote: Hi All, It's my understanding only PV, integers and strings can be used in the core route function. Is there a reason I don't understand why we can not use script variables or AVP's? Thanks!! - Jim DeVito Mobile 216.507.9497 ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- - Jim DeVito Mobile 216.507.9497 ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- - Jim DeVito Mobile 216.507.9497 ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] 2.3 How to set content-disposition header with add_body_part
Hi, how can one set the content-disposition Header to the body added with add_body_part function? Thanks xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Use of colon in XML element names
Hi,
Just tried the new xml module and have some issues with colon in element names.
Should I use some escape magic for colons with opensips xml module?
Another question is how to add encoding="UTF-8" to have it like this -
It would be also great to have formatted XML output. Something like format
parameter in toString method of XML::LibXML::Document in perl.
test:/usr/local/etc/opensips # /usr/local/sbin/opensips -V
version: opensips 2.3.1 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, F_MALLOC,
FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
git revision: 72fa146
main.c compiled on 18:53:05 Aug 16 2017 with gcc 4.8
$xml(xml_s) = "";
$xml(xml_s.attr/xmlns:tns) = "http://test.org/abc/params/xml/abc";;
$xml(xml_s/tns:messageType) = "";
$xml(xml_s/tns:messageType/tns:crtg) =
"";
$xml(xml_s/tns:messageType/tns:crtg/tns:ControlIndicators) =
"5";
xlog("XML_TEST: $xml(xml_s)\n");
2017-08-20T17:46:38.320273+02:00 test /usr/local/sbin/opensips[32422]:
XML_TEST: #012
The final XML should be like this:
http://test.org/abc/params/xml/abc";>
5
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Set userpart parameter using $rU
Hi Ben,
thanks for pointing this out.
I’ll try the fix on my 2.3 opensips.
Greetings,
Xaled
From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Ben Newlin
Sent: Mittwoch, 12. Juli 2017 14:54
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Set userpart parameter using $rU
Xaled,
I ran into this issue very recently myself. Please reference this thread from
the mailing list:
http://lists.opensips.org/pipermail/users/2017-July/037666.html
Thanks,
Ben
From: Users mailto:users-boun...@lists.opensips.org> > on behalf of xaled mailto:xa...@web.de> >
Reply-To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >
Date: Wednesday, July 12, 2017 at 8:45 AM
To: 'OpenSIPS users mailling list' mailto:users@lists.opensips.org> >
Subject: [OpenSIPS-Users] Set userpart parameter using $rU
Hello,
I cannot set the userpart parameter in the RURI using $rU. The needed parameter
always becomes the URI and not userpart parameter.
rewriteuser("+1234556;rn=+1234567");
or
$rU = "+1234556;rn=+1234567";
Produces the same result with the userpart parameter becoming URI parameter:
"INVITE sip:+1234...@test.com:5080;rn=+1234567 SIP/2.0\r
Only modifying the whole URI using $ru works as needed:
$ru="sip:" + "+1234567;rn=+1234567" + "@" + "test.com";
"INVITE sip:+1234567;rn=+1234...@test.com SIP/2.0\r
Is there a reason for this behavior?
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Set userpart parameter using $rU
Hello,
I cannot set the userpart parameter in the RURI using $rU. The needed parameter
always becomes the URI and not userpart parameter.
rewriteuser("+1234556;rn=+1234567");
or
$rU = "+1234556;rn=+1234567";
Produces the same result with the userpart parameter becoming URI parameter:
"INVITE sip:+1234...@test.com:5080;rn=+1234567 SIP/2.0\r
Only modifying the whole URI using $ru works as needed:
$ru="sip:" + "+1234567;rn=+1234567" + "@" + "test.com";
"INVITE sip:+1234567;rn=+1234...@test.com SIP/2.0\r
Is there a reason for this behavior?
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] negative values in math_rpn
Hi Liviu,
thanks for pointing to the current state of math_eval. It is definitely much
more user friendly.
Googling “opensips math_eval” gave me only the 1.10 version of math_eval
documentation with only the binary operations at that time.
As usual - one should have looked better.
I was obviously stuck with the assumption that a value should always come first
in an RPN expression.
Greetings,
xaled
From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Liviu Chircu
Sent: Montag, 10. Juli 2017 13:06
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] negative values in math_rpn
I suggest you use math_eval() - it's much more human friendly. The following
should work:
$var(neg) = "-6.135";
$var(neg_int) = $(var(neg){s.int});
math_eval("abs($var(neg_int))", "$var(result)");
OTOH, if you really want to use RPN, this will fix it:
math_rpn("abs $var(neg_int)", "$var(result)");
Liviu Chircu
OpenSIPS Developer
http://www.opensips-solutions.com
On 10.07.2017 13:55, xaled wrote:
Hi,
am I doing something wrong, or can math_rpn not handle negative values?
$var(neg) = "-6.135";
$var(neg_int) = $(var(neg){s.int});
math_rpn("$var(neg_int) abs", "$avp(result)");
2017-07-10T12:47:59.804008+02:00 fra-ivr01 /usr/local/sbin/opensips[10971]:
DBG:mathops:w_evaluate_rpn: Evaluating expression: -6 abs
2017-07-10T12:47:59.804339+02:00 fra-ivr01 /usr/local/sbin/opensips[10971]:
WARNING:mathops:get_rpn_op: Parse expr error: Invalid operator! <-6>
2017-07-10T12:47:59.804669+02:00 fra-ivr01 /usr/local/sbin/opensips[10971]:
ERROR:mathops:evaluate_rpn: Failed to parse RPN!
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] negative values in math_rpn
Hi,
am I doing something wrong, or can math_rpn not handle negative values?
$var(neg) = "-6.135";
$var(neg_int) = $(var(neg){s.int});
math_rpn("$var(neg_int) abs", "$avp(result)");
2017-07-10T12:47:59.804008+02:00 fra-ivr01 /usr/local/sbin/opensips[10971]:
DBG:mathops:w_evaluate_rpn: Evaluating expression: -6 abs
2017-07-10T12:47:59.804339+02:00 fra-ivr01 /usr/local/sbin/opensips[10971]:
WARNING:mathops:get_rpn_op: Parse expr error: Invalid operator! <-6>
2017-07-10T12:47:59.804669+02:00 fra-ivr01 /usr/local/sbin/opensips[10971]:
ERROR:mathops:evaluate_rpn: Failed to parse RPN!
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Create new branch on receipt of provisional response on the main branch
Hi Bogdan,
a-ha I thought of triggering on event, but did not find an even for the
received 180 response. What I did not know, that one can simulate an event.
That is a powerful function.
Thanks,
Xaled
From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of
Bogdan-Andrei Iancu
Sent: Dienstag, 30. Mai 2017 12:30
To: OpenSIPS users mailling list
Subject: Re: [OpenSIPS-Users] Create new branch on receipt of provisional
response on the main branch
Hi Xaled,
Normally you should use the "msg" param for the inject function, to take the
new destination (to be injected) from the sip msg RURI. But you are in on_reply
route so you cannnot do this.
The only option is to use the "event" param and to manually simulate an event
by populating some AVPs:
$avp(uri) = ;
$avp(received) = ; empty string if not used
$avp(path) = ; empty string if not used
$avp(qval) = ; mandatory
$avp(bflags) = ; mandatory (use 0 as
default)
$avp(socket) = ; empty string if not used
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2017, Huston, US
http://opensips.org/training/OpenSIPS_Bootcamp_2017.html
On 05/29/2017 02:43 PM, xaled wrote:
Hi Bogdan,
Thanks of pointing this new feature out.
I’d like to have something like the script below to work by adding a branch
after receipt of 180. The problem is I don’t get the meaning of source
parameter of t_inject_branch in this scenario. Can you help me with this one?
route {
t_on_reply("global");
t_relay();
}
onreply_route[global] {
if (t_check_status("180")) {
t_inject_branch(“???”);
}
}
Thanks,
Xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Freitag, 26. Mai 2017 15:28
To: OpenSIPS users mailling list <mailto:users@lists.opensips.org>
; xaled <mailto:xa...@web.de>
Subject: Re: [OpenSIPS-Users] Create new branch on receipt of provisional
response on the main branch
Hi Xaled,
With a pre-2.3 release you cannot do this, unless you wait for the current
branches to fail, so to use the failure_route to add new branches.
With 2.3 you can do it by using the t_inject_branch() function.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2017, Huston, US
http://opensips.org/training/OpenSIPS_Bootcamp_2017.html
On 05/22/2017 09:30 PM, xaled wrote:
Hello,
I need to create a branch on receipt of provisional response on the main branch.
Doing append_brach in reply_route does not seem to work.
What is right way to do it?
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] Create new branch on receipt of provisional response on the main branch
Hi Bogdan,
Thanks of pointing this new feature out.
I’d like to have something like the script below to work by adding a branch
after receipt of 180. The problem is I don’t get the meaning of source
parameter of t_inject_branch in this scenario. Can you help me with this one?
route {
t_on_reply("global");
t_relay();
}
onreply_route[global] {
if (t_check_status("180")) {
t_inject_branch(“???”);
}
}
Thanks,
Xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Freitag, 26. Mai 2017 15:28
To: OpenSIPS users mailling list ; xaled
Subject: Re: [OpenSIPS-Users] Create new branch on receipt of provisional
response on the main branch
Hi Xaled,
With a pre-2.3 release you cannot do this, unless you wait for the current
branches to fail, so to use the failure_route to add new branches.
With 2.3 you can do it by using the t_inject_branch() function.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2017, Huston, US
http://opensips.org/training/OpenSIPS_Bootcamp_2017.html
On 05/22/2017 09:30 PM, xaled wrote:
Hello,
I need to create a branch on receipt of provisional response on the main branch.
Doing append_brach in reply_route does not seem to work.
What is right way to do it?
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] identify branch by name in minor_branch_flag
Hi Bogdan,
Ok, thanks!
Greetings,
xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Freitag, 26. Mai 2017 15:25
To: OpenSIPS users mailling list ; xaled
Subject: Re: [OpenSIPS-Users] identify branch by name in minor_branch_flag
Hi Xaled,
The first param of setbflag is the index of the added branch, starting from 1.
Each append_branch() will add a new branch. And there is a single set of
branches per transaction, so they cannot mix.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Bootcamp 2017, Huston, US
http://opensips.org/training/OpenSIPS_Bootcamp_2017.html
On 05/22/2017 06:15 PM, xaled wrote:
Hello Bogdan,
thanks!
Following question – are the branch indexes and settings shared between the
route? Wont the minor branch setting in route[a] for branch alice affect the
bob’s branch setting in route[b]
modparam("tm", "minor_branch_flag", 1)
route[a] {
append_branch( "sip:al...@test.com");
setbflag(1,1);
}
route[b] {
append_branch( "sip:b...@test.com");
append_branch( "sip:ca...@test.com");
setbflag(2,1);
}
Thanks,
xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Montag, 22. Mai 2017 16:43
To: OpenSIPS users mailling list <mailto:users@lists.opensips.org>
; xaled <mailto:xa...@web.de>
Subject: Re: [OpenSIPS-Users] identify branch by name in minor_branch_flag
Hello Xaled,
Any branch can be a minor branch, you just have to properly mark it via the
branch flag you configured (via the minor_branch_flag param - see
http://www.opensips.org/html/docs/modules/2.3.x/tm.html#idp5618944 )
You can set the corresponding branch flag via setbflag(
www.opensips.org/Documentation/Script-CoreFunctions-2-3
<http://www.opensips.org/Documentation/Script-CoreFunctions-2-3> ) and check
it via
isbflagset(http://www.opensips.org/Documentation/Script-CoreFunctions-2-2#toc22)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit May 2017 Amsterdam
http://www.opensips.org/events/Summit-2017Amsterdam.html
On 05/20/2017 03:32 AM, xaled wrote:
Hi,
did I get it right that it is only possible to identify minor branches by index?
Using index I cannot have first branch to be minor in some scenarios and not
minor in other.
It would be good to be able to identify multiple minor branches by names. Ether
URI, or additional specific name parameter could be used for it.
Instead of:
modparam("tm", "minor_branch_flag", 1)
something like:
modparam("tm", "minor_branch_flag", “sip:al...@test.com”)
route[1]{
append_branch( "sip:al...@test.com");
append_branch( "sip:b...@test.com");
}
route[2]{
append_branch( "sip:b...@test.com");
append_branch( "sip:al...@test.com");
}
$T_branch_idx could be extended to $T_branch_name.
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] Create new branch on receipt of provisional response on the main branch
Hello, I need to create a branch on receipt of provisional response on the main branch. Doing append_brach in reply_route does not seem to work. What is right way to do it? Thanks, xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] identify branch by name in minor_branch_flag
Hello Bogdan,
thanks!
Following question – are the branch indexes and settings shared between the
route? Wont the minor branch setting in route[a] for branch alice affect the
bob’s branch setting in route[b]
modparam("tm", "minor_branch_flag", 1)
route[a] {
append_branch("sip:al...@test.com");
setbflag(1,1);
}
route[b] {
append_branch("sip:b...@test.com");
append_branch("sip:ca...@test.com");
setbflag(2,1);
}
Thanks,
xaled
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Montag, 22. Mai 2017 16:43
To: OpenSIPS users mailling list ; xaled
Subject: Re: [OpenSIPS-Users] identify branch by name in minor_branch_flag
Hello Xaled,
Any branch can be a minor branch, you just have to properly mark it via the
branch flag you configured (via the minor_branch_flag param - see
http://www.opensips.org/html/docs/modules/2.3.x/tm.html#idp5618944 )
You can set the corresponding branch flag via setbflag(
www.opensips.org/Documentation/Script-CoreFunctions-2-3
<http://www.opensips.org/Documentation/Script-CoreFunctions-2-3> ) and check
it via
isbflagset(http://www.opensips.org/Documentation/Script-CoreFunctions-2-2#toc22)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit May 2017 Amsterdam
http://www.opensips.org/events/Summit-2017Amsterdam.html
On 05/20/2017 03:32 AM, xaled wrote:
Hi,
did I get it right that it is only possible to identify minor branches by index?
Using index I cannot have first branch to be minor in some scenarios and not
minor in other.
It would be good to be able to identify multiple minor branches by names. Ether
URI, or additional specific name parameter could be used for it.
Instead of:
modparam("tm", "minor_branch_flag", 1)
something like:
modparam("tm", "minor_branch_flag", “sip:al...@test.com”)
route[1]{
append_branch( "sip:al...@test.com");
append_branch( "sip:b...@test.com");
}
route[2]{
append_branch( "sip:b...@test.com");
append_branch( "sip:al...@test.com");
}
$T_branch_idx could be extended to $T_branch_name.
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] identify branch by name in minor_branch_flag
Hi,
did I get it right that it is only possible to identify minor branches by index?
Using index I cannot have first branch to be minor in some scenarios and not
minor in other.
It would be good to be able to identify multiple minor branches by names. Ether
URI, or additional specific name parameter could be used for it.
Instead of:
modparam("tm", "minor_branch_flag", 1)
something like:
modparam("tm", "minor_branch_flag", “sip:al...@test.com”)
route[1]{
append_branch("sip:al...@test.com");
append_branch("sip:b...@test.com");
}
route[2]{
append_branch("sip:b...@test.com");
append_branch("sip:al...@test.com");
}
$T_branch_idx could be extended to $T_branch_name.
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to change the order of characters in a string and ascii2hex
Hello Răzvan,
Ok, just opened an issue.
Another good thing would be the possibility to access a specific character in a
string.
Something like:
$var(str) = "123456";
xlog("first character: $var(str)[0] second character: $var(str)[1] ");
Greetings,
xaled
From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan
Crainea
Sent: Mittwoch, 17. Mai 2017 16:47
To: users@lists.opensips.org
Subject: Re: [OpenSIPS-Users] How to change the order of characters in a string
and ascii2hex
Hello!
Yes, I was talking about the order of characters.
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com <http://www.opensips-solutions.com>
On 05/17/2017 04:06 PM, xaled wrote:
Hi Răzvan
What feature do you mean – changing the order of characters in a string, or
ascii2hex?
I found s.encode.hexa that does what I meant with ascii2hex.
I actually thought about an existing functionality a la reg expression for
changing the order of characters.
If It is not possible to do with existing functionality I will open a feature.
Thanks,
xaled
From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan
Crainea
Sent: Mittwoch, 17. Mai 2017 10:59
To: users@lists.opensips.org <mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to change the order of characters in a string
and ascii2hex
Hi, Xaled!
This might be interesting - if you need this feature, please open a new feature
request on our issue tracker[1] so we can centralize everyting.
[1] https://github.com/OpenSIPS/opensips/issues
Best regards,
Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com <http://www.opensips-solutions.com>
On 05/16/2017 08:35 PM, xaled wrote:
Hello,
I have a question and a feature idea.
What is the best way to change the order of characters in a string?
I have a string “12345” and I want to get “21435”
It would be nice to have ascii2hex in addition to dec2hex
Thanks,
xaled
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to change the order of characters in a string and ascii2hex
Hi Răzvan What feature do you mean – changing the order of characters in a string, or ascii2hex? I found s.encode.hexa that does what I meant with ascii2hex. I actually thought about an existing functionality a la reg expression for changing the order of characters. If It is not possible to do with existing functionality I will open a feature. Thanks, xaled From: Users [mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan Crainea Sent: Mittwoch, 17. Mai 2017 10:59 To: users@lists.opensips.org Subject: Re: [OpenSIPS-Users] How to change the order of characters in a string and ascii2hex Hi, Xaled! This might be interesting - if you need this feature, please open a new feature request on our issue tracker[1] so we can centralize everyting. [1] https://github.com/OpenSIPS/opensips/issues Best regards, Răzvan Crainea OpenSIPS Solutions www.opensips-solutions.com <http://www.opensips-solutions.com> On 05/16/2017 08:35 PM, xaled wrote: Hello, I have a question and a feature idea. What is the best way to change the order of characters in a string? I have a string “12345” and I want to get “21435” It would be nice to have ascii2hex in addition to dec2hex Thanks, xaled ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] How to change the order of characters in a string and ascii2hex
Hello, I have a question and a feature idea. What is the best way to change the order of characters in a string? I have a string “12345” and I want to get “21435” It would be nice to have ascii2hex in addition to dec2hex Thanks, xaled ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan,
I know, that script level is better and I use the script regex now it is
working. Perl was used out of frustration of not being able to get the right
regex with script. I’m neither good at perl, but the first regex example I
found on the web worked right away with minor changes.
Honestly I do not quite understand why the workable script regex should be the
way it is. Especially compared with the regex I used in perl. But I’m not a
regex expert either. Anyway I’m happy as long as it does what I need.
The patch looks good. I will try it and let you know how it will work out.
Thanks a lot for your support!
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 19. Januar 2017 11:54
To: xaled ; 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
To be honest I'm not good on perl, but if you can do it directly at script
level, it it cleaner and more efficient.
Also, check this
https://github.com/OpenSIPS/opensips/commit/d509aa63698bc26fde390a4b707dbf2be31f5de5
Thanks and Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/18/2017 04:09 PM, xaled wrote:
Hi Bogdan,
works like a charm, thanks!
As an additional bonus now I know how to work with the perl module ;)
$rb(mime)[idx] is even more flexible.
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Dienstag, 17. Januar 2017 15:12
To: xaled <mailto:xa...@web.de> ; 'OpenSIPS users mailling list'
<mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
There was a small typo in my regexp. The correct one is:
$var(reg) = "/(.*)gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
I tried it and it does the job.
Regarding the usability of the $rb variable, yes you have a point. I was
thinking of something like $rb(mime)[idx] to access also per mime.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/13/2017 12:04 PM, xaled wrote:
Hi Bogdan,
thank you for looking at this issue. This regex does not work. I tried
different combinations of the idea but it just not getting there.
2017-01-13T11:02:42.287766+01:00 ivr01 /usr/local/sbin/opensips[24845]:
DBG:core:tr_eval_re: we must compile the regexp
2017-01-13T11:02:42.288116+01:00 ivr01 /usr/local/sbin/opensips[24845]:
WARNING:core:parse_repl: \/ unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s
2017-01-13T11:02:42.288464+01:00 ivr01 /usr/local/sbin/opensips[24845]:
ERROR:core:subst_parser: unknown flag . in
(.*)/gml:Coordinates>(.*)<\/gml:Coordin
ates(.*)/\2/s
2017-01-13T11:02:42.288787+01:00 ivr01 /usr/local/sbin/opensips[24845]:
ERROR:core:tr_eval_re: Can't compile regexp
I managed to get it running with perl:
use OpenSIPS qw ( log );
use OpenSIPS::Constants;
use OpenSIPS::Message;
sub parsePIDFLO {
my $m = shift;
my $body = $m->getBody();
($coord) = $body =~ /Coordinates>(.*)mailto:bog...@opensips.org]
Sent: Mittwoch, 11. Januar 2017 11:05
To: OpenSIPS users mailling list <mailto:users@lists.opensips.org>
; asd asd <mailto:xa...@web.de>
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
Please try
$var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/06/2017 05:44 PM, xaled wrote:
Hi Bogdan,
can you give any hints on how to get the Coordinates values and not the whole
xml body from the regex subst?
Sorry for being not clever enough to figure it out myself.
Thanks
Hi Bogdan,
$var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
DBG:core:subst_run:matched shows the needed XML element with value, but not the
value alone. The xlog output shows the whole XML body without gml:Coordinates.
2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: Trying to apply reg
exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012mailto:pres:sip:+1234...@test.com>
"pres:sip:+1234...@test.com">#015#012 #015#012 #015#012 #015#012#015#012
#015#012 #015#012 12.32
34.24#015#012 #015#012 #015#012#015#012
#015#012 no#015#012
#015#012#01
5#012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#0
12#015#012#015#012]
2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: we must compile the
regexp
2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan,
works like a charm, thanks!
As an additional bonus now I know how to work with the perl module ;)
$rb(mime)[idx] is even more flexible.
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Dienstag, 17. Januar 2017 15:12
To: xaled ; 'OpenSIPS users mailling list'
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
There was a small typo in my regexp. The correct one is:
$var(reg) = "/(.*)gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
I tried it and it does the job.
Regarding the usability of the $rb variable, yes you have a point. I was
thinking of something like $rb(mime)[idx] to access also per mime.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/13/2017 12:04 PM, xaled wrote:
Hi Bogdan,
thank you for looking at this issue. This regex does not work. I tried
different combinations of the idea but it just not getting there.
2017-01-13T11:02:42.287766+01:00 ivr01 /usr/local/sbin/opensips[24845]:
DBG:core:tr_eval_re: we must compile the regexp
2017-01-13T11:02:42.288116+01:00 ivr01 /usr/local/sbin/opensips[24845]:
WARNING:core:parse_repl: \/ unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s
2017-01-13T11:02:42.288464+01:00 ivr01 /usr/local/sbin/opensips[24845]:
ERROR:core:subst_parser: unknown flag . in
(.*)/gml:Coordinates>(.*)<\/gml:Coordin
ates(.*)/\2/s
2017-01-13T11:02:42.288787+01:00 ivr01 /usr/local/sbin/opensips[24845]:
ERROR:core:tr_eval_re: Can't compile regexp
I managed to get it running with perl:
use OpenSIPS qw ( log );
use OpenSIPS::Constants;
use OpenSIPS::Message;
sub parsePIDFLO {
my $m = shift;
my $body = $m->getBody();
($coord) = $body =~ /Coordinates>(.*)mailto:bog...@opensips.org]
Sent: Mittwoch, 11. Januar 2017 11:05
To: OpenSIPS users mailling list <mailto:users@lists.opensips.org>
; asd asd <mailto:xa...@web.de>
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
Please try
$var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/06/2017 05:44 PM, xaled wrote:
Hi Bogdan,
can you give any hints on how to get the Coordinates values and not the whole
xml body from the regex subst?
Sorry for being not clever enough to figure it out myself.
Thanks
Hi Bogdan,
$var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
DBG:core:subst_run:matched shows the needed XML element with value, but not the
value alone. The xlog output shows the whole XML body without gml:Coordinates.
2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: Trying to apply reg
exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012mailto:pres:sip:+1234...@test.com>
"pres:sip:+1234...@test.com">#015#012 #015#012 #015#012 #015#012#015#012
#015#012 #015#012 12.32
34.24#015#012 #015#012 #015#012#015#012
#015#012 no#015#012
#015#012#01
5#012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#0
12#015#012#015#012]
2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: we must compile the
regexp
2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_parser: ok, se is 0x7f39a
5d0a1f0
2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: running. r=0
2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: matched (404, 45): [
gml:Coordinates>12.32 34.24#015#012mailto:pres:sip:+1234...@test.com> "pres:sip:+1234...@test.com">#015#0
12 #015#012 #015#012 #015#012
#015#012 #015#012 #015#012
<12.32 34.24>#015#012 #015#012 #015#012#015#012
#015#012 no#015#012 #015#012#015#
012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#012
Thanks
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 5. Januar 2017 13:12
To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >; xaled mailto:xa...@web.de> >
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan,
thank you for looking at this issue. This regex does not work. I tried
different combinations of the idea but it just not getting there.
2017-01-13T11:02:42.287766+01:00 ivr01 /usr/local/sbin/opensips[24845]:
DBG:core:tr_eval_re: we must compile the regexp
2017-01-13T11:02:42.288116+01:00 ivr01 /usr/local/sbin/opensips[24845]:
WARNING:core:parse_repl: \/ unknown escape in (.*)<\/gml:Coordinates(.*)/\2/s
2017-01-13T11:02:42.288464+01:00 ivr01 /usr/local/sbin/opensips[24845]:
ERROR:core:subst_parser: unknown flag . in
(.*)/gml:Coordinates>(.*)<\/gml:Coordin
ates(.*)/\2/s
2017-01-13T11:02:42.288787+01:00 ivr01 /usr/local/sbin/opensips[24845]:
ERROR:core:tr_eval_re: Can't compile regexp
I managed to get it running with perl:
use OpenSIPS qw ( log );
use OpenSIPS::Constants;
use OpenSIPS::Message;
sub parsePIDFLO {
my $m = shift;
my $body = $m->getBody();
($coord) = $body =~ /Coordinates>(.*)mailto:bog...@opensips.org]
Sent: Mittwoch, 11. Januar 2017 11:05
To: OpenSIPS users mailling list ; asd asd
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
Please try
$var(reg) = "(.*)/gml:Coordinates>(.*)<\/gml:Coordinates(.*)/\2/s";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 01/06/2017 05:44 PM, xaled wrote:
Hi Bogdan,
can you give any hints on how to get the Coordinates values and not the whole
xml body from the regex subst?
Sorry for being not clever enough to figure it out myself.
Thanks
Hi Bogdan,
$var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
DBG:core:subst_run:matched shows the needed XML element with value, but not the
value alone. The xlog output shows the whole XML body without gml:Coordinates.
2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: Trying to apply reg
exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012mailto:pres:sip:+1234...@test.com>
"pres:sip:+1234...@test.com">#015#012 #015#012 #015#012 #015#012#015#012
#015#012 #015#012 12.32
34.24#015#012 #015#012 #015#012#015#012
#015#012 no#015#012
#015#012#01
5#012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#0
12#015#012#015#012]
2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: we must compile the
regexp
2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_parser: ok, se is 0x7f39a
5d0a1f0
2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: running. r=0
2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: matched (404, 45): [
gml:Coordinates>12.32 34.24#015#012mailto:pres:sip:+1234...@test.com> "pres:sip:+1234...@test.com">#015#0
12 #015#012 #015#012 #015#012
#015#012 #015#012 #015#012
<12.32 34.24>#015#012 #015#012 #015#012#015#012
#015#012 no#015#012 #015#012#015#
012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#012
Thanks
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 5. Januar 2017 13:12
To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >; xaled mailto:xa...@web.de> >
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan,
can you give any hints on how to get the Coordinates values and not the whole
xml body from the regex subst?
Sorry for being not clever enough to figure it out myself.
Thanks
Hi Bogdan,
$var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
DBG:core:subst_run:matched shows the needed XML element with value, but not the
value alone. The xlog output shows the whole XML body without gml:Coordinates.
2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: Trying to apply reg
exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012#015#012
#015#012 #015#012 #015#012#015#012
#015#012 #015#012 12.32
34.24#015#012 #015#012 #015#012#015#012
#015#012 no#015#012
#015#012#01
5#012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#0
12#015#012#015#012]
2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: we must compile the
regexp
2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_parser: ok, se is 0x7f39a
5d0a1f0
2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: running. r=0
2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: matched (404, 45): [
gml:Coordinates>12.32 34.24#015#012#015#0
12 #015#012 #015#012 #015#012
#015#012 #015#012 #015#012
<12.32 34.24>#015#012 #015#012 #015#012#015#012
#015#012 no#015#012 #015#012#015#
012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#012
Thanks
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 5. Januar 2017 13:12
To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >; xaled mailto:xa...@web.de> >
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan,
$var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
xlog("Position is $(rb[1]{re.subst,$var(reg)})\n");
DBG:core:subst_run:matched shows the needed XML element, but not the value. The
xlog output shows the whole XML body without gml:Coordinates.
2017-01-05T13:23:23.104982+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: Trying to apply reg
exp [/gml:Coordinates>(.*)<\/gml:Coordinates/\1/] on : [#015#012#015#012
#015#012 #015#012 #015#012#015#012
#015#012 #015#012 12.32
34.24#015#012 #015#012 #015#012#015#012
#015#012 no#015#012
#015#012#01
5#012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#0
12#015#012#015#012]
2017-01-05T13:23:23.107376+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:tr_eval_re: we must compile the
regexp
2017-01-05T13:23:23.107903+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_parser: ok, se is 0x7f39a
5d0a1f0
2017-01-05T13:23:23.108241+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: running. r=0
2017-01-05T13:23:23.111918+01:00 ivr01 /usr/local/sbin/opensips[2227]:
DBG:core:subst_run: matched (404, 45): [
gml:Coordinates>12.32 34.24#015#012#015#0
12 #015#012 #015#012 #015#012
#015#012 #015#012 #015#012
<12.32 34.24>#015#012 #015#012 #015#012#015#012
#015#012 no#015#012 #015#012#015#
012 #015#012 #015#012
2016-8-02T04:13:23Z#015#012 #015#012
Thanks
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 5. Januar 2017 13:12
To: OpenSIPS users mailling list ; xaled
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Try $var(reg) = "/gml:Coordinates>(.*)<\/gml:Coordinates/\1/";
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 05.01.2017 13:38, xaled wrote:
Hi Bogdan,
Well - almost enough ;)
$var(reg) = "/gml:Coordinates>(.*)(.*)mailto:users-boun...@lists.opensips.org] On Behalf Of xaled
Sent: Donnerstag, 5. Januar 2017 12:22
To: 'OpenSIPS users mailling list' <mailto:users@lists.opensips.org>
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan,
that is enough for me!
Thanks.
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 5. Januar 2017 12:19
To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >; xaled mailto:xa...@web.de> >
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
You can use the $(rb[n]) to access a specific body part. see:
http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65
Once you get the XML body, you can use some regexp in order to extract the
needed info from the the XML (unfortunately thers is no way to parse XML at
script level). See the "re" transformation :
http://www.opensips.org/Documentation/Script-Tran-2-2#toc82
$var(reg) = "/gml:pos>(.*)http://www.opensips-solutions.com
On 05.01.2017 12:57, xaled wrote:
Hi Bogdan;
opensips-2.2.2
Thanks.
From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org]
Sent: Donnerstag, 5. Januar 2017 11:39
To: OpenSIPS users mailling list <mailto:users@lists.opensips.org>
; xaled <mailto:xa...@web.de>
Subject: Re: [OpenSIPS-Users] How to parse XML Body?
Hi,
What version of OpenSIPS are you using ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 04.01.2017 21:19, xaled wrote:
Hi,
What is the best way to parse xml body in an INVITE request?
I want to access geographic location information gml:Coordinates or gml:pos
from xml body and do some routing. I’ve seen the emergency module, but it is
too specific to be useful in my basic scenario.
Content-Type: multipart/mixed;boundary=ssboundary-1_
Content-Type: application/pidf+xml
…
XYZ
XYZ
…
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan, Well - almost enough ;) $var(reg) = "/gml:Coordinates>(.*)(.*)mailto:users-boun...@lists.opensips.org] On Behalf Of xaled Sent: Donnerstag, 5. Januar 2017 12:22 To: 'OpenSIPS users mailling list' Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi Bogdan, that is enough for me! Thanks. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Donnerstag, 5. Januar 2017 12:19 To: OpenSIPS users mailling list mailto:users@lists.opensips.org> >; xaled mailto:xa...@web.de> > Subject: Re: [OpenSIPS-Users] How to parse XML Body? You can use the $(rb[n]) to access a specific body part. see: http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 Once you get the XML body, you can use some regexp in order to extract the needed info from the the XML (unfortunately thers is no way to parse XML at script level). See the "re" transformation : http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 $var(reg) = "/gml:pos>(.*)http://www.opensips-solutions.com On 05.01.2017 12:57, xaled wrote: Hi Bogdan; opensips-2.2.2 Thanks. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Donnerstag, 5. Januar 2017 11:39 To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> ; xaled <mailto:xa...@web.de> Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan, that is enough for me! Thanks. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Donnerstag, 5. Januar 2017 12:19 To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? You can use the $(rb[n]) to access a specific body part. see: http://www.opensips.org/Documentation/Script-CoreVar-2-2#toc65 Once you get the XML body, you can use some regexp in order to extract the needed info from the the XML (unfortunately thers is no way to parse XML at script level). See the "re" transformation : http://www.opensips.org/Documentation/Script-Tran-2-2#toc82 $var(reg) = "/gml:pos>(.*)http://www.opensips-solutions.com On 05.01.2017 12:57, xaled wrote: Hi Bogdan; opensips-2.2.2 Thanks. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Donnerstag, 5. Januar 2017 11:39 To: OpenSIPS users mailling list <mailto:users@lists.opensips.org> ; xaled <mailto:xa...@web.de> Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Re: [OpenSIPS-Users] How to parse XML Body?
Hi Bogdan; opensips-2.2.2 Thanks. From: Bogdan-Andrei Iancu [mailto:bog...@opensips.org] Sent: Donnerstag, 5. Januar 2017 11:39 To: OpenSIPS users mailling list ; xaled Subject: Re: [OpenSIPS-Users] How to parse XML Body? Hi, What version of OpenSIPS are you using ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 04.01.2017 21:19, xaled wrote: Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I’ve seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml … XYZ XYZ … ___ Users mailing list Users@lists.opensips.org <mailto:Users@lists.opensips.org> http://lists.opensips.org/cgi-bin/mailman/listinfo/users ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
[OpenSIPS-Users] How to parse XML Body?
Hi, What is the best way to parse xml body in an INVITE request? I want to access geographic location information gml:Coordinates or gml:pos from xml body and do some routing. I've seen the emergency module, but it is too specific to be useful in my basic scenario. Content-Type: multipart/mixed;boundary=ssboundary-1_ Content-Type: application/pidf+xml . XYZ XYZ . ___ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
