We currently have in 5 different places same code - for building a dummy SIP
requests. We should get a single one, easier to maintain.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/iss
Closed #828.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/828#event-590973640___
Devel mailing list
Devel@lists.opensips.org
http://list
Thank you @rrb3942 for your fix - I just pushed a larger one (covering several
aspects) . Please confirm that the commit 2d0cebc really fixes the issues for
you.
Regards,
Bogdan
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on Git
$si should return NULL now if called from a route without a real SIP message.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/817#issuecomment-197026722_
Branch: refs/heads/2.1
Home: https://github.com/OpenSIPS/opensips
Commit: 981e3541239ce67481abfc52cae769f7bd35a6ee
https://github.com/OpenSIPS/opensips/commit/981e3541239ce67481abfc52cae769f7bd35a6ee
Author: Bogdan-Andrei Iancu
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed pa
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: 2d0cebc0be2491984ce357afd89d41212866bc06
https://github.com/OpenSIPS/opensips/commit/2d0cebc0be2491984ce357afd89d41212866bc06
Author: Bogdan-Andrei Iancu
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed
Closed #817 via 2d0cebc0be2491984ce357afd89d41212866bc06.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/817#event-590964818___
Devel ma
@telephone-man , you are right, whatever you do from script, it should not
crash.
The problem is related to $si - you should not use message related variables
from an event route (as you do not actually have a sip message here). but, once
again, it should not crash.
The solutions are - fix the b
Yes, obviously $var(newTo) = "sip:" + $rU + "@" + $var(someVar); works. Like
I was explaining, I need to accommodate patterns that can't be standardized.
How does one enter:
"sip:" + $rU + "@" + $var(someVar);
"sip:" + $var(foo) + $var(bar) + "@" + $var(someVar);
...
Into the dialplan databa
@mishehu , it may be an misunderstanding on how you construct strings from
variables.
Instead of
$var(newTo) = "sip:$rU@$var(someVar)";
(where the input is simply evaluated as string)
the correct way (if you want to have variables evaluated is:
$var(newTo) = "sip:"+$rU+"@"+$var(someVa
We are using async and exec to make a web-request as shown below:
$var(fullQueryClientReadyRequest) = "an url with params";
async(exec("curl --connect-timeout 30 --max-time 30
\"$var(fullQueryClientReadyRequest)\"", "", "$var(restGetResponse)"),
RT_RESUME_AFTER_RESPONSE);
We see
thank you @liviuchircu !
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/819#issuecomment-197008484___
Devel mailing list
Devel@lists.ope
Closed #819 via 7511e8460afa1fa89d6602865f3db8f706dda711.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/819#event-590901213___
Devel ma
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: 7511e8460afa1fa89d6602865f3db8f706dda711
https://github.com/OpenSIPS/opensips/commit/7511e8460afa1fa89d6602865f3db8f706dda711
Author: Bogdan-Andrei Iancu
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed
Branch: refs/heads/2.1
Home: https://github.com/OpenSIPS/opensips
Commit: b2bc43e76494e07d6cb1ce1bec2fc27e72fa0a47
https://github.com/OpenSIPS/opensips/commit/b2bc43e76494e07d6cb1ce1bec2fc27e72fa0a47
Author: Bogdan-Andrei Iancu
Date: 2016-03-15 (Tue, 15 Mar 2016)
Changed pa
yeah, the local transactions do not have the the uas sip_msg structure. I guess
we need to either disabled async in local route, either re-adapt the
sip_msg_cloner strategy for before the local route
---
You are receiving this because you are subscribed to this thread.
Reply to this email di
Hello !
I'm having a problem that this disturbing me a lot and I have no idea how
can I solve this. I'm using my opensips as redirect server and some INVITE
that the server receives some times it doesn't answer and the most time its
works perfect... When Its occur I the server run my redirect scri
After upgrading some systems from 1.10 to 1.11 I started receiving segfaults
that I traced back to accessing $si when it was not populated in the msg and a
failure to correctly check the return value of ip_addr2a(). I believe it only
happened on internally generated requests.
Not sure what chan
Closed #788.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/788#event-590434098___
Devel mailing list
Devel@lists.opensips.org
http://li
Thanks !
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/One-session-per-account-tp7602024p7602035.html
Sent from the OpenSIPS - Devel mailing list archive at Nabble.com.
___
Devel mailing list
Devel@lists.opens
yes
http://www.opensips.org/html/docs/modules/devel/registrar.html#id293748
On 03/15/2016 05:51 AM, Anderson Catao wrote:
Hello !
I would like to know if I can limit the number of register per account. I
want that one account can just logging in one device.
Thanks !
--
View this message
Hello !
I would like to know if I can limit the number of register per account. I
want that one account can just logging in one device.
Thanks !
--
View this message in context:
http://opensips-open-sip-server.1449251.n2.nabble.com/One-session-per-account-tp7602024.html
Sent from the OpenSIP
22 matches
Mail list logo
