[SR-Users] Hex to Dec conversion

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 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-us

Re: [SR-Users] Hex to Dec conversion

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 external

[SR-Users] Hex to Dec conversion

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) - sr-u

Re: [SR-Users] sr-users Digest, Vol 119, Issue 28

"ERROR: htable [ht_var.c:176]: pv_parse_ht_name(): wrong format". 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 > To: sr-use

[SR-Users] sht_rm_name_re() question

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 w

Re: [SR-Users] SIP messages over UDP with sizes over MTU

ip 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 on behalf of > Yufei Tao > *Sent:* Friday, April 3, 2015 7:04 AM > *To:* sr-

Re: [SR-Users] sr-users Digest, Vol 119, Issue 4

your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > >1. Re: SIP messages over UDP with sizes over MTU (Yufei Tao) >2. Re: SIP messages over UDP with sizes over MTU > (Daniel-Constantin Mierla) &

Re: [SR-Users] SIP messages over UDP with sizes over MTU

ble check and be sure that the SBC is not blacklisted (traffic from it should not be handled via pike_check_req()). Cheers, Daniel On 01/04/15 15:42, Yufei Tao wrote: > Hi > > We've got Kamailio (v4.0.0) connected to some SBC, which sends SIP > traffic and periodic OPTIONS pings t

[SR-Users] SIP messages over UDP with sizes over MTU

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

[SR-Users] Kamailio Advanced Training Course in Europe 2014?

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 -- Yufe

Re: [SR-Users] Presence: Duplicate entry 'username-domain-presence-*#-OFFLINE-#*' for key 'presentity_idx' when multiple clients register using the same credentials

ag of expired presentity entries 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)

Re: [SR-Users] Presence: Duplicate entry 'username-domain-presence-*#-OFFLINE-#*' for key 'presentity_idx' when multiple clients register using the same credentials

OFFLINE-#*' for key 'presentity_idx' when multiple clients register using the same credentials Message-ID: <21074.36213.575240.614...@siika.tutpro.com><mailto:21074.36213.575240.614...@siika.tutpro.com> Content-Type: text/plain; charset=us-ascii Yufei Tao writes

Re: [SR-Users] Presence: Duplicate entry 'username-domain-presence-*#-OFFLINE-#*' for key 'presentity_idx' when multiple clients register using the same credentials

he same > '*#-OFFLINE-#*' etag. Because presentity table has a 'CONSTRAINT > presentity_idx UNIQUE (username, domain, event, etag)', this gives the > errors. > > Should the constraint be removed to cope with this situation? > > Thank you! > Yufei > > >

[SR-Users] Presence: Duplicate entry 'username-domain-presence-*#-OFFLINE-#*' for key 'presentity_idx' when multiple clients register using the same credentials

, this gives the errors. Should the constraint 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 send

[SR-Users] How to stop NOTIFY from being sent to stable location entries on unreliable network?

xpired in the active_watchers table. My question 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 c

Re: [SR-Users] Subscribe to a common resource list

ial URL so 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 To: Subject: [SR-Users] Subscribe to a common resource list Message-ID: <5215ed93.7050...@redembedded.com> Content-Type: text/plain; charset="ISO-

[SR-Users] Subscribe to a common resource list

... The problem is the watcher_user in this case would be user1 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 attachme

Re: [SR-Users] var vs avp...

y. It can be accessed from any process 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

Re: [SR-Users] sr-users Digest, Vol 90, Issue 39

t part -- > An HTML attachment was scrubbed... > URL: > <http://lists.sip-router.org/pipermail/sr-users/attachments/20121113/cf13d83a/attachment-0001.htm> > > -- > > ___ > sr-users mailing li

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

l be set), or 2. 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 Subject: Re: [SR-Users] call forking using dbaliases not worki

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

first branch is handled differently? So maybe when $du 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, i

Re: [SR-Users] call forking using dbaliases not working for un-NATed clients

okup(). ($du=null or > $du=$null, not sure what the correct syntax is). > > Another 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 >> &g

[SR-Users] call forking using dbaliases not working for un-NATed clients

(method=="REGISTER") { fix_nated_register(); xlog("L_DBG","NAT: Just done fix_nated_register in REGISTER message in NAT route\n"); } else { xlog("L_DBG","NAT: fix_nated_contact\n"); fix_nated_contact(); } setflag(FLT_NATS);

