Hi Dan, Please, see this sequence: ****** Register Cseq: 101 REGISTER Contact: <sip:pa...@192.168.15.100:3265;LINEID=b1e36a3c3798> ********
************* Status-Line: SIP/2.0 401 Unauthorized Cseq: 101 REGISTER /******************/ /***********/ Register Cseq: 102 REGISTER *Contact: <sip:pa...@my_public_ip:3265;LINEID=b1e36a3c3798>* *API should use this new contact, ok?* ********/ /**************/ Status-Line: SIP/2.0 200 OK Cseq: 102 REGISTER Contact: <sip:pa...@my_public_ip:3265;LINEID=b1e36a3c3798>;*expires=300* /***************************/ in the SipRefreshMgr::parseContactFields we have: if ( returnedIdentity.compareTo(requestContactIdentity) == 0 ) it is comparing: returnedIdentity = pa...@my_public_ip:3200 to requestContactIdentity = pa...@*192.168.15.100*:3200 so that it does not grab to the new expire value I think that requestContactIdentity should be updated to Cseq: 102 REGISTER Contact: <sip:pa...@my_public_ip:3265;LINEID=b1e36a3c3798> Regards Paulo On Thu, Mar 19, 2009 at 10:54 AM, Daniel Petrie <dpet...@sipez.com> wrote: > > Hi Paulo: > At the SIP stack level we support both. I assume you are asking about > REGISTER transactions? If you are using the sipXtapi inteface to register > lines, it uses SipRefreshMgr which always sends the expiration as a > parameter in the Contact header of the REGISTER request, but will look for > the expiration header and expiration parameter of the contact header in the > REGISTER response. > > Cheers, > Dan > > --- On Wed, 3/18/09, Paulo Vicentini <vicentini.pa...@gmail.com> wrote: > > > From: Paulo Vicentini <vicentini.pa...@gmail.com> > > Subject: [sipxtapi-dev] SIP Expires > > To: sipxtapi-dev@list.sipfoundry.org > > Date: Wednesday, March 18, 2009, 9:26 PM > > Hi,Is sipxtapi assumed to > > support expires Contact header parameter or just Expires > > header field or both?thanksPaulo > >
_______________________________________________ sipxtapi-dev mailing list sipxtapi-dev@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
