I expect this should really go to the H.323 Implementors list, but maybe some people out there want to answer James.
-----Original Message----- From: Yu, James [mailto:james.yu@neustar.com] Sent: Thursday, September 06, 2001 2:29 PM To: 'sip-h323@yahoogroups.com' Subject: RE: [sip-h323]
Charles,
Cisco has a proposal to support number portability for H.323. My question on H.323 is "who, the GK or GW, will do the NP queries? I guess that either one can do it but just want to know in the real world who will be doing that.
James -----Original Message----- From: Agboh, Charles [mailto:charles.agboh@ebone.com] Sent: Tuesday, July 31, 2001 6:17 PM To: 'sip-h323@yahoogroups.com' Subject: RE: [sip-h323]
Hi Ranjit,
I believe TRIP will close that gap (contact details and thier expiration/keepalive).
Regards, Charles -----Original Message----- From: Ranjit Kumar Avasarala [mailto:ranjitka@email.masconit.com] Sent: Wednesday, August 01, 2001 12:02 AM To: sip-h323@yahoogroups.com Subject: RE: [sip-h323]
Hi Charles, But RFC 2543 does not mandate processing of Expires header. What is says is time duration mentioned in Expire header field can be used as upper limit For the user to respond. So since it is optional it depends on the SIP Proxy / Registrar implementation. I was thinking of the case Where it is not implemented. Regards Ranjit Mascon Communication Technologies http://www.masconit.com Ph: 847-240-2444 -----Original Message----- From: Agboh, Charles [mailto:charles.agboh@ebone.com] Sent: Tuesday, July 31, 2001 4:42 PM To: 'sip-h323@yahoogroups.com' Subject: RE: [sip-h323] Hi, Ranjit; You may have looked at this but, the Expires header and optional "expires" Contact parameter is just for that (Expires t; where t is time in seconds (i.e. 0)). See Section 4.2.6 of http://www.cs.columbia.edu/sip/drafts/draft-ietf-sip-rfc2543bis-02.pdf for details. Also see section 7.4 of http://www.cs.columbia.edu/sip/drafts/draft-ietf-sip-rfc2543bis-03.pdf. I hope this helps. Regards, Charles
-----Original Message----- From: Roy, Radhika R, ALCTA [mailto:rrroy@att.com] Sent: Tuesday, July 31, 2001 11:19 PM To: sip-h323@yahoogroups.com Subject: RE: [sip-h323]
Hi, Ranjit:
Yes, it is an issue (especially for the IWF where it will be working on behalf of many users).
Our work is to limit ourselves within the context of RFC 2543.
However, if there are any good proposals, we can make suggestion to the SIP WG for the future improvement.
Alternatively, we can also work for some best current practices or experimental documents separately based on our collectives experiences (e.g., your suggestions for solving some of the problems for the IWF).
Let us collect all the issues and, please provide more comments like this.
Best regards, Radhika
-----Original Message----- From: Ranjit Kumar Avasarala [mailto:ranjitka@email.masconit.com] Sent: Tuesday, July 31, 2001 5:15 PM To: sip-h323@yahoogroups.com Subject: RE: [sip-h323]
Hi Radhika,
Ya I am talking of SIP side.
In SIP there is no mechanism for the registrar to indicate to user agents that their registration has expired. So it should be either responsibility of UA to periodically monitor its registration status or registrar should Notify the UA about its registration status.
I feel this could be a problem if IWF behaving like SIP UA and registers with SIP registrar using REGISTER method
Thanks
Ranjit -----Original Message----- From: Roy, Radhika R, ALCTA [ mailto:rrroy@att.com mailto:rrroy@att.com ] Sent: Tuesday, July 31, 2001 3:48 PM To: sip-h323@yahoogroups.com Subject: RE: [sip-h323]
Hi, Ranjit:
IWF will have its two sides: SIP (UA) and H.323.
Now for the SIP side, it will behave like a SIP UA and, its relationship with the SIP REGISTER will be in accordance to RFC 2543. So, some of the behaviors that you are describing may be applicable in this context.
Best regards, Radhika
-----Original Message----- From: Ranjit Kumar Avasarala [ mailto:ranjitka@email.masconit.com mailto:ranjitka@email.masconit.com ] Sent: Tuesday, July 31, 2001 4:43 PM To: sip-h323@yahoogroups.com Subject: [sip-h323]
Hi
Say IWF is registered with Sip registrar in SIP networkand with GK in the H323 zone.
Say the registration has expired after some time. Now registrar has no means
of notifying IWF that its registration has expired.
So I feel IWF should periodically monitor if its registration is active or the Registrar should send CANCEL message SIP
Messages from IWF. Then IWF will come to know that its registration has expired and will re register.
Regards
Ranjit
Yahoo! Groups Sponsor
< http://rd.yahoo.com/M=210948.1523299.3088501.1269402/D=egroupw eb/S=17050047 <http://rd.yahoo.com/M=210948.1523299.3088501.1269402/D=egroup web/S=17050047
26:HM/A=733441/R=0/* http://altfarm.mediaplex.com/ad/ck/1177-3936-1039-2?mpt= http://altfarm.mediaplex.com/ad/ck/1177-3936-1039-2?mpt= 996611651>
< http://us.adserver.yahoo.com/l?M=210948.1523299.3088501.126940
2/D=egroupmai
<http://us.adserver.yahoo.com/l?M=210948.1523299.3088501.12694
02/D=egroupmai
l/S=1705004726:HM/A=733441/rand=317565678>
To Post a message, send it to: sip-h323@eGroups.com
To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service < http://docs.yahoo.com/info/terms/
http://docs.yahoo.com/info/terms/ > .
------------------------ Yahoo! Groups Sponsor ---------------------~--> Small business owners... Tell us what you think! http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/26EolB/TM http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/26EolB/TM ---------------------------------------------------------------------~-> To Post a message, send it to: sip-h323@eGroups.com To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ http://docs.yahoo.com/info/terms/
Yahoo! Groups Sponsor
<http://rd.yahoo.com/M=210948.1523299.3088501.1269402/D=egroupweb/S=17050047
26:HM/A=733441/R=0/*http://altfarm.mediaplex.com/ad/ck/1177-3936-1039-2?mpt=
996613626>
<http://us.adserver.yahoo.com/l?M=210948.1523299.3088501.1269402/D=egroupmai
l/S=1705004726:HM/A=733441/rand=622034757> To Post a message, send it to: sip-h323@eGroups.com To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service http://docs.yahoo.com/info/terms/ .
To Post a message, send it to: sip-h323@eGroups.com To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
------------------------ Yahoo! Groups Sponsor ---------------------~--> Small business owners... Tell us what you think! http://us.click.yahoo.com/vO1FAB/txzCAA/ySSFAA/26EolB/TM ---------------------------------------------------------------------~-> To Post a message, send it to: sip-h323@eGroups.com To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
To Post a message, send it to: sip-h323@eGroups.com
To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
To Post a message, send it to: sip-h323@eGroups.com
To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
Yahoo! Groups Sponsor ADVERTISEMENT
You can, too! Start here...
Height: 345678 ft 01234567891011in
Weight: lbs. kg.
To Post a message, send it to: sip-h323@eGroups.com
To Unsubscribe, send a blank message to: sip-h323-unsubscribe@eGroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For help on this mail list, send "HELP ITU-SG16" in a message to listserv@mailbag.intel.com