I´ve been trying pjsua succesfully, and seems that I have a problem with incoming calls, and refresher interval... This is the brief: 12:07:28.798 <- The incoming INVITE has "Session-Expires: 600" 12:07:28.798 -> SIP/2.0 100 Trying 12:07:31.954 -> SIP/2.0 200 OK with "x: 600;refresher=uac" 12:07:32.110 <- ACK The call is stablished... Some registers 12:10:14.019 -> REGISTER 12:10:14.159 <- SIP/2.0 200 OK ... And now the problem... 12:16:59.946 dlg00c29d18 No session refresh received after 568s (expiration period=600s), stopping session now! 12:16:59.946 -> BYE 12:16:59.993 <- SIP/2.0 200 OK 12:16:59.993 pjsua_app.c Call 0 is DISCONNECTED [reason=408 (Request Timeout)] An the call is closed in 10 minutes by pjsua !!! Please, tellme if refresher=uac ? who has to make the reinvite? pjsua or network side? Thanks in advance

The caller needs to send the re-invite. A timeout after 568 with a negotiated expires of 600 is in order. On 11/08/2011 07:51 PM, segalion wrote: > I´ve been trying pjsua succesfully, and seems that I have a problem > with incoming calls, and refresher interval... > > > This is the brief: > > 12:07:28.798 <- The incoming INVITE has "Session-Expires: 600" > 12:07:28.798 -> SIP/2.0 100 Trying > 12:07:31.954 -> SIP/2.0 200 OK with "x: 600;refresher=uac" > 12:07:32.110 <- ACK > > > The call is stablished... > > > Some registers > 12:10:14.019 -> REGISTER > 12:10:14.159 <- SIP/2.0 200 OK > ... > > > And now the problem... > > 12:16:59.946 dlg00c29d18 No session refresh received after 568s > (expiration period=600s), stopping session now! > 12:16:59.946 -> BYE > 12:16:59.993 <- SIP/2.0 200 OK > 12:16:59.993 pjsua_app.c Call 0 is DISCONNECTED [reason=408 > (Request Timeout)] > > > An the call is closed in 10 minutes by pjsua !!! > > Please, tellme if refresher=uac ? who has to make the reinvite? pjsua > or network side? > > Thanks in advance > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

The caller or the UAC? In http://www.ietf.org/rfc/rfc4028.txt page 9 we can read: ... The 'refresher' parameter will be present in the Session-Expires header field, indicating who will perform the refreshes. The UAC MUST set the identity of the refresher to the value of this parameter. If the parameter contains the value 'uac', the UAC will perform them. ... But probably 2011/11/8 Joegen E. Baclor <joegen.baclor@gmail.com> > ** > The caller needs to send the re-invite. A timeout after 568 with a > negotiated expires of 600 is in order. > > > > On 11/08/2011 07:51 PM, segalion wrote: > > I´ve been trying pjsua succesfully, and seems that I have a problem with > incoming calls, and refresher interval... > > > This is the brief: > > 12:07:28.798 <- The incoming INVITE has "Session-Expires: 600" > 12:07:28.798 -> SIP/2.0 100 Trying > 12:07:31.954 -> SIP/2.0 200 OK with "x: 600;refresher=uac" > 12:07:32.110 <- ACK > > > The call is stablished... > > > Some registers > 12:10:14.019 -> REGISTER > 12:10:14.159 <- SIP/2.0 200 OK > ... > > > And now the problem... > > 12:16:59.946 dlg00c29d18 No session refresh received after 568s > (expiration period=600s), stopping session now! > 12:16:59.946 -> BYE > 12:16:59.993 <- SIP/2.0 200 OK > 12:16:59.993 pjsua_app.c Call 0 is DISCONNECTED [reason=408 (Request > Timeout)] > > > An the call is closed in 10 minutes by pjsua !!! > > Please, tellme if refresher=uac ? who has to make the reinvite? pjsua or > network side? > > Thanks in advance > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing listpjsip@lists.pjsip.orghttp://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > >

 indicating who will perform the refreshes.  The UAC MUST set the
 identity of the refresher to the value of this parameter.  If the
 parameter contains the value 'uac', the UAC will perform them.

 The caller needs to send the re-invite.  A timeout after 568 with
 a negotiated expires of 600 is in order.



 On 11/08/2011 07:51 PM, segalion wrote:

 I´ve been trying pjsua succesfully, and seems that I have a
 problem with incoming calls, and refresher interval...


 This is the brief:

 12:07:28.798 <- The incoming INVITE has "Session-Expires: 600"
 12:07:28.798 -> SIP/2.0 100 Trying
 12:07:31.954  -> SIP/2.0 200 OK with "x: 600;refresher=uac"
 12:07:32.110 <- ACK


 The call is stablished...


 Some registers
 12:10:14.019 -> REGISTER
 12:10:14.159 <- SIP/2.0 200 OK
 ...


 And now the problem...

  12:16:59.946    dlg00c29d18  No session refresh received after
 568s (expiration period=600s), stopping session now!
  12:16:59.946   -> BYE
  12:16:59.993 <- SIP/2.0 200 OK
  12:16:59.993    pjsua_app.c  Call 0 is DISCONNECTED [reason=408
 (Request Timeout)]


 An the call is closed in 10 minutes by pjsua !!!

 Please, tellme if refresher=uac ? who has to make the reinvite?
 pjsua or network side?

 Thanks in advance



 _______________________________________________
 Visit our blog:http://blog.pjsip.org

 pjsip mailing list
 pjsip@lists.pjsip.org  <mailto:pjsip@lists.pjsip.org>
 http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

