Thanks,

I was able to suspend the transaction and wait for the register but the client that sends the INVITE get unavailable right after the other side joins.

Here is my debug flow:

Client A sends the INVITES.

Use case 1: Client B register one time. Then I turn off the WiFi in client B so it will not recieve the push notification. Client A sends the INVITE, server sends the PUSH and Client A is waiting for 5 seconds.

Use case 3: Same as before but now client B get the push. This time client A that sends the INVITE gets from the server unavailable as soon as client B register.

I did as you suggested and suspend the trunsaction before sending the push. Probably a second suspend is needed when client B sends the REGISTER?

Thanks and regards,

Nir

On Wed, Jul 20, 2016 at 4:06 PM, Federico Cabiddu <federico.cabiddu@gmail.com> wrote:

Hi,
to set the timeout for a specific transaction you can use tm module function t_set_fr (http://www.kamailio.org/docs/modules/devel/modules/tm.html#tm.f.t_set_fr).
For example you could call it before suspending the transaction setting a short timeout and then call it again in the reply route when receiving the first provisional response from the client.

Regards,

Federico

On 20 Jul 2016 2:50 pm, "Nahum Nir" <hello.shalom.hi@gmail.com> wrote:
Hello,

How can I chage the timer waiting for the client to send the register. i.e. how much time to wait for the push?

Thanks,
Nir

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users