Hi,
I have a question regarding SIP-H323 3PCC interworking draft.
>From what I understand in Figures 5, 6, 7 and 8, IWF receives
TCS from H323 EP and then sends back TCS of it's own. But in
all scenarios it hasn't received any SDP from Controller yet.
Thus, I assume, that the best thing that IWF can do is send
exactly the same TCS that it received.
But that means that H323 EP may choose any coder that it likes
in the following OLC. Or, to be precise, it will most probably
choose the first coder that it put in it's own TCS.
And that means that SDP B (see Figure 7) contains only
one coder (assuming that we have a regular telephony mono voice
conversation). So the SIP EP can either accept or reject this
SDP. But it can hardly be called "coder negotiation".
Does my logic flaw somewhere?
Wouldn't it be better if we introduce additional reINVITE on SIP side,
so that the original INVITE carries full coder list from/to TCS message,
and the reINVITE maps OLC procedure?
Best regards,
Alex Agranov
Senior Software Engineer
Comgates
www.comgates.com
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
