sobomax     2008/12/24 11:46:03 CET

  SER CVS Repository

  Modified files:
    .                    main.c rtpp_command.c rtpp_session.c 
                         rtpp_session.h 
  Log:
  o Make disconnect notification feature actually usable:
  
   - Don't remove "unix:" prefix twice from the same argument;
  
   - remove "unix:" prefix in the command handler as well so that we compare
  apples to apples, not apples to oranges;
  
   - make reconnect feature actually working by not reusing a single socket
  create by the socket(2) system call on startup, but instead allocating a
  new one when connection fails. I don't know about all operating systems,
  but FreeBSD doesn't allow to use connect(2) on such a failed socket;
  
   - advertize the feature in the capabilities check command;
  
   - allow the software which reqests notification to pass arbitrary
  URL-encoded string, which the RTPproxy should send as a notification when
  session timeouts. This allows for example B2BUA to pass down command to
  forcefully disconnect session;
  
   - when the previously connected notification socket fails, try to
  reconnect and re-send command instead of just dropping it. Only if the
  second attempt fails drop notification request.
  
  o Use HAVE_SOCKADDR_SUN_LEN instead of checking for the OS type.
  
  o Move atexit() little bit further to match our custom version code.
  This should be a NOP.
  
  o Fix typo in the "20081102" capability description.
  
  Revision  Changes    Path
  1.87      +4 -8      rtpproxy/main.c
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/main.c.diff?r1=1.86&r2=1.87
  1.23      +29 -8     rtpproxy/rtpp_command.c
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_command.c.diff?r1=1.22&r2=1.23
  1.13      +27 -7     rtpproxy/rtpp_session.c
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_session.c.diff?r1=1.12&r2=1.13
  1.17      +9 -4      rtpproxy/rtpp_session.h
http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/rtpproxy/rtpp_session.h.diff?r1=1.16&r2=1.17
_______________________________________________
Devel mailing list
[email protected]
http://lists.rtpproxy.org/mailman/listinfo/devel

Reply via email to