sorry，I have not expressed clearly.
kamailio will recive two REGISTER at a time.In first 200 OK to REGISTER,
Server will tell Linphone the Linphone Nat Ip and Port.
like this:
Via:SIP/2.0/TCP 30.9.2.1:50691
;received=42.1.7.1;alias;branch=z9hG4bK.kmhC2L9Rf;rport=33746
and Linphone will know it's o
On Tue, Mar 15, 2016 at 1:19 AM, Shiv Patidar
wrote:
> Thank you for help
> For registration , we would like to see the complete traces at all nodes
> whoever processing UE sending REGISTER method.
> could you please let me know how can we check the logging at all IMS nodes?
> i am able to succes
Hi:
I am sure this has been answered before on this list and I have tried the basic
answers I got from Google without any luck. Any suggests would be great.
The Kamailio host is running Oracle Linux 6.7 (64 bit) and is fully patched as
of today.
The Kamailio version is:
Server:: kamailio (4.3.4
Currently (AFAIK), restarting Kamailio amidst production call processing
is basically "safe"; except for no availability during the few seconds
it takes to restart (which will just result in retransmissions until it
is available), most things will happen "correctly" after restart even
though TM
Hi Daniel,
Actually I see I need to go to 4.3 to use the ds_default_socket parameter.
Will go to 4.3 and see how it goes.
Thanks
Jon
modparam("dispatcher", "ds_default_socket", "udp:192.168.0.125:5060")
From: hunter...@hotmail.com
To: mico...@gmail.com; sr-users@lists.sip-router.org
Date: Mon, 14 M
Thank you for help
For registration , we would like to see the complete traces at all nodes
whoever processing UE sending REGISTER method.
could you please let me know how can we check the logging at all IMS nodes?
i am able to successfully register and got 200OK but i want understand what
and all
Hi Daniel,
Thanks for the reply, sorry I keep missing you ! :)
I have added force_send_socket in the correct places now , and I can now make
inbound/outbound calls are required.
However with dispatcher, when Im trying to send SIP options pings to gateways
defined, I see these errors;
RROR: dis
Hello Daniel,
Carrier: 10.0.0.1
Kamailio 1: 10.14.0.1
Kamailio 2: 10.14.0.2
I also removed the SDP from the INVITE and the 183 messages.
This is the trace from the Kamailio which directly communicates with the
Carrier.
U 10.14.0.2:5060 -> 10.14.0.1:5060
INVITE sip:0031123456789@10.14.0.1:5060
Hello,
what would be relevant here is seeing the INVITE request sent to
10.14.0.1:5060 -- paste it to the mailing list discussion. That is going
to be used to generate 487, and the Via stack from it should be used there.
Cheers,
Daniel
On 14/03/16 13:23, Grant Bagdasarian wrote:
>
> Hello,
>
>
Indeed, the ports are different, that's why adding received is important
in this situation.
While local ip and local port are in most of the cases also unique for
devices behind a nat router, it is not 100% true, because there can be
many layers of NATs, which can result in seeing same local ip/po
Hello,
We're testing kamailio 4.3.4 with two kamailio's communicating with each other.
One of them is a gateway with rtpengine at the carrier side, the other is a
basic sip router.
When calling a destination and cancelling the INVITE a 487 is received from the
carrier and directly ACK'd by the
source IP is same, But port is different。
like INVITE sip:Linphone_nat_Ip:Linphone_nat_port;tcp;
2016-03-14 18:26 GMT+08:00 Daniel-Constantin Mierla :
> Adding received information to Path helps to identify properly the
> connection to be used. Because both devices are behind the same NAT,
> p
Hello,
with current stable version (4.3.x), see the utils module, it offers the
function for http query. In the past, whenever I needed some complex
http query, I used embedded lua interpreter (app_lua module).
Upcoming stable (4.4.0, to be out in about 2 weeks or so), has more
options here, two
I am using kamailio without database.
It works fine.
For some scenario, I would like to replace the from uri (using
mac_replace_from works fine) but using data I can accessed with a REST API.
I want to have different origination depending on the sipusername.
I need to have some synchronous reques
Hello,
On 07/03/16 16:29, jaflong jaflong wrote:
> Hi everyone
>
> How can I generate a random port number, one that is currently available to
> bind to.
> I want to assign this to the media parameter in the sdp
I think you should use here rtpproxy or rtpengine, if you need to relay
the rtp.
If
Adding received information to Path helps to identify properly the
connection to be used. Because both devices are behind the same NAT,
practically they show the same source IP when they send traffic to server.
Cheers,
Daniel
On 14/03/16 04:05, 张顺通 wrote:
> KA_EDGE have two IP，external public IP
CC-ing Ovidiu, the author of the module, maybe he can assist here and
add a bit to documentation as well...
Cheers,
Daniel
On 13/03/16 19:03, Uri Shacked wrote:
> Thank Alex, I find great comfort for not being the only one :-)
> Actually, after straggling for a while I managed to send the followi
Hello,
so you complain, too ... but your name is at the top of the
documentation file for xhttp_rpc module. I expect you used it as you
contributed there already, maybe adding a bit more would help the
others, too :-)
Daniel
On 13/03/16 18:44, Alex Balashov wrote:
> Hello,
>
> It is indeed a pit
Hello,
not using this module here -- so just replying to point to other
modules, like jsonrpc-s, where the command is provided in a more
standard format. Also, xmlrpc module can be an option. Both of them use
http just as transport layer.
Cheers,
Daniel
On 13/03/16 18:38, Uri Shacked wrote:
> Hi
19 matches
Mail list logo
