Hello,
I don't know if this has already been reported, but I've downloaded kamailio
4.0.2 and tried to compile it with db_unixodbc. I got the following error:
CC (gcc) [M db_unixodbc.so] _con.o
_con.c:34:17: fatal error: con.h: No such file or directory
compilation terminated.
make[1
Can someone let me know how I can increase the registration expiration time for
my endpoint devises? Currently the expiration time is at 60 secs. Thank you.
U 2013/07/03 04:39:53.000710 71.252.xxx.xxx:1029 -> 10.164.62.166:5060
REGISTER sip:54.235.xx.xx SIP/2.0.
Via: SIP/2.0/UDP
192.168.1.8:506
Hello,
I pushed a patch in master that detects when the dialog is created by
not getting to transaction due to a stateless reply.
http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sip-router;a=commitdiff;h=fa0339b1906690f009786fc9ed92c73a8c9e6520;hp=b4682cac2e2f151288a411018da077b6d1526eca
If so
This is how my sip capture looks. I am making a call from ext 1002 to 1004.
U 2013/07/02 21:13:32.876503 50.84.xxx.yyy:61472 -> 10.164.62.166:5060
SIP/2.0 180 Ringing.
Via: SIP/2.0/UDP 54.235.xxx.xxx:5060;branch=z9hG4bKb0be.e57d8ce.0.
Via: SIP/2.0/UDP
50.84.xxx.xxx:5065;rport=5065;branch=z9hG4bK
I've been struggling getting sipsak to perform srv lookups. I have exhausted my
options and wanted to reach out and see if there was any input.
I compiled c-ares library and afterwards compiled sipsak, sipsak configure
script detected the c-ares librarys, however when performing any sipsak comma
We've been using RTPProxy behing a Dlink router from hell for 2 years
now (SIP ALG mangling and everything). No problems here
PS Make sure your "C=", and RR are correct. If not, fix them with the proxy.
N.
___
SIP Express Router (SER) and Kamailio
That's what I thought, thanks.
From: Carlos Ruiz Díaz
To: Kamailio (SER) - Users Mailing List
Sent: Tuesday, July 2, 2013 2:40 PM
Subject: Re: [SR-Users] Issue with RTP proxy
Not true. I'm running RTP proxy behind NAT without problems.
On Tue, Jul 2
Not true. I'm running RTP proxy behind NAT without problems.
On Tue, Jul 2, 2013 at 3:22 PM, Sergey Okhapkin
wrote:
> That might not work. Substituting of advertise IP address is not enough.
> NAT
> router could mangle IP port too.
>
> Once again - RTP proxy must run on a public IP address. The
Does that mean that Kamailio can not be installed on an ec2 instance ?
From: Sergey Okhapkin
To: arun Jayaprakash ; Kamailio (SER) - Users
Mailing List
Sent: Tuesday, July 2, 2013 2:22 PM
Subject: Re: [SR-Users] Issue with RTP proxy
That might not work
That might not work. Substituting of advertise IP address is not enough. NAT
router could mangle IP port too.
Once again - RTP proxy must run on a public IP address. There are no
workarounds.
On Tuesday 02 July 2013 12:16:40 arun Jayaprakash wrote:
> ...also
>
> listen=udp:10.164.62.166:5060
...also
listen=udp:10.164.62.166:5060 advertise 54.235.xx.xx:5060
From: Daniel-Constantin Mierla
To: arun Jayaprakash ; Kamailio (SER) - Users
Mailing List
Sent: Tuesday, July 2, 2013 12:41 PM
Subject: Re: [SR-Users] Issue with RTP proxy
On 7/2/1
Daniel, I have installed the new version of rtpproxy from GIT. Now I am not
getting any errors but I am not getting any audio at all ( not even one way).
This is what I have for my modparameters:
modparam("rtpproxy", "rtpproxy_sock", "udp:127.0.0.1:7722")
modparam("nathelper", "force_socket", "u
Hi Daniel,
this is probably just me, but Google always messes around with the
documentation from the early versions of Kamailio to the latest ones when
searching. This could confuse the new comers.
Thanks for pointing me out to the right direction.
Carlos
On Tue, Jul 2, 2013 at 1:45 PM, Daniel
On 7/2/13 7:05 PM, Nick Khamis wrote:
RTPProxy can run on a natted (i.e., bridged mode) environment without
any patches using rtpproxy_offer/answer("ie","IP") etc...
If you are on a public IP just use MediaProxy
RTPProxy runs well on the public address, being actually the most common
use ca
Hello,
your links are to old versions, but also mixed.
With latest stable version is easier just to use 'advertise' for listen
parameters:
- http://www.kamailio.org/wiki/cookbooks/4.0.x/core#listen
That's all, so there is no need for a complex config logic using
advertised_address and preset
Hi,
you can also check the RTPProxy replacement from Sipwise:
- https://github.com/sipwise/mediaproxy-ng
It supports working behind NAT with advertised IPs. I've used it on
Amazon EC2 myself.
Kind regards,
Carsten
2013/7/2 Daniel-Constantin Mierla :
>
> On 7/2/13 6:44 PM, arun Jayaprakash wrot
On 7/2/13 7:01 PM, arun Jayaprakash wrote:
Can you please give me some pointers as to how to apply this patch, I
have never done one in the past. Thank you.
I guess you can find good tutorials online on how to use patch tool or
understand patching mechanisms.
Or if it is ok, just take the who
On 7/2/13 6:44 PM, arun Jayaprakash wrote:
Daniel, so you are saying that the machine running RTP proxy should
not be a natted one but should have its own public IP?
RTP proxy can run on a natted system such as ec2, but i can listen only
on local ip, not on the public one. The advertised addres
Hi,
rtpproxy needs to bind to an IP that, as well, needs to be bound to a
network interface. In case you are dealing with a Kamailio installation
behind NAT, you have to instruct rtproxy to advertise an address (public
IP) that it doesn't have locally. That's the reason the patch is needed.
Simil
RTPProxy can run on a natted (i.e., bridged mode) environment without
any patches using rtpproxy_offer/answer("ie","IP") etc...
If you are on a public IP just use MediaProxy
N.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
Can you please give me some pointers as to how to apply this patch, I have
never done one in the past. Thank you.
Regards,
Arun
From: Sergey Okhapkin
To: arun Jayaprakash ; Kamailio (SER) - Users
Mailing List
Sent: Tuesday, July 2, 2013 11:49 AM
Subject:
How else?
On Tuesday 02 July 2013 09:44:48 arun Jayaprakash wrote:
> Daniel, so you are saying that the machine running RTP proxy should not be a
> natted one but should have its own public IP?
>
> Thanks,
> Arun
>
>
>
>
>
> From: Daniel-Constantin Mierla
>
Daniel, so you are saying that the machine running RTP proxy should not be a
natted one but should have its own public IP?
Thanks,
Arun
From: Daniel-Constantin Mierla
To: Kamailio (SER) - Users Mailing List
Sent: Tuesday, July 2, 2013 10:53 AM
Subject: Re:
On 7/2/13 5:11 PM, David | StyleFlare wrote:
Daniel,
I am confused, I thought that patch is not really needed?
Indeed, the patch is not really needed when you have a single instance
of rtpproxy and know its public ip. But when you deal with many
rtpproxies, then you cannot deal from config. A
Good evening Gary.
1.- With regard to session control you can also implement with htable module
(avoiding orphan dialog module).
INVITE transaction
$sht(channels=>$ci) = $avp(s:caller_uuid);
BYE/on_failure transaction
$sht(channels=>$ci) = NULL;
CHANNEL CONTROL ROUTE ->
.
if ( $
On 7/2/13 4:50 PM, Fred Posner wrote:
This is awesome... did it say which version of RTP Proxy or did I just
not RTFM well enough?
The patch on github is to latest git version of rtpproxy (I cloned the
git rtpproxy repository from sourceforge to my github).
But it can be easily extracted and
Daniel,
I am confused, I thought that patch is not really needed?
On Ec2 you should be able to bind to the Local IP and then pass the
External IP to rtp-manage.
Am I missing something here?
Should effectively be the same thing.
On 7/2/13 10:50 AM, Fred Posner wrote:
This is awesome... did
This is awesome... did it say which version of RTP Proxy or did I just
not RTFM well enough?
Fred Posner | Team Forrest / LOD
direct: 503-914-0999 | fax: 954-472-2896
On 07/02/2013 10:17 AM, Daniel-Constantin Mierla wrote:
Hello,
have you re-installed rtpproxy from sources after applying the
Now that you mention it, it makes perfect sense since this function sends
BYE to both legs which only makes sense with confirmed dialogs.
I run out of alternatives. Maybe patching the module is the only solution.
Regards,
Carlos
On Tue, Jul 2, 2013 at 10:16 AM, Charles Chance <
charles.cha...@s
Hello,
have you re-installed rtpproxy from sources after applying the patch I
provided the link to?
Cheers,
Daniel
On 7/2/13 3:33 PM, arun Jayaprakash wrote:
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722
rtpproxy: invalid option -- 'A'
usage: rt
That doesn't work I'm afraid. Also from
http://www.kamailio.org/docs/modules/3.1.x/modules_k/dialog.html#id2524783:
*Note: Works only for confirmed dialogs.*
It's something I've been meaning to look further into for a while, but
haven't yet had chance. I suspect a small patch will be required th
Ok, I haven't noticed that, although I can't tell for sure whether it will
work or not.
If you can dump the dialogs using xmlrpc or rpc interface, maybe you could
parse the info and tear down those unconfirmed dialogs using dlg_end_dlg:
http://www.kamailio.org/docs/modules/3.1.x/modules_k/dialog.
The parameter does not work for us. We have modparam("dialog",
"default_timeout",7200), but it only has an effect on confirmed dialogs. As
you can see from my previous example, there is not even a "timestart" value
on the unconfirmed dialog, so how can Kamailio know when timeout is
reached?
On 2
There is, but for all dialogs, not only the unconfirmed ones.
http://www.kamailio.org/docs/modules/3.3.x/modules_k/dialog.html#default-timeout-id
On Tue, Jul 2, 2013 at 9:49 AM, Charles Chance <
charles.cha...@sipcentric.com> wrote:
> Hmm, I don't think there is even a timeout value set on unco
Hmm, I don't think there is even a timeout value set on unconfirmed dialogs
in memory.
Example (Kamailio 3.3.3):
dialog:: hash=1791:10106
state:: 1
ref_count:: 1
timestart:: 0
timeout:: 0
...
Whereas:
dialog:: hash=2963:2808
state:: 4
ref_count:: 2
timestart:: 1372772302
timeout:: 114829207
.
Hi Daniel, I get this error:
rtpproxy -F -l 10.164.62.166 -A 54.x.x.x -s udp:127.0.0.1:7722
rtpproxy: invalid option -- 'A'
usage: rtpproxy [-2fvFiPa] [-l addr1[/addr2]] [-6 addr1[/addr2]] [-s path]
[-t tos] [-r rdir [-S sdir]] [-T ttl] [-L nfiles] [-m port_min]
[-M port_max] [-u u
Am Dienstag, 2. Juli 2013, 14:23:25 schrieb Charles Chance:
> I don't think this will help at all, as regardless of DB mode, unconfirmed
> dialogs are not stored in DB anyway.
>
> The important thing to remember is that if you are calling dialog_manage()
> in your config, to only do it once you ar
What if you set the default dialog timeout to a value much less than 12/14
hours, maybe 2 hours. It's very unlikely that a session last that long.
On Tue, Jul 2, 2013 at 9:23 AM, Charles Chance <
charles.cha...@sipcentric.com> wrote:
> Hi,
>
> I don't think this will help at all, as regardless o
Hi,
I don't think this will help at all, as regardless of DB mode, unconfirmed
dialogs are not stored in DB anyway.
The important thing to remember is that if you are calling dialog_manage()
in your config, to only do it once you are ready to forward the request. If
you call it but then exit for
Thanks for suggestion. I will give it try.
Since every call will have to check database, will this effect the
performance of Kamailio for high volume server?
Gary
On Tue, Jul 2, 2013 at 8:55 AM, I.Pavlov wrote:
> Hi, Gary. I had same problem. Try to use “db_mode” parameter of dialog
> module w
Hi, Gary. I had same problem. Try to use "db_mode" parameter of dialog
module with 1 value.
1 - REALTIME - any dialog information changes will be reflected into the
database immediatly.
Then you can kill the dead dialogs through database.
From: sr-users-boun...@lists.sip-router.org
[mai
Kamailio 3.3.3
I am using dialog module to do the concurrent call limit. Once a while I
got a dead unconfirmed dialog hung in memory. The only way I know to
cleanup this is to restart kamailio. So my questions are:
1) Does anybody know a better way to cleanup the dead dialog without having
to rest
Hello,
make uninstall in kamailio does not actually delete the deployed files.
Just prints the commands you should run.
Therefore be sure you first delete the deployed modules. You can just do:
rm -rf /opt/kamailio/lib64/kamailio/modules/
The be sure you have db_mysql back in the list of inc
Hello,
On 7/1/13 5:48 PM, arun Jayaprakash wrote:
Hello, I have enabled RTP proxy on my machine (ec2 instance) by
running the following script:
rtpproxy -F -l mypublicip -s udp:localhost:7722
but I keep getting this error. The phones ring but there is no audio:
3(4144) ERROR: rtpproxy [rtpp
Hello,
On 7/2/13 6:16 AM, piyush.ban...@relianceada.com wrote:
Hi,
I am a regular user of iptel ser. I am facing an issue while
trying to insert "P-hint" header field in 200 OK response to REGISTER
message. I want to have a condition check. If condition is true, the
P-hint header shou
Hi All,
I tried the steps as requested by Barry.
e.g :
listen=tcp:10.212.129.99:5060 advertise 107.22.60.14:5060
listen=udp:10.212.129.99:5060 advertise 107.22.60.14:5060
After restarting Kamailio, i was able to register with sample app using TCP.
But when i try to send IM, i get 408 Request Ti
46 matches
Mail list logo
