On Apr 11, 2011, at 8:38 pm, Paul Belanger wrote:
On 11-04-11 10:26 AM, Effie Mouzeli wrote:
This may lead to some buggy clients not to accept the call (with 488),
but I've noticed some cases where a callee was behind NAT,
an INVITE with one video codec would me forwarded properly
to the
Not that it has anything to do with this, but after having tried and
failed to use many 1.8 betas and most of the 1.8 release versions,
yesterday I followed the instructions on how to get trunk and my
problem with 1.8 is fixed.
It involved this error:
WARNING[24384] chan_sip.c:
Hi all,
I realise that asterisk's codec negotiation has been discussed in
the past multiple times. What I haven't been able to understand is
how asterisk decides which video codecs to advertise to the other
end when canreinvite=no in sip.conf and the initial caller
doesn't support video.
On 11-04-11 10:26 AM, Effie Mouzeli wrote:
This may lead to some buggy clients not to accept the call (with 488),
but I've noticed some cases where a callee was behind NAT,
an INVITE with one video codec would me forwarded properly
to the callee, but another INVITE with 3 video codecs, would