Re: [SR-Users] [sr-dev] new feature: option to remove, contacts based on sip nat keepalives

ot of branches causing many >> > retransmissions. >> > >> > There is plant to go for tcp/tls as well and detect when the connection is >> > down, but looks like no spare time in the near future. However, right now >> > using set_forward_no_connect()

Re: [SR-Users] Siremis routing support does not include drouting

via: > > http://kb.asipto.com/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 m

[SR-Users] Siremis routing support does not include drouting

abets+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 addr

Re: [SR-Users] drouting module: can I use non-digit prefix?

gi/sip-router/?a=commit;h=c737ff95bb2e742981d81088169baa60d4605b85 > > > 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 versi

Re: [SR-Users] drouting module: can I use non-digit prefix?

routing rule at all. > > Can you get the backtrace? First do: > > ulimit -c unlimited > > Then run again an a corefile should be generated (in / or in working > directory) - use gdb to get the backtrace: > > gdb /path/to/kamailio /path/to/corefile > > bt full > &g

Re: [SR-Users] drouting module: can I use non-digit prefix?

On 12/06/12 10: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' define

[SR-Users] drouting module: can I use non-digit prefix?

an use prefixes with alphabet and dots, e.g. "gateway1."? 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 please notify the sender by return and

Re: [SR-Users] ACCDB insert issues

as any ideas? >>> >>> >>> >>> >>> >>> >>> >>> The db_insert_mode set to 1 does not work (my ACC table is INNODB >>> >>> because I don?t want to lose info). >>> >>> >>> >>> >

Re: [SR-Users] add_contact_alias and handle_ruri_alias vs fix_nated_contact

ncorrect. i just checked and the function has nothing > to do with nated contacts. > > -- juha -- 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 send

Re: [SR-Users] How to do accounting for Kamailio-generated BYEs?

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 interna

Re: [SR-Users] How to do accounting for Kamailio-generated BYEs?

Hi To summarize my questions: 1. What is the correct way to account for Kamailio internally-generated BYEs? 2. Using sql_query inside event_route() crashes Kamailio - is this a bug or unexpected usage? Thanks very much! Yufei On 28/02/12 17:06, Yufei Tao wrote: > Hi > > Thanks for y

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

shov > Subject: Re: [SR-Users] How to do accounting for Kamailio-generated > BYEs? > To: sr-users@lists.sip-router.org > Message-ID: <4f4bc9be.8000...@evaristesys.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 02/27/2012 12:58 PM, Yufei Tao wr

[SR-Users] How to do accounting for Kamailio-generated BYEs?

I'm 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 mu

Re: [SR-Users] Detection of broken TCP connections to clients

Mierla wrote: > Hello, > > On 2/9/12 3:51 PM, Yufei Tao wrote: >> Hi >> >> When clients register to Kamailio over TCP/TLS, if I set >> tcp_connection_lifetime to be quite small, like 30 seconds, and let >> clients send refreshes every 20 seconds, for example.

[SR-Users] Detection of broken TCP connections to clients

expiring time of 1 hour, but then crashed, then the location table entry and presence information of this user would be wrong for the rest of the hour. How do I get around this? I assume server can send periodic OPTION messages but that would be a bit expensive. Thank you very much! Yufei -- Yufei

Re: [SR-Users] sr-users Digest, Vol 81, Issue 7

ter.org > > You can reach the person managing 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..." > > >

[SR-Users] TCP keepalive on server and client

d it make 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! Y

Re: [SR-Users] problem forking to dbaliase

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

[SR-Users] problem forking to dbaliase

} 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 Tao Red Embedded This E-mail and any attach

Re: [SR-Users] dialog table entry not deleted after call if in-dialog requests are challenged

and try again? > > 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_ma

Re: [SR-Users] dialog table entry not deleted after call if in-dialog requests are challenged

when everything > was successful. > > Can you enable logging of queries in database 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 res

Re: [SR-Users] dialog table entry not deleted after call if in-dialog requests are challenged

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 that: $DLG_status=5. But the dialog entry

[SR-Users] dialog table entry not deleted after call if in-dialog requests are challenged

;, 1) # don't use did, so to cope with clients that don't preserve parameters # and mode 1 (fallback to 3261 matching) didn't work?? modparam("dialog", "dlg_match_mode", 2) modparam("dialog", "profiles_no_value", "inbound ; outbound