Aastra SIP-DECT and UNREGISTER from FreeSWITCH
-----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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again, I wiresharked the registering process now and here is the 200 ok reply from FS: SIP/2.0 200 OK Via: SIP/2.0/UDP aa.aa.aa.aa;branch=z9hG4bK-1065d870d0bfc57 From: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=f-4ef46703147946f6 To: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=3Dr3pc2Q15Fgj Call-ID: 1cd92cc94ef6d804cd2e6b46@DSIP CSeq: 110118 REGISTER Contact: "PP 1" <sip:4919@aa.aa.aa.aa>;expires=600 Date: Thu, 04 Nov 2010 16:59:55 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 As you can see there is an "expires" parameter in Contact header. regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzS590ACgkQ4tZeNddg3dzSYwCfa00u+OlEY05Qcv2mLDLy2xcO 8HgAn1Muhnd2VypuOliC7a6JWJiIiEQY =cAKq -----END PGP SIGNATURE-----
This is a bounty/feature request on Jira. We don't currently support this fetch operation. /b On Nov 4, 2010, at 12:05 PM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi again,
I wiresharked the registering process now and here is the 200 ok reply from FS:
there is a feature request open for this already on jira with a semi completed patch. On Thu, Nov 4, 2010 at 12:05 PM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi again,
I wiresharked the registering process now and here is the 200 ok reply from FS:
SIP/2.0 200 OK Via: SIP/2.0/UDP aa.aa.aa.aa;branch=z9hG4bK-1065d870d0bfc57 From: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=f-4ef46703147946f6 To: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=3Dr3pc2Q15Fgj Call-ID: 1cd92cc94ef6d804cd2e6b46@DSIP CSeq: 110118 REGISTER Contact: "PP 1" <sip:4919@aa.aa.aa.aa>;expires=600 Date: Thu, 04 Nov 2010 16:59:55 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
As you can see there is an "expires" parameter in Contact header.
regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkzS590ACgkQ4tZeNddg3dzSYwCfa00u+OlEY05Qcv2mLDLy2xcO 8HgAn1Muhnd2VypuOliC7a6JWJiIiEQY =cAKq -----END PGP SIGNATURE-----
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org googletalk:conf+888@conference.freeswitch.org pstn:+19193869900
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Anthony, as far as I see the mentioned patch doesn't address my problem. I looked into "sofia-reg.c" and found that FS's already append "expires" to "contact-header" when a SIP client is registering (as mentioned below). I applied the following patch which solves the issue with Aastra DECT SIP OMM-RFPs to sofia_reg.c: index 67641ae..a94a93a 100644 - --- a/src/mod/endpoints/mod_sofia/sofia_reg.c +++ b/src/mod/endpoints/mod_sofia/sofia_reg.c @@ -1437,6 +1437,7 @@ uint8_t sofia_reg_handle_register(nua_t *nua, sofia_profile_t *profile, nua_hand } #endif } else { + sip_contact_add_param(nua_handle_home(nh), sip->sip_contact, "expires=0"); if (switch_event_create_subclass(&s_event, SWITCH_EVENT_CUSTOM, MY_EVENT_UNREGISTER) == SWITCH_STATUS_SUCCESS) { switch_event_add_header_string(s_event, SWITCH_STACK_BOTTOM, "profile-name", profile->name); switch_event_add_header_string(s_event, SWITCH_STACK_BOTTOM, "from-user", to_user); The only thing what happens is to add "expires=0" parameter to contac-header when replying "200 OK" to a client's (UN-)REGISTER message. Shall I open an issue in Jira? regards helmut Am 04.11.2010 18:44, schrieb Anthony Minessale:
there is a feature request open for this already on jira with a semi completed patch.
On Thu, Nov 4, 2010 at 12:05 PM, Helmut Kuper <helmut.kuper@ewetel.de> wrote: Hi again,
I wiresharked the registering process now and here is the 200 ok reply from FS:
SIP/2.0 200 OK Via: SIP/2.0/UDP aa.aa.aa.aa;branch=z9hG4bK-1065d870d0bfc57 From: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=f-4ef46703147946f6 To: "PP 1" <sip:4919@bb.bb.bb.bb>;tag=3Dr3pc2Q15Fgj Call-ID: 1cd92cc94ef6d804cd2e6b46@DSIP CSeq: 110118 REGISTER Contact: "PP 1" <sip:4919@aa.aa.aa.aa>;expires=600 Date: Thu, 04 Nov 2010 16:59:55 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
As you can see there is an "expires" parameter in Contact header.
regards helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzieLsACgkQ4tZeNddg3dxJpACfapgSUpPocn1QJmHKxtqUTSOS Ha4An12EjWIbCOLTqqaTA/ipAPLoaOF9 =j3bn -----END PGP SIGNATURE-----
Here is the jira: http://jira.freeswitch.org/browse/FS-790 The attached patch is done incorrectly. /b On Nov 4, 2010, at 11:53 AM, Helmut Kuper wrote:
-----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-----
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi again, I've opened up a jira issue to this bug: http://jira.freeswitch.org/browse/FS-2875 regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzs2ekACgkQ4tZeNddg3dxOYwCfYqTGazmLq7x7L9gFLjBAHte3 fKUAnj82LGY19hYzKTrN7bnyu1fnuaVT =lrdV -----END PGP SIGNATURE-----
Hello Helmut, we discovered the same thing with Aastra OMMs firing a number requests when a handset is deregistered. Asking Aastra for a feedback did not get a solution. So now we are happy to have at least a patch for this. Best regards Peter Helmut Kuper schrieb:
Hi again,
I've opened up a jira issue to this bug: http://jira.freeswitch.org/browse/FS-2875
regards helmut
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org -- With kind regards Peter Steinbach Telefaks Services GmbH Theo-Geisel-Strasse 25 D 61250 Usingen, Germany mailto:lists (att) telefaks.de Internet: www.telefaks.de
participants (4)
-
Anthony Minessale
-
Brian West
-
Helmut Kuper
-
Peter Steinbach