-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I installed today an Aastra SIP-DECT. It works so far pretty well. When I unregister a "portable part" (pp) (which is a handset) I found many of this syslog messages: Nov 4 17:12:47 omm: 0001986827 *** DSIP: [01|-1] Missing expires in REGISTER-2xx, assume 300 s Nov 4 17:12:47 omm: 0001986913 *** DSIP: [01|-1] Missing expires in REGISTER-2xx, assume 300 s Nov 4 17:12:48 omm: 0001987011 *** DSIP: [01|-1] Missing expires in REGISTER-2xx, assume 300 s The result is a (allways successful) unregistering loop done by the aastra base. The first REGISTER from aastra is replyed with 401 by FS. The 2nd REGISTER is replyed with 200 OK. The syslog messages tell me that the aastra dect base is looking for expires header in FS's SIP REGISTER 200 reply. But there is no such field in FS' response. I found this link (http://www.ietf.org/mail-archive/web/sip/current/msg11313.html) where say say that an expires header is neccessary. The RFC 3261 seems to confirm that: "The registrar returns a 200 (OK) response. The response MUST contain Contact header field values enumerating all current bindings. Each Contact value MUST feature an "expires" parameter indicating its expiration interval chosen by the registrar. The response SHOULD include a Date header field." FS's 200 ok reply is this: SIP/2.0 200 OK Via: SIP/2.0/UDP aa.aa.aa.aa;branch=z9hG4bK-655180136fcd67 From: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=f-1a3ec06907bcc23 To: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=vQ7ZUS1aQHNye Call-ID: 1e19ff301a3ec04cd2c75a3@DSIP CSeq: 369236 REGISTER Contact: "PP 1" <sip:4919@aa.aa.aa.aa> Date: Thu, 04 Nov 2010 15:56:37 GMT User-Agent: FreeSWITCH-mod_sofia/1.0.head-git- Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Length: 0 Is this a problem in aastra or in FS? Or is there a way do configure it in FS? What do you think? I use FS trunk. Unfortunately I can't get the revision number but it shouldn't be older than two months. regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzS5PUACgkQ4tZeNddg3dy6xQCcDXGus4NeLGkky1+Hy13W83dT mzQAniDgaydQfK+blJSWC/TdNPi+BF3c =yzsh -----END PGP SIGNATURE-----