<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2963" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>I <SPAN class=683100312-21052009>improved
</SPAN>trau_mux.c. Now it supports not just bridging only. A new function
"trau_recv_lchan" is used to link a channel to a call reference<SPAN
class=683100312-21052009> </SPAN>of a transaction. <SPAN
class=683100312-21052009>(Transactions are used in later patches.) </SPAN>TRAU
frames will then be forwarded<SPAN class=683100312-21052009> </SPAN>to the
application with the given call reference<SPAN class=683100312-21052009> (in
later patches)</SPAN>. Also the application can send TRAU frames by using
"trau_send_lchan".</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>A new list is introduced in trau_mux.c.
(upqueue_entry) All subslots that must be sent to application are listed
here.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Received TRAU frames are written in the upqueue of
application interface, if a call reference is found in the upqueue-list. If an
entry is found the ss_entry list, the TRAU frames are bridged as before. The
frames have a message type (msg_type), a call reference (callref) and a
trau frame (data). The length of trau frame is defined by the content of
the c-bits inside the frame.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>There is no support for ip-access yet. Harald must
add this in order to use application interface with ip-access. The bridging with
ip-access<SPAN class=683100312-21052009> </SPAN>works as before.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2> </DIV></FONT></BODY></HTML>