[SR-Users] Capturing-200 Okey(with SDP) from cfg

2013-11-01 Thread Surendra
Hi all, I have a requirement , i.e. I need to capture 200 ok(with SDP) from cfg file. This 200 okey will be getting once the called party answers the call. Can anyone help me to get out of this. Regards Surendra ___

[SR-Users] using timer in kamailio

2013-11-01 Thread Karimi-Cherkandi, Bizhan
I am currently using register_timer() to register one of ,my timers. Any idea how I would delete this timer later? I noticed that register_timer is new, the functions timer_del() and timer_free() are old and expect 'struct timer_ln *' which I do not have (this is not used in register_timer())

Re: [SR-Users] Kamailio - RTPProxy - Asymmetric RTP

2013-11-01 Thread Daniel Grotti
Hi, you can try also to set flag 'a' in on_reply route for that peer: a - flags that UA from which message is received doesn't support symmetric RTP. (automatically sets the 'r' flag) Don't know if it can help, never tested. As far as I know if rtpproxy receives RTP stream for port X, it will

Re: [SR-Users] Capturing-200 Okey(with SDP) from cfg

2013-11-01 Thread Daniel Grotti
Hi, what do you mean with "capture from cfg file" ? Do you want to log 200OK message in kamailio log file ? Daniel On Friday, November 1, 2013 08:36 CET, "Surendra" wrote: > Hi all, > > > > I have a requirement , i.e. I need to capture 200 ok(with > SDP) from cfg file

[SR-Users] msilo - use case: registered but not reachable

2013-11-01 Thread Marc M .
Hi! I have a simple msilo setup which is working fine: -If the user is registered, the messages are delivered right away -If the user is not registered, the messages are stored in msilo and got deliverd at the next register Here is the relevant part of the cfg: --- if (is_metho

Re: [SR-Users] Kamailio - RTPProxy - Asymmetric RTP

2013-11-01 Thread Daniel-Constantin Mierla
Hello, indeed, 'a' flag should be used for asymmetric rtp. However, iirc, in some cases when one side was symmetric and the other one not, the rtp didn't flow properly. I had to use fix_contact_sdp() followed by msg_apply_changes() for the party behind the nat to make it trustable-ip in sdp.

Re: [SR-Users] msilo - use case: registered but not reachable

2013-11-01 Thread Daniel-Constantin Mierla
Hello, you have to set a failure route for MESSAGE request before relaying it. In failure route, you can call m_store(). If you look at current default config file, it has something similar for INVITE, to send it to voicemail if it is not answered. Cheers, Daniel On 11/1/13 2:05 PM, Marc M

Re: [SR-Users] Kamailio - RTPProxy - Asymmetric RTP

2013-11-01 Thread Lucas Girard
It works !! "a" flag in rtpproxy_manage() solve it. I can see that similar ports are used in flow, but seems like "a" flag instructs the rtpproxy or kamailio to listen properly. Thanks a lot team !! Lucas Girard On Fri, 2013-11-01 at 15:28 +0100, Daniel-Constantin Mierla wrote: > Hello, > > in

Re: [SR-Users] using timer in kamailio

2013-11-01 Thread Daniel-Constantin Mierla
Hello, a note: make a new email when having a new topic, because you get into old email discussion thread when you reply, even when you change the subject. If you want to control better the timer, then you have to use lower functions, such as timer_init(), timer_add() ... see the content of

Re: [SR-Users] dispatcher: what is the syntax for dispatcher list file

2013-11-01 Thread Daniel-Constantin Mierla
Hello, On 9/27/13 6:10 PM, Karimi-Cherkandi, Bizhan wrote: I figured out the correct syntax: URI:: sip:10.233.20.106:5060;transport=tcp flag=A priority=2 attrs='bijan=xyz;td=1' Now the remaining question is: can dispatcher pass the priority to kamailio, for instance over an AVP? no. Mayb

Re: [SR-Users] Incoming call problem

2013-11-01 Thread Daniel-Constantin Mierla
Hello, On 10/30/13 3:22 PM, Jason Sia wrote: Hi, I have kamailio server and a freeswitch server during a call the kamailio passes the call to freeswitch to play a media and back to kamailio for routing to the destination, this works fine however for samsung devices (any ROM using linphone).

Re: [SR-Users] Incoming call problem

2013-11-01 Thread Juha Heinanen
Daniel-Constantin Mierla writes: > With upcoming 4.1, the behavior should be unified as for udp, and get in > a failure_route. yes, i can confirm that udp and tcp behave the same way in 4.1. the only difference is that in tcp case it takes much longer before failure is detected and failure rout