Samuel Vinson wrote: > For the moment I haven't much time to do this, but if you give more > information maybe I can try. I'm thinking to handle this in the client registration session (sip_reg.c). This should be rather straightforward. If we get 423, parse the Min-Expires, update the interval, and re-send REGISTER request. It's similar to what we do to handle 401/407 response. thanks, -benny > Samuel > > Benny Prijono a ?crit : >> Klaus Darilion wrote: >> >>>> Hi Samuel, >>>> >>>> currently pjsip does not interpret this header (it was intentionally >>>> left for application), so I guess for now probably we could only >>>> manually set the registration timeout to 1800. >>>> >>> can pjsua handle this correctly? >>> >> Nope. It was not implemented because we used to use REGISTER request >> as mean for keeping the NAT binding open, so automatically extending >> the registration interval didn't sound like good idea. But now that >> keep alive is done with CRLF, maybe now we can handle this >> automatically in pjsip. >> >> Now if only somebody could create a patch for this. ;-) >> >> cheers, >> -benny >> >> >>> regards >>> klaus
