Re: [reSIProcate-users] Remove customized headers from the REGISTER request message during refresh
CSeq will be one for first request, then 2 if the request was
challenged, refreshes should then start incrementing from either 1 or
2.
Scott
On Wed, Feb 4, 2009 at 10:22 PM, Wong Kok Meng-a17866
<kokmeng.wong@xxxxxxxxxxxx> wrote:
> Hi,
>
> Outbound decorators will apply to initial and refresh requests. Is there
> a way to differentiate them? Is it sufficient by checking CSeq header?
>
> Regards,
> Kok Meng
>
> -----Original Message-----
> From: slgodin@xxxxxxxxx [mailto:slgodin@xxxxxxxxx] On Behalf Of Scott
> Godin
> Sent: Wednesday, February 04, 2009 1:06 PM
> To: Wong Kok Meng-a17866
> Cc: resiprocate-users@xxxxxxxxxxxxxxx
> Subject: Re: [reSIProcate-users] Remove customized headers from the
> REGISTER request message during refresh
>
> I think outbound decorators may be the only route to do this. see
> Profile::setOutboundDecorator.
>
> On Mon, Feb 2, 2009 at 9:39 AM, Wong Kok Meng-a17866
> <kokmeng.wong@xxxxxxxxxxxx> wrote:
>> Hi,
>>
>> In the initial REGISTER request message, I added a few customized
>> headers. During REGISTER refresh, I would like to exclude these
>> customized headers in the request message.
>>
>> I understand there is no onReadyToSend() for client registration, how
>> can I exclude certain headers in the REGISTER refresh request message?
>>
>> Thank you,
>> Kok Meng, Wong
>> _______________________________________________
>> resiprocate-users mailing list
>> resiprocate-users@xxxxxxxxxxxxxxx
>> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>>
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>