Hi Daniel,
I've tested the patch on top of v4.2.5 and it works. Thank you very much!
Yufei
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
Hi,
Thanks for the replies! The first thing I looked at was the
encode/decode.hexa transformations but it only transforms between ASCII
characters and Hex numbers. Then I used exec_avp to call a bash command
(for example, 'echo $((0x123))' gives you 291) which works. But calling
something
Hi,
I want to convert a Hex number string into a Dec number string, e.g. Hex
number "123" into Dec number "291". What is the best way? I didn't find any
transformation for this.
Thank you!
Yufei
___
SIP Express Router (SER) and Kamailio (OpenSER) -
. Any way
to use the end-of-line symbol?
Cheers,
Yufei
--
Message: 10
Date: Wed, 29 Apr 2015 18:01:26 +0100
From: Yufei Tao yufei@gmail.com
To: sr-users@lists.sip-router.org
Subject: [SR-Users] sht_rm_name_re() question
Message-ID
Hi
I've hit a problem with sht_rm_name_re() in htable module. I was calling it
like this:
sht_rm_name_re(Dlg=$var(callid)::tenant);
But when I used sipp to generate 600 concurrent calls for example, I called
this function when receiving BYE. But it removed more entries than it
should. Seems
the sip receiver was
stuck in some weird state. If I were you I would do TCP for SIP. It is also
recommended in 3261 to use TCP when sip is that big.
--
*From:* sr-users sr-users-boun...@lists.sip-router.org on behalf of
Yufei Tao yufei@gmail.com
*Sent:* Friday
Hi
We've got Kamailio (v4.0.0) connected to some SBC, which sends SIP traffic
and periodic OPTIONS pings to Kamailio's VIP. Kamailio responds to the
OPTIONS pings with OK, i.e. in the main route block:
if (is_method(OPTIONS))
{
sl_send_reply(200,OK);
exit;
}
All works fine
Hi
Just a quick question about the Kamailio Advanced Training Course: are
there any courses scheduled in Europe in 2014? If there are, roughly
what time will they likely to take place? The only one I can find is the
one in Miami next month but it's a bit far to travel.
Cheers,
Yufei
--
Yufei Tao
to the same *#-OFFLINE-#*.
Maybe it would be good to include the original etag for the expired entries,
e.g. '*#-OFFLINE-#*-orig_etag' rather than just '*#-OFFLINE-#*', in which case
these errors won't occur, since the original etags (orig_etag) are unique.
Yufei
On 08/10/13 13:54, Yufei Tao
be removed to cope with this situation?
Thank you!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee please notify
the sender by return and delete the message.
You must
is: is there any ways that I can stop all the NOTIFY
messages from being sent to the stale locations, i.e. remove these
SUBSCRIBE dialogs from memory?
Thank you!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee
that every
other user can get its RL document?
Cheers,
Yufei
Message: 3
Date: Thu, 22 Aug 2013 11:53:07 +0100
From: Yufei Tao yufei@redembedded.com
To: sr-users@lists.sip-router.org
Subject: [SR-Users] Subscribe to a common resource list
Message-ID: 5215ed93.7050...@redembedded.com
Content-Type
or user2,
which is not 'group1' so the resource list document fails to be
retrieved. How can I allow user1 and user2 to retrieve group1's RL document?
Thank you!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee
in
kamailio's process list (childs)
- $var has local route block scope.
- $avp has SIP transaction scope.
- Both $avp and $var are automatically freed.
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you
-bin/mailman/listinfo/sr-users
End of sr-users Digest, Vol 90, Issue 39
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee please notify
workaround is to use fix_nated_register() for every client
(the pragmatic and more secure approach).
regards
Klaus
On 18.09.2012 15:16, Yufei Tao wrote:
Hi
I have a strange problem on forking calls to a group of users. For
example I have two users y2 and y3 in dbaliases, both
is null, should set it to $ru on the
branches?
Yufei
On 19/09/12 11:53, Klaus Darilion wrote:
On 19.09.2012 12:24, Yufei Tao wrote:
Hi Klaus
Thanks for the reply!
I check the $du, it is always null before and after the lookup. Is it
only set when relaying to a proxy (from record-route
. set $du after lookup if it is empty Wonder if it is worth
adding fixes in the source code. Thanks very much Klaus for pointing me
to the right direction! Yufei Date: Wed, 19 Sep 2012 15:13:29 +0100
From: Yufei Tao yufei@redembedded.com Subject: Re: [SR-Users] call
forking using dbaliases
and RELAY are the last two routes:
route {
...
route(NAT);
... ...
# user location service
route(LOCATION);
route(RELAY);
}
Hope I have made it clear. Thanks very much!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
a closed TCP connection for a device behind NAT or
failure to response to NAT pings.
/O
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee please notify
the sender by return
/siremis:install32x:new-views
Cheers,
Daniel
On 6/16/12 11:34 AM, Yufei Tao wrote:
Hello
Seems Siremis 3.2.1 doesn't support configuration of drouting. Any plans
that it will in the future? I hope to use it to make my drouting
configuration easier.
What I want to do is to route prefixed
+dot and
maybe+underscore+hyphen as well). Maybe I should use PDT module instead
as it is supported by Siremis?
Thanks!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee
It is one line of effective code that you have to change. Let me know
if goes ok now and I will backport to stable branches.
Cheers,
Daniel
On 6/13/12 11:16 AM, Yufei Tao wrote:
Hi Daniel
The version is:
version: kamailio 3.2.2 (i386/linux)
flags: STATS: Off, USE_IPV6, USE_TCP
,
Daniel
On 6/12/12 4:33 PM, Yufei Tao wrote:
Hi Daniel
Thanks for the reply!
I tried it again and the log seems to suggest it crashed when loading
the dr_rules table that contains non-digit prefix, e.g. prefix bing
'abc.':
1. First crash when doing MI command dr_reload:
Jun 12 15:19
:53, Daniel-Constantin Mierla wrote:
Hello,
On 6/1/12 4:57 PM, Yufei Tao wrote:
Hi
I'm using drouting module and seems that it only allows digit-only
prefixes. Also all the number of digits to be stripped ('strip' defined
in dr_gateways) must be all digits too. When I used non-digits
attachment was scrubbed...
URL:
http://lists.sip-router.org/pipermail/sr-users/attachments/20120321/dd9bf194/attachment.htm
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee please
is always correct. regarding tcp
connection reuse, i don't remember why i wrote about that in the
tutorial. perhaps i was just mislead by the name of fix_nated_contact()
function that is incorrect. i just checked and the function has nothing
to do with nated contacts.
-- juha
--
Yufei Tao
OK now I've upgraded to Kamailio 3.2 and it all works: sql_query (to
insert BYE into acc table) in event_route() doesn't crash anymore.
On 29/02/12 09:31, Yufei Tao wrote:
Hi
To summarize my questions:
1. What is the correct way to account for Kamailio internally-generated
BYEs?
2. Using
Kamailio 3.1.5.
Thank you very much!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee please notify
the sender by return and delete the message.
You must not disclose
the client send crlfcrlf?
The reason I'm confused is, with these settings, if Kamailio can only
respond to crlfcrlf, but not send, then would the client only respond
too, as in 1. and 2., they seem to configure the same set of parameters?
Please help me clarify this. Thanks very much!
Yufei
--
Yufei Tao
the list at
sr-users-ow...@lists.sip-router.org
When replying, please edit your Subject line so it is more specific
than Re: Contents of sr-users digest...
Today's Topics:
1. TCP keepalive on server and client (Yufei Tao
);
}
if (!t_relay()) {
sl_reply_error();
}
exit;
}
#
And in the main route, route LOCATION and RELAY are the last two routes:
route {
...
# user location service
route(LOCATION);
route(RELAY);
}
Thanks very much!
Yufei
--
Yufei
Hi Daniel
Thanks very much for the quick response - and it works fine now :)
Cheers,
Yufei
On 13/12/11 16:05, Daniel-Constantin Mierla wrote:
Hello,
On 12/13/11 2:31 PM, Yufei Tao wrote:
Hi
I'm using Kamailio 3.1.5 and want to fork calls to all members in the
same group defined
:18 PM, Yufei Tao wrote:
Hi Daniel
Thanks very much for you response!
In my original config, I only set the dialog flag when receiving the
initial INVITE, and didn't use dlg_manage() at all.
Now I have added dlg_manage() when BYE is received as you suggested, I
got from the log
and see if the
delete query is sent to mysql server?
Cheers,
Daniel
On 12/2/11 12:18 PM, Yufei Tao wrote:
Hi Daniel
Thanks very much for you response!
In my original config, I only set the dialog flag when receiving the
initial INVITE, and didn't use dlg_manage() at all.
Now I have
dlg_manage() when BYE is received.
Cheers,
Daniel
On 11/30/11 3:36 PM, Yufei Tao wrote:
Hi
I am using dialog module in Kamailio 3.1.5, and find that the dialog
table entry does not get deleted after call if in-dialog requests (e.g.
session timer refresh re-INVITEs in my case) are challenged
the dialog flag (4) when receiving the initial INVITE.
Any idea why? Am I using the dialog module correctly?
Thanks very much!
Yufei
--
Yufei Tao
Red Embedded
This E-mail and any attachments hereto are strictly confidential and intended
solely for the addressee. If you are not the intended addressee
37 matches
Mail list logo