19 Nov
2003
19 Nov
'03
9:52 p.m.
Indeed. A phone from an unnamed vendor likes sending in-dialog OPTIONs, others
love to send INFO,and so on and so forth. If you don't watch for follow-up
requests, you may end up running out of sequence or racing with parallel
requests. Eventually, the recepient will report out-of-order requests and
deny BYEs.
So to get it right, you will end up with a call stateful server. We have such,
I will be happy to take it off-line if you are interested.
-jiri
At 05:36 PM 11/19/2003, Jan Janak wrote:
Greg,
Theoretically it is possible, but you must examine every message within
that dialog because they increment CSeq. What you need to remember is
From, To, Contact, CSeq, and Route set for both sides.
Jan.
On 19-11 10:22, Greg Fausak wrote:
--
Jiri Kuthan http://iptel.org/~jiri/
I've been toying with a couple ideas on
terminating
an in process call. I'm thinking that a BYE instruction
send to the FIFO device will do just that. For example:
UA -> SER -> Gateway (call setup worked fine, call in progress).
Then, at a later time, inject a BYE to the UA and to the Gateway
for the call ID. If I save a packet, say the initial INVITE, can I
simply increment the SEQ, change the METHOD to BYE, and squirt it
into the SER FIFO towards the endpoints? Has anyone done this?
Thanks,
---greg
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers