Re: [SR-Users] path uri problem

2013-04-09 Thread Andrew Pogrebennyk
Hi Juha, On 04/07/2013 01:51 PM, Juha Heinanen wrote: i escaped them, but it didn't help. path header now looks like: Path: sip:192.98.102.10;transport=tcp;lr;received='sip:192.98.102.10:58156%3Btransport%3Dtcp'. and i still get the same error: Apr 7 14:49:47 wheezy1

[SR-Users] Diversion header authentication

2013-04-09 Thread phillman25
Dear List I am currently using the group module to authenticate inbound calls using the From header using the below code: if (!is_user_in(From, 1)) { sl_send_reply(403, NOT ALLOWED); exit; }; }; I want to now authenticate the Diversion header, when

Re: [SR-Users] path uri problem

2013-04-09 Thread Juha Heinanen
Andrew Pogrebennyk writes: I don't see why you think that ; and = should be escaped. rfc3327 chapter 4 says: The syntax for Path is defined as follows: Path = Path HCOLON path-value *( COMMA path-value ) path-value = name-addr *( SEMI rr-param ) because path-value starts

[SR-Users] Kamailio World Updates - April 9

2013-04-09 Thread Daniel-Constantin Mierla
Kamailio World Conference is one week away, only few bits to adjust, everything being pretty much in place. The agenda with presentations is available at: - http://conference.kamailio.com/k01/schedule/ Details about the speakers are available at: -

Re: [SR-Users] path uri problem

2013-04-09 Thread Andrew Pogrebennyk
On 04/09/2013 11:59 AM, Juha Heinanen wrote: because path-value starts with name-addr and my interpretation is that since there are s around this path header body: Path: sip:192.98.102.10;transport=tcp;lr;received='sip:192.98.102.10:58156%3Btransport%3Dtcp' solely consists of name-addr

Re: [SR-Users] Diversion header authentication

2013-04-09 Thread Morten Isaksen
Hi, I have not tested this, but try: $avp(s:divhdr) = $(hdr(Diversion)[$var(i)]); avp_subst($avp(s:divhdr), /.*sip:\+45(.*)(@.*)/\1/); # Extract number between +45 and @ if (is_user_in($avp(s:divhdr), 1) { ... } Please note that there can be more than one Diverseion header. In that case you

Re: [SR-Users] sr-users Digest, Vol 95, Issue 33

2013-04-09 Thread julian arsanches
this ? thanks in advance... -- next part -- An HTML attachment was scrubbed... URL: http://lists.sip-router.org/pipermail/sr-users/attachments/20130409/51f952b4/attachment-0001.htm -- Message: 3 Date: Tue, 09 Apr 2013 07:27:56 +0200 From

Re: [SR-Users] Diversion header authentication

2013-04-09 Thread Daniel-Constantin Mierla
Hello, just adding that the tobody transformation could be handy to extract the user or uri part of a Diversion header, not to fight with subst expressions: - http://www.kamailio.org/wiki/cookbooks/devel/transformations#to-body_transformations Cheers, Daniel On 4/9/13 3:16 PM, Morten

Re: [SR-Users] Contact header from linphone too long to delete

