Browse code

phone provisioning added to shopping list

Jiri Kuthan authored on 19/09/2003 23:37:23
Showing 1 changed files
... ...
@@ -11,10 +11,10 @@ I) MUSTs
11 11
 Without MUSTs, I will not like the phone.
12 12
 
13 13
 - Price - get it bellow $100 (I mean for one phone, not for 10.000 of them)
14
-- NAT-Traversal support: STUN, symmetric communication
14
+- NAT-Traversal support: STUN, symmetric communication, comedia
15 15
 - DNS fail-over, as required by specification (I'm aware of only one phones
16 16
   which is getting it right today, 2003-02)
17
-- REFER (correctly please)
17
+- REFER (correctly please, test with CTD)
18 18
 - reasonable provisioning
19 19
 - the phones must be able to detect loss of Ethernet connectivity,
20 20
   display it, and re-REGISTER when reconnected
... ...
@@ -47,3 +47,9 @@ KNOWN ERRORs
47 47
 ------------
48 48
 These are errors we observed frequently to fail in phones: digest/qop, 
49 49
 DNS fail-over, REFER, transaction matching, record-routing.
50
+
51
+NEAR FUTURE REQUIREMENTS
52
+------------------------
53
+Automated phone provisiong is a really big item. It is not thinkable that
54
+sip site operators configure both user accounts at server and credentials
55
+at phone manually. that introduces human factor which is bad.