Browse code

comment on CTD using precomputed dialog state

Jiri Kuthan authored on 01/03/2003 16:28:56
Showing 1 changed files
... ...
@@ -26,10 +26,17 @@
26 26
 # ------------
27 27
 # it only works with UACs supporting REFER; it has been tested 
28 28
 # with Cisco 7960 and Mitel 5055; Windows Messenger does not
29
-# support REFER; dialog parser over-simplified (see inline) but 
30
-# quite functional (if there is something to be fixed, it is
31
-# richness of SIP syntax); an awk-only rewrite would be esthetically
32
-# nicer, imho. Never tested on solaris.
29
+# support REFER. Never tested on solaris. Dialog parser 
30
+# over-simplified (see inline) but  quite functional 
31
+# (if there is something to be fixed, it is richness of SIP 
32
+# syntax); an awk-only rewrite would be esthetically
33
+# nicer, imho. Another design alternative would be to
34
+# create all the dialog values (route set, outbound uri,
35
+# request uri) in ser, and similarly to vm module return
36
+# them through FIFO. The CTD app would just then mirror
37
+# them in subsequent requests and would not have to recompute 
38
+# everything. One would just compute dialog info, put it in 
39
+# beginning of FIFO reply, followed by the reply.
33 40
 #
34 41
 # History:
35 42
 # --------