I agree, usually RFC are created first by university so by
students...
----- Original Message -----
Sent: Thursday, June 10, 2010 12:09
PM
Subject: Re: [Freeswitch-users]
uuid_media hangs
The funny part is you are willing to go to all this effort to
try to make us correct it because you know the other people wont.
This type of finger pointing to RFC is typical to providers so now I
have to do free work to investigate it for you.
And I bet you are paying them money and not us, oh well,
typical.....Don't worry I won't hold it against you.
The philosophical question here is weather or not to send a requires
timer in the reinvite, so ok.
I can try to look it up for you but from a logical point of view, once
you establish in the original invite that you are going to use session
timers, every reinvite constitutes a timer refresh, so once you have agreed
in the original invite to use timers it would stand to reason to require the
timer option in every new re-invite since it represents a timer
refresh.
But, let's face it... Who cares right? its a meaningless param in
an REINVITE. Most sip implementation wing it on most of these packet
parsers. The sofia developers are very keen to actually follow all
these silly RFC you are trying to quote and they have been relaxing it
nonstop ever since because nobody really follows any rules in SIP they just
use them to avoid having to patch their code. Especially in a deployed
appliance in a telco. They are really telling you they can't support
it because the code in their sip gateway fails when it sees this and they
are too lazy to change it so they pray that some RFC will let them off the
hook. Trust me, we've had worse. One place refused our calls
because they did not like the syntax of our user agent string......
So bottom line is I would trust the default behavior of
sofia-sip over most things any day but if they are really doing something
wrong the problem would be in the sofia-sip library not in FreeSWITCH so I
am not sure where to tell you to look in the code to correct it because we
use that code asis and avoid hacking into it a all costs. Try using
grep into the sofia-sip lib for the strings you know are meaningful.
P.S
All the event related things are fixed now, there was a small speed
bump along the way this week.
On Thu, Jun 10, 2010 at 4:34 AM, peely
<freeswitch@peely.com>
wrote:
Hi,
It's not a hijacked thread, I created
this with an issue around uuid_media,
initially it was hanging, then in
the latest git it receives a 4xx from the
far end due to the Requires:
timer support bot being supported in the
reinvite transaction. I did
anecdotally mention problems with events, which
I subsequently pulled
off to another thread.
I was looking at RFC 4028, in the examples
it shows the refresh event not
providing the Required: timer header
even for the refresh of the original
invite transaction, just the
Supported: timer. There's nothing in RFC 3725
regarding sesison timers
in 3PCC but as the reinvite for the media
adjustment is a new
transaction, I don't think it needs the Requires: timer
option to
persist the timer support on the original dialogue. This is
certainly
the behaviour of the previous equipment I had on this interconnect
and
it operates using session timers and 3PCC in several other
environments
too.
I'm not brilliant with C, but if you could
please point me to the right
approach to removing the Requires: timer
field in the header I'd be happy to
test it and let you know if it
causes any problems with rienvites across
various carriers and other
platforms.
Cheers,
Neil.
--
View this message in context: http://freeswitch-users.2379917.n2.nabble.com/uuid-media-hangs-tp5145657p5162317.html
Sent from the freeswitch-users mailing list archive at
Nabble.com.
_______________________________________________
--
Anthony Minessale II
FreeSWITCH
http://www.freeswitch.org/ClueCon
http://www.cluecon.com/Twitter:
http://twitter.com/FreeSWITCH_wireAIM:
anthm
MSN:anthony_minessale@hotmail.comGTALK/JABBER/
PAYPAL:anthony.minessale@gmail.comIRC:
irc.freenode.net
#freeswitch
FreeSWITCH Developer Conference
sip:888@conference.freeswitch.orggoogletalk:conf+888@conference.freeswitch.orgpstn:+19193869900
_______________________________________________
FreeSWITCH-users
mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org