Re: [reSIProcate-users] header(h_SessionExpires).param(p_refresher)

[Ruadhri Howman <ruadhri@xxxxxxxxx>]

Hi Scott,

Thanks for all of that.

I'm not sure how to get the system to behave as I want: which is to have the Callee do the refreshing.

I've had another read of RFC 4028, and I don't see how I can negotiate the refresher.

In section 7.1 it states:

   The UAC MAY include the refresher parameter with value 'uac' if it
   wants to perform the refreshes.  However, it is RECOMMENDED that the
   parameter be omitted so that it can be selected by the negotiation
   mechanisms described below.


(First, this implies that the UAC shouldn't set the refresher to 'uas'. So what I was doing last time was illegal anyway.)

In the "negotiation mechanisms described below", I couldn't see anything which said when it was ok to modify the refresher (unless one of the proxies/UAC/UAS didn't support it) -- only the Session-Expires. 

Also, having removed the changes I described in my previous email, I've tried all four settings for masterProfile->setDefaultSessionTimerMode:
Profile::PreferRemoteRefreshes
Profile::PreferLocalRefreshes
Profile::PreferUACRefreshes
Profile::PreferUASRefreshes

And all result in the Caller (me) doing the refresh.

The response to my initial INVITE always sets the refresher to 'uac' so that may well be the expected and correct behaviour.

So, in summary, is there any way I can get the Callee to do the refreshing?


Thanks,
Ruadhri.