2013-04-09 Thread Daniel-Constantin Mierla
Hello, On 4/8/13 7:13 PM, Ross Kusler wrote: Hello, We noticed an issue with a bunch of stale entries in the mysql location table recently -- all for the same user. It turns out that if you install linphone 2.0.2 on an iOS device (other versions/platforms might also be

[SR-Users] Operator !~

2013-04-09 Thread Manwe
Hi all I was checking for an operator not matching regular expression. Acording to the doc we have =~ and !~ for matching and not matching. http://www.kamailio.org/wiki/cookbooks/3.3.x/core#script_statements I tried this one: if(!is_domain_local($rd) $rd !~ ^.+\.local$) Resulting on these

Re: [SR-Users] xcap server crash

2013-04-09 Thread Daniel-Constantin Mierla
Hello, can you provide 'bt full' and print the variables start_pos, end_pos and cur_etag_len in the frame 1? Cheers, Daniel On 4/8/13 10:23 AM, Juha Heinanen wrote: i tested kamailio 4.0 xcap server with sipclients and got crash. should i add a tracker entry? -- juha (gdb) where #0

Re: [SR-Users] xcap server crash

2013-04-09 Thread Juha Heinanen
Daniel-Constantin Mierla writes: can you provide 'bt full' and print the variables start_pos, end_pos and cur_etag_len in the frame 1? daniel, thanks for looking into this. the info you asked is below. -- juha (gdb) bt full #0 0x7fa35ab47764 in ?? () from

Re: [SR-Users] Operator !~

2013-04-09 Thread José Luis Millán
Jon, I guess you can find the response in [1] ``` not operator in if() if (!$fd=~“regexp”) must now be written as if (!($fd=~“regexp”)) for what reason ever. Notice: the operator !~ seems not to be working for some reason as well. e.g.: ($fd !~ 'not this') must be replaced with !($fd =~ 'not

Re: [SR-Users] path uri problem

2013-04-09 Thread Iñaki Baz Castillo
2013/4/9 Juha Heinanen j...@tutpro.com: because path-value starts with name-addr and my interpretation is that since there are s around this path header body: Path: sip:192.98.102.10;transport=tcp;lr;received='sip:192.98.102.10:58156%3Btransport%3Dtcp' solely consists of name-addr and does

Re: [SR-Users] Operator !~

2013-04-09 Thread Manwe
El Tue, 9 Apr 2013 18:16:52 +0200 José Luis Millán jmil...@aliax.net escribió: Jon, I guess you can find the response in [1] ``` not operator in if() if (!$fd=~“regexp”) must now be written as if (!($fd=~“regexp”)) for what reason ever. Notice: the operator !~ seems not to be

Re: [SR-Users] sip_trace unable to capture after next_branches()

2013-04-09 Thread Ramaseshi reddy kolli
Hi, Outbound SIP invite is not captured even after setting flag only.Can anyone help with this issue please ? Thanks Ram On Sun, Apr 7, 2013 at 3:33 AM, Ramaseshi reddy kolli ramaseshire...@gmail.com wrote: Hi, Once in a while it captures outbound SIP Invite but it captures always 100

Re: [SR-Users] path uri problem

2013-04-09 Thread Iñaki Baz Castillo
2013/4/9 Richard Fuchs rfu...@sipwise.com: On 04/09/13 12:19, Iñaki Baz Castillo wrote: So the received value added by Kamailio is invalid. Such a value cannot be the value of a SIP URI parameter at all. I strongly propose encoding it in base64 or escaping the = and the ; symbols when in a

Re: [SR-Users] path uri problem

2013-04-09 Thread Spencer Thomason
Although slightly off topic, I've been trying to craft a Path header that will work with FreeSWITCH. See: http://jira.freeswitch.org/browse/FS-4989 It would be great if the Path header was compatible with what they want as well. BR, Spencer On Apr 9, 2013, at 4:05 PM, Iñaki Baz Castillo

Re: [SR-Users] path uri problem

2013-04-09 Thread Iñaki Baz Castillo
As I said before, this Path header Path: sip:10.59.1.195;lr;received='sip:10.59.1.241:5079;transport=tcp' has a URI with these params: - lr : no value - received : 'sip:10.59.1.241:5079 - transport : tcp' And this is because quoting a *URI param* between single quotes is a bug

Re: [SR-Users] path uri problem

2013-04-09 Thread Juha Heinanen
Richard Fuchs writes: Would you and everyone else agree that unconditionally encoding the param in base64 would be the preferred solution? I have some pending additions to the path module and could include that as well. i don't agree. characters that are not param-unreserved or unreserved

Re: [SR-Users] path uri problem

2013-04-09 Thread Juha Heinanen
below is patch that fixes receiced param value. i have not tested if kamalio that gets such a value is able to unescape the escaped chars. if not, that is a bug too. -- juha *** path.c Fri Mar 29 19:14:46 2013 --- /usr/src/sip-router/modules/path/path.c Wed Apr 10 08:09:43 2013