50 likes | 208 Views
SIP Telephony Device Requirements draft-sinnreich-sipping-device-requirements-00.txt. Daniel Petrie dpetrie@pingtel.com SIPPING WG 18 Mar 2002. SIP Telephony Device Requirements. <draft-sinnreich-sipping-device-requirements-00.txt>, informational. With companion drafts:
E N D
SIP Telephony Device Requirementsdraft-sinnreich-sipping-device-requirements-00.txt Daniel Petrie dpetrie@pingtel.com SIPPING WG 18 Mar 2002 SIP Device Requirements
SIP Telephony Device Requirements <draft-sinnreich-sipping-device-requirements-00.txt>, informational • With companion drafts: • "A Framework for SIP User Agent Configuration" • <draft-petrie-sip-config-framework-01.txt> • "SIP End Point Configuration Data Format Requirements" • <draft-stredicke-sipping-ep-config-00.txt> Buy SIP phones and configure over the network Consistent operation by ISPs and/or Enterprises • Protocols • Configuration processes • Media and codecs • Echo control • Services supported by SIP telephony devices • User interface • LANs and power SIP Device Requirements
Scope Issues • Line Echo Cancellation – Not applicableRemoveITU-T G.168, not G.165 • Acoustic Echo Cancellation • Hands free/Speeker phone – Not in scopePrice point/vendor decision • Handset – In scope (the thing you hold not the whole device)Mechanical & Accoustic coupling: • ANSI/EIA/TIA-810-A-2000 • TIA/EIA-579-A • LAN Based devices – In scope(e.g. Fixed and wireless) • Mobile Devices – Not in scope(e.g. 3G) SIP Device Requirements
Misc. Issues • SHOULD/MUST provide translation from local emergency number to sos URL • SHOULD provide ability to disallow REFERLarger scope than REFERAddress this in: draft-ietf-sipping-cc-framework-00.txt • Make this a SIPPING WG Item SIP Device Requirements
Comments received on the Requirements I-D Count: 1 for wireline phones, 1 generic SIP, 2 for wireless devices Robert Born: • Acoustic properties: Specify ITU-T G.168, not G.165 • Acoustic-electrical for IP/packet: ANSI/EIA/TIA-810-A-2000 • Stability and minimum loss: TIA/EIA-810-A and TIA/EIA-579-A Yaron Sheffer: • DHCP is a MUST • HTTP and DNS in client, server or both • Emergency URL – write just “sos” for non-technical people • ILBR codec: Need reference draft • Supported services: In server or phone? • Disabling SIP REFER – “SHOULD” for security reasons Karl Pospisek: • GSM-EFR codec MUST be supported, though GSM-AMR is the 3G choice Ashutosh Dutta: • Used Columbia SIPC (also in Linux) IPAQs/802.11b, CDPD, CDMA1XRTT SIP Device Requirements