Hi
I'm using Kamailio 4.2.4 and rtpengine 4.0.0.0+0~mr4.0.0.0. Kamailio is
configured with sip users that can register. I have also configured a sip
trunk to PSTN. I'm using rtpengine to handle RTP when a client want's to
call to PSTN.
When a user behind NAT wants to make a call to PSTN and sends
Finally, it works!
I keep the previous configuration that I show you but I delete the WHITH_AUTH
define.
This way, all sip-phones and softphones register without any problem (no
UNAUTHORIZED messages from Kamailio). I can see them in my database, in the
“location” table.
Unfortunately, I sti
Hi,
I only add the two defines.The follow is my settings.
#!define WITH_NAT
#!define WITH_NATSIPPIN
modparam("nathelper", "natping_interval", 30)
modparam("nathelper", "ping_nated_only", 1)
modparam("nathelper", "sipping_bflag", FLB_NATSIPPING)
modparam("nathelper", "sipping_from", "si
I know this is an old thread, but I'm having a strange issue like this with
trustedDump and trustedReload in permissions module.
I compiled latest git:
git clone git://git.sip-router.org/kamailio
I can only reload trusted data by restart kamailio
and when I do trustedDump command, i get strange ou
On 21/04/15 10:40 PM, GG GG wrote:
> By port closed, I mean that ports are normally closed, but when
> rtpengine send the first rtp packets to the client, it opens a pinhole
> in the firewall, and the matching incoming packets from the client will
> make the connection established,related in iptabl
Hello,
last day of coding new features for next major release 4.3.
In more details, freezing timeline is 23:59 Kamailian timezone (aka
Hawaii), in other words, North and South America should have also full
day available for pushing new features. The mark will be effectively the
change of the vers
You might want to read up on ICE (STUN & TURN) and SRTP / DTLS which
broadly resolve your issues.
On 21 April 2015 at 23:40, GG GG wrote:
> By port closed, I mean that ports are normally closed, but when rtpengine
> send the first rtp packets to the client, it opens a pinhole in the
> firewall,
Hi Xuefeng,
did you do set any other module parameters?
I can't get it to work..
My UAs uregister only because of expire=300, that means that they go
offline after 5 minutes. Usually UAs have much higher expire=3600, does
that mean they would go offline in 1 hour?
I hoped, that when I set
#!def
Hi,
After restarting Kamailio, I got the following errors during the startup:
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]:
db_mongodb_get_columns(): field [caller_sock] not found in result iterator
kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]:
db_mongodb_store_resu
Hi,
For now, I got it only once, I will keep an eye on it.
Thanks,
Mickael
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: Wednesday, April 22, 2015 12:37 PM
To: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Possib
Subject: [SR-Users] Iterative DNS resolution by enum module ? Date: Wed, Apr
22, 2015 at 11:36:56AM +0200 Quoting jyaim (jya...@gmail.com):
> Hello everyone,
>
> Do you know if the kamailio enum module is able to process
> 'recursives' dns requests in case of CNAME or NS response, until a
> NAPTR
Hello everyone,
Do you know if the kamailio enum module is able to process
'recursives' dns requests in case of CNAME or NS response, until a
NAPTR answer is returned ?
Thanks in advance!
Jy
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-user
Hello,
On 22/04/15 11:26, Mickael Marrache wrote:
>
> Hi,
>
>
>
> I just got the following issue when stopping kamailio.
>
>
>
> kamailio[7279]: NOTICE: [main.c:682]: handle_sigs(): Thank you
> for flying kamailio!!!
>
> kamailio[7279]: ERROR: ctl [ctl.c:369]: mod_destroy(): ERROR: ctl:
> cou
Hello,
ok, perfect!
For sake of information, in the future, if git.kamailio.org is not
responding, one can use the github repository:
- https://github.com/kamailio/kamailio
Anyhow, always report here if git.kamailio.org is not responding, it
has to be fixed.
Cheers,
Daniel
On 22/04/15 10:5
Hi,
I just got the following issue when stopping kamailio.
kamailio[7279]: NOTICE: [main.c:682]: handle_sigs(): Thank you for
flying kamailio!!!
kamailio[7279]: ERROR: ctl [ctl.c:369]: mod_destroy(): ERROR: ctl: could not
delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)
Hello,
now it works! :)
Thank you.
Best regards,
Kai Ohnacker
Von: sr-users [mailto:sr-users-boun...@lists.sip-router.org] Im Auftrag von
Daniel-Constantin Mierla
Gesendet: Mittwoch, 22. April 2015 10:28
An: Kamailio (SER) - Users Mailing List
Betreff: Re: [SR-Users] Problems with git.kamailio.o
Hello,
thanks for reporting, I restarted the git daemon and now all seems ok.
Let us know if works for you now.
Cheers,
Daniel
On 22/04/15 10:20, kai.ohnac...@cbc.de wrote:
>
> Hello,
>
>
>
> is there actually a problem with the git.kamailio.org server?
>
> If I try the command
>
> / /
>
> /gi
Hello,
is there actually a problem with the git.kamailio.org server?
If I try the command
git clone --depth 1 git://git.kamailio.org/kamailio kamailio
or
git clone --depth 1 git://git.sip-router.org/kamailio kamailio
I got the message "fatal: read error: connection reset by peer".
Perhaps it is
Hello,
First, thank you for your quick answer!
When you say it’s a password problem, do you talk about the password of the
user that kamailio use to connect my database?
Because it doesn’t seem to be a connection problem between PostgreSQL and
Kamailio. I think the connection is established betw
19 matches
Mail list logo