The "uac" in this context is the initiator of the transaction, thus the caller. If the UAC indicated refresher=uas, then the receiver of the INVITE (callee) must be responsible for the refresh. On 11/09/2011 01:33 AM, segalion wrote: > The caller or the UAC? > > In http://www.ietf.org/rfc/rfc4028.txt page 9 we can read: > > ... > The 'refresher' parameter will be present in the Session-Expires header field, > > indicating who will perform the refreshes. The UAC MUST set the > identity of the refresher to the value of this parameter. If the > parameter contains the value 'uac', the UAC will perform them. > ... > > But probably > > > 2011/11/8 Joegen E. Baclor <joegen.baclor@gmail.com > <mailto:joegen.baclor@gmail.com>> > > The caller needs to send the re-invite. A timeout after 568 with > a negotiated expires of 600 is in order. > > > > On 11/08/2011 07:51 PM, segalion wrote: >> I´ve been trying pjsua succesfully, and seems that I have a >> problem with incoming calls, and refresher interval... >> >> >> This is the brief: >> >> 12:07:28.798 <- The incoming INVITE has "Session-Expires: 600" >> 12:07:28.798 -> SIP/2.0 100 Trying >> 12:07:31.954 -> SIP/2.0 200 OK with "x: 600;refresher=uac" >> 12:07:32.110 <- ACK >> >> >> The call is stablished... >> >> >> Some registers >> 12:10:14.019 -> REGISTER >> 12:10:14.159 <- SIP/2.0 200 OK >> ... >> >> >> And now the problem... >> >> 12:16:59.946 dlg00c29d18 No session refresh received after >> 568s (expiration period=600s), stopping session now! >> 12:16:59.946 -> BYE >> 12:16:59.993 <- SIP/2.0 200 OK >> 12:16:59.993 pjsua_app.c Call 0 is DISCONNECTED [reason=408 >> (Request Timeout)] >> >> >> An the call is closed in 10 minutes by pjsua !!! >> >> Please, tellme if refresher=uac ? who has to make the reinvite? >> pjsua or network side? >> >> Thanks in advance >> >> >> >> _______________________________________________ >> Visit our blog:http://blog.pjsip.org >> >> pjsip mailing list >> pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org> >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

indicating who will perform the refreshes.  The UAC MUST set the
identity of the refresher to the value of this parameter.  If the
parameter contains the value 'uac', the UAC will perform them.

Ok, thanks for your response. Then, problem is on network side, and pjsua is working correctly. Please, can anybody tellme if could be easily to change some parameter (or similar) to offer UAS (and act) as refresher in incomming INVITE calls? Thanks. 2011/11/9 Joegen E. Baclor <joegen.baclor@gmail.com> > ** > The "uac" in this context is the initiator of the transaction, thus the > caller. If the UAC indicated refresher=uas, then the receiver of the > INVITE (callee) must be responsible for the refresh. > > > On 11/09/2011 01:33 AM, segalion wrote: > > The caller or the UAC? > > In http://www.ietf.org/rfc/rfc4028.txt page 9 we can read: > > ... > > The 'refresher' parameter will be present in the Session-Expires header field, > > indicating who will perform the refreshes. The UAC MUST set the > identity of the refresher to the value of this parameter. If the > parameter contains the value 'uac', the UAC will perform them. > > ... > > But probably > > > 2011/11/8 Joegen E. Baclor <joegen.baclor@gmail.com> > >> The caller needs to send the re-invite. A timeout after 568 with a >> negotiated expires of 600 is in order. >> >> >> >> On 11/08/2011 07:51 PM, segalion wrote: >> >> I´ve been trying pjsua succesfully, and seems that I have a problem >> with incoming calls, and refresher interval... >> >> >> This is the brief: >> >> 12:07:28.798 <- The incoming INVITE has "Session-Expires: 600" >> 12:07:28.798 -> SIP/2.0 100 Trying >> 12:07:31.954 -> SIP/2.0 200 OK with "x: 600;refresher=uac" >> 12:07:32.110 <- ACK >> >> >> The call is stablished... >> >> >> Some registers >> 12:10:14.019 -> REGISTER >> 12:10:14.159 <- SIP/2.0 200 OK >> ... >> >> >> And now the problem... >> >> 12:16:59.946 dlg00c29d18 No session refresh received after 568s >> (expiration period=600s), stopping session now! >> 12:16:59.946 -> BYE >> 12:16:59.993 <- SIP/2.0 200 OK >> 12:16:59.993 pjsua_app.c Call 0 is DISCONNECTED [reason=408 (Request >> Timeout)] >> >> >> An the call is closed in 10 minutes by pjsua !!! >> >> Please, tellme if refresher=uac ? who has to make the reinvite? pjsua or >> network side? >> >> Thanks in advance >> >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing listpjsip@lists.pjsip.orghttp://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> >> > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing listpjsip@lists.pjsip.orghttp://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > >