Correct I just have to make sure that set_contact_alias is used in the
initial dialog.
I was doing the the NAT fixes after the initial dialog.
On Tue, Feb 7, 2017 at 11:23 PM, Daniel-Constantin Mierla wrote:
> Hello,
>
> ok, so it was the missing of set_contact_alias(), right?
>
> Cheers,
> Dani
Hi.
>> Can you provide more details for what you need it,maybe we can provide some
>> hints?
I want to store the data of registered users (location) in the database
cassandra (it would be great also dialog stored in cassandra).
>>Can you provide access to a test system/vm where to try to fix it
That is accurate. The external IP info ends up in the received
column/attribute.
On Wed, Feb 08, 2017 at 01:33:56PM -0600, JR Richardson wrote:
> Hi All,
>
> Just confirming when using nathelper, the fix_nated_register function
> is only used to write corrected contact into to $avp then to datab
Hi All,
Just confirming when using nathelper, the fix_nated_register function
is only used to write corrected contact into to $avp then to database,
this function does not actually change the contact in the SIP message
when passing through the proxy, correct?
fix_nated_contact is used to actually
Hello,
Help me with a question. Is it possible to change the prohirity of a
Kamailio Dispatcher target at run time, without changing the destination
entry in the database?
If so, which module should I use?
Have you some link for support?
Thank you very much.
--
Rodrigo M.
(37) 9132-4539
(34) 98
Auth was failing on the server with -5. We need someone more familiar with
kamailio to take a look.
I am attaching earlier follow-up message.
-Original Message-
From: Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Sent: Tuesday, February 07, 2017 10:47 PM
To: Pranathi Venkatayogi ;
Hello,
My small contribution to Kamailio's documentation:
https://www.voztovoice.org/?q=node/1491
If you find any error, please write me.
Regards
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.o
On Wed, Feb 08, 2017 at 12:28:36PM +0200, Arsen wrote:
> I am not sure that nat_uac_test can determine type of NAT device.
> and why you need all these checks if you always use rtpproxy? (another q
> from 2013 :)
The answer is: you don't have to.
> The idea is to reduce using of rtpproxy for bet
Hi Daniel,
I am not sure that nat_uac_test can determine type of NAT device.
and why you need all these checks if you always use rtpproxy? (another q
from 2013 :)
The idea is to reduce using of rtpproxy for better scalability and voice
quality. If we can beat all types of NAT with a near-end NAT
On Wed, Feb 08, 2017 at 01:12:05AM -0700, Arsen Semionov wrote:
> good question from 2013 :)
> Maybe someone has experience and can confirm this?
The answer to the 2013 question is: if you can depend on this (I have
never seen it) you can script kamailio to make use of it.
> My main question: is
Hello,
The challenge with Blink (v3.0.0) is that it seems I can't define any
additional credentials regarding the MSRP connection. I assumed Blink
would use the SIP credentials for MSRP connection but it seems I was
wrong. This would explain the Kamailio behaviour on not authenticating
the cli
Hello,
in our Kamailio, we are using python_exec to execute script used to send
push notifications to Google or Apple.
Currenty, the method we call only accepts the message as parameter. We then
extract from the message the Call Id, to URI and from URI.
Here is the python method signature:
*de
Hi guys!
good question from 2013 :)
Maybe someone has experience and can confirm this?
My main question: is it possible to determine when it's required to use RTP
proxy ? In other words can we know that the client is behind symmetric NAT
device or we just use rtpproxy as a silver bullet?
Thanks!
13 matches
Mail list logo