>
> Hi,
>
> The iPhone client, when it goes into background, can only respond to
> incoming messages.
> That makes the Registration expire when there is no communication from the
> server before
> the expire time. I could make the Registration not expire at all. Not sure
> it's the only option.
>
> Is there a way to send a Ping message from server periodically to the
> iPhone SIP client. This
> will wakeup the SIP client and resend REGISTER message.
>
> Thanks
> Krish Kura
>
Hi,
When a user is removed using "kamctl rm", is there way way to clean up
presence information
in the database (xcap, presentity, watcher and active watcher tables) and in
the cache? Is there a
event that gets fired when the user is removed from subscriber table which
I could handle in config
file and and cleanup?
Thanks
Krish Kura
Hi All,
Kamailio 3.1.2 generate a core in db_text module when subscriber table is
updated and after this action some SIP message require authentication
process...
Someone Can Help me to understand why this core is happening? Below is part
of kamailio's trace and gdb core too.
Kamailio's trace:
*Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2327]: DEBUG:
auth_db [authorize.c:239]: realm value [192.168.166.199]*
Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2327]: DEBUG:
auth [api.c:95]: auth: digest-algo: MD5 parsed value: 1
*Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2327]: DEBUG:
db_text [dbt_file.c:78]: [subscriber] was updated*
Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2324]: ALERT:
<core> [main.c:741]: child process 2327 exited by a signal 11
Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2324]: ALERT:
<core> [main.c:744]: core was generated
Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2324]: INFO:
<core> [main.c:756]: INFO: terminating due to SIGCHLD
Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2335]: INFO:
<core> [main.c:807]: INFO: signal 15 received c
Sep 22 16:35:54 sswpst00 /home2/local/kamailio/sbin/kamailio[2335]: DEBUG:
<core> [main.c:818]: Memory status (pkg):
gdb core trace:
Core was generated by `/home2/local/kamailio/sbin/kamailio -P
/var/run/kamailio.pid'.
Program terminated with signal 11, Segmentation fault.
*#0 0x00f21603 in dbt_db_del_table (_dc=0xb6071e60, _s=0xbf837040, sync=0)
at dbt_lib.c:238*
238 dbt_lib.c: Arquivo ou diretório não encontrado.
in dbt_lib.c
Best Regards
Hello,
On 9/30/11 12:11 AM, JJ Zeng wrote:
>
> Thanks Daniel. I followed your advice and install kamailio 3.1. Now
> I get a weird problem: it works 1 out 5 times for the relaying.
>
try to set like tcp_connection_lifetime=3604 global parameter, or to a
value higher than the longer registration time.
>
> The t_relay is where the the problem is, because I check the response
> code and route(LOCATION) always succeeds, which means the entries
> exist in "location".
>
> If I don't put set_forward_no_connect, then t_relay will take a long
> time until my client time out. If I put it, then the client will get
> 477 right away.
>
> BTW, the original config didn't work, either. That's why I started to
> strip down some irrelevant stuff.
>
What errors you got with the default config?
Cheers,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Dec 5-8, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hello,
please keep the mainling list cc-ed.
Calling ds_select_dst() first in the main route block is not really a
good place. First you have to handle sanity checks, within dialog
requests a.s.o. Of course it is a matter of your purpose, but as general
hint, selecting the destination should be done just (or as close as
possible) before relaying.
If you take default config and you have only load balancing, then you
can replace location lookup part with load balancing. Other parts may be
stripped as well, just giving some direction here.
Cheers,
Daniel
On 9/28/11 11:11 PM, Henrik Aagaard Sørensen wrote:
> That did the job.
>
> I just placed the ds_select_dst-code at the very first thing after route{
>
> Thank you for your help!
>
> 2011/9/28 Daniel-Constantin Mierla <miconda(a)gmail.com
> <mailto:miconda@gmail.com>>
>
> Hello,
>
> the devel version of dispatcher module README has a different
> config example, maybe it helps you more:
>
> http://kamailio.org/docs/modules/devel/modules_k/dispatcher.html#id2522847
>
> I am considering to update it again soon to be a bit more complete
> and follow the structure of the default config file shipped with
> kamailio.
>
> Cheers,
> Daniel
>
>
> On 9/28/11 6:30 PM, Henrik Aagaard Sørensen wrote:
>> Hi Carsten.
>>
>> The configuration works. It's actually where (which line) in the
>> configuration I should put:
>> ds_select_dst("1", "0");
>>
>> :) I'm not strong in Kamailio and just want it to load balance
>> between Freswitch servers. So I have a basic installation of
>> Kamailio, without MySQL, NAT, Auth etc.
>>
>> On Wed, Sep 28, 2011 at 5:09 PM, Carsten Bock
>> <carsten(a)ng-voice.com <mailto:carsten@ng-voice.com>> wrote:
>>
>> Hi,
>>
>> When you've got problems with placing "ds_select_dst()" in your
>> config, you should do the following:
>> - Open an Editor of your choice
>> - go to the line, where you want to place it
>> - type: ds_select_dst("1", "0");
>> - save & exit
>>
>> Just kidding! You should do the following with your config:
>> kamailio -f <path-to-your-config> -c
>>
>> What error is displayed? If none, then check your syslog for
>> errors.
>> Could you post your config? It is better to put a full path
>> in the
>> config to the dispatcher-file... otherwise it might be
>> dependent of,
>> where you are running the init.d-skript/kamailio....
>>
>> I am using dispatcher in Kamailio 1.5, 3.1 and 3.2,
>> everythings works
>> fine with me.
>>
>> Kind regards,
>> Carsten
>>
>> 2011/9/28 Henrik Aagaard Sørensen
>> <henrikaagaardsorensen(a)gmail.com
>> <mailto:henrikaagaardsorensen@gmail.com>>:
>> > I've installed 2 Freeswitch on different servers and would
>> like to have
>> > Kamailio load balance between them.
>> >
>> > I've installed Kamailio following:
>> >
>> http://www.kamailio.org/dokuwiki/doku.php/install:kamailio-3.1.x-from-git
>> >
>> > I've created dispatcher.list and added:
>> >
>> > loadmodule "dispatcher.so"
>> >
>> > modparam("dispatcher", "list_file", "../etc/dispatcher.list")
>> >
>> > in the kamailio.cfg.
>> >
>> > But looking at:
>> >
>> http://kamailio.org/docs/modules/3.1.x/modules_k/dispatcher.html
>> > I'm having difficulties to placing:
>> >
>> > ds_select_dst("1", "0");
>> >
>> > in the kamailio.cfg that was created originally.
>> >
>> > Can anyone help me?
>> >
>> > _______________________________________________
>> > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
>> mailing list
>> > sr-users(a)lists.sip-router.org
>> <mailto:sr-users@lists.sip-router.org>
>> > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>> >
>> >
>>
>>
>>
>> --
>> Carsten Bock
>> CEO (Geschäftsführer)
>>
>> ng-voice GmbH i. Gr.
>> Schomburgstr. 80
>> D-22767 Hamburg / Germany
>>
>> http://www.ng-voice.com
>> mailto:carsten@ng-voice.com <mailto:carsten@ng-voice.com>
>>
>> Mobile +49 179 2021244 <tel:%2B49%20179%202021244>
>> Office +49 40 34927219 <tel:%2B49%2040%2034927219>
>> Fax +49 40 34927220 <tel:%2B49%2040%2034927220>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
>> mailing list
>> sr-users(a)lists.sip-router.org
>> <mailto:sr-users@lists.sip-router.org>
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org>
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
> --
> Daniel-Constantin Mierla --http://www.asipto.com
> Kamailio Advanced Training, Oct 10-13, Berlin:http://asipto.com/u/kat
> http://linkedin.com/in/miconda -- http://twitter.com/miconda
>
>
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda
Hey again,
Btw: I am using Kamailio 3.1.5 and found the event_route in 3.2.x Dispatcher
documentation. Is there a possibility in 3.1.x?
Greetings
Timo
Von: sr-users-bounces(a)lists.sip-router.org
[mailto:sr-users-bounces@lists.sip-router.org] Im Auftrag von Timo Klecker
Gesendet: Donnerstag, 29. September 2011 11:10
An: 'kamailio users'
Betreff: [SR-Users] Logmessage when Dispatcher-Module sets a dispatcher to
probing
Hey,
I'd like to have a log-entry in the kamailio logfile when
#ds_probind_threshhold OPTIONS pings fail to reach a dispatcher (408 localy
generated after #fr_timer ms). Is it possible to do this without changing
code?
Greetings
Timo
Hi,
I am really new to ser(just installed it today). My situation is here:
Both A and B make tcp connection to ser proxy server. If A sends "Invite" to B, ser would look up the tcp connection of B, and relay the sip request. If B is not connected, then 480 is returned to A. When B sends back the response, ser would relay it to A.
It looks really simple, but I just can't figure out how to do it.
Thanks.
JJ
Hey,
I'd like to have a log-entry in the kamailio logfile when
#ds_probind_threshhold OPTIONS pings fail to reach a dispatcher (408 localy
generated after #fr_timer ms). Is it possible to do this without changing
code?
Greetings
Timo
Hello list.
I'm trying to test/implement http://www.openimscore.org/ to setup an IMS
scenario for development purposes. The project seems quite inactive to me
and I wonder if there is any other similar project or this one just died and
is no longer maintained.
The documentation didn't specify if there is any kind of compatibility with
Kamailio and based on what was written, only SER core architecture is
supported.
Any help will be appreciated.
Regards.
Carlos.
Hello,
in preparation for release 3.2.0, I was checking our wiki (on
kamailio.org), which is quite rich in information, but some tutorials
are for older versions.
Maybe it is also a good time to do some restructuring along with the
update of the useful tutorials to be valid for 3.2.0.
For restructuring, the main goal is to provide some ways to let people
find the documentation they need (and it is available there) easier.
Some ideas, introducing categorization/tags for specific topics (e.g.,
radius, ldap, presence, asterisk, ...), introducing some index pages to
link tutorials per version, etc.
More suggestions are welcome here, let us know what will make your life
easier in browsing the docs.
On another hand, currently wiki is based on dokuwiki, which from my
point of view did good job so far, but maybe we are missing another
excellent wiki system that we should use, because provides more tools
for this kind of purpose. One thing I was missing, was export to pdf,
which I may be possible right now with dokuwiki plugins -- or even
better, we can get something to export to docbook xml format with
dokuwiki or other wiki system.
In the same kind of subject, what about using git to store (or at least
have a replica of) the wiki pages? IIRC, I saw somewhere that even for
dokuwiki is possible to configure to use a git repository to store the
wiki content instead of local CVS. This will allow people to mirror very
easy the content. I could spot from time to time web spiders downloading
the wiki.
Comments or other suggestions to make the access to documentation easier?
Thanks,
Daniel
--
Daniel-Constantin Mierla -- http://www.asipto.com
Kamailio Advanced Training, Oct 10-13, Berlin: http://asipto.com/u/kathttp://linkedin.com/in/miconda -- http://twitter.com/miconda