Browse code

initiatl commit of phone shopping list

Jiri Kuthan authored on 28/02/2003 12:58:16
Showing 1 changed files
1 1
new file mode 100644
... ...
@@ -0,0 +1,47 @@
1
+$Id$
2
+
3
+jiri's SIP phone shopping list
4
+------------------------------
5
+
6
+This is Jiri's list of wishes for SIP "hardphones". When there is such
7
+a phone, I will be glad to test it, promote it, and praise the vendor.
8
+
9
+I) MUSTs
10
+
11
+Without MUSTs, I will not like the phone.
12
+
13
+- Price - get it bellow $100 (I mean for one phone, not for 10.000 of them)
14
+- NAT-Traversal support: STUN, symmetric communication
15
+- DNS fail-over, as required by specification (I'm aware of only one phones
16
+  which is getting it right today, 2003-02)
17
+- REFER (correctly please)
18
+- reasonable provisioning
19
+
20
+II) RECOMMENDED
21
+
22
+With RECOMMENDED, I will do like the phone.
23
+
24
+- multiple lines 
25
+- multiple calls
26
+- DTMF
27
+
28
+III) SHOULD
29
+
30
+With SHOULDs, I will fall in love with it.
31
+
32
+- GIPS codec is good
33
+- power-Ethernet
34
+- desktop features: deny incoming call, DnD, 3-rd party conferencing,
35
+  auto-repeat of failed call attempts
36
+- well-readable display, at best backlit
37
+- solid robust design, like with the PBX phones from well-established
38
+  PBX vendors 
39
+
40
+Note there are other lists too -- Henry Sinnreich's draft provides a great
41
+dictate to phone vendors.
42
+http://www.iptel.org/ietf/configuration/#draft-sinnreich-sipdev-req
43
+
44
+KNOWN ERRORs
45
+------------
46
+These are errors we observed frequently to fail in phones: digest/qop, 
47
+DNS fail-over, REFER, transaction matching, record-routing.