Difference between revisions of "Introduction"

From TD-er's Wiki
Jump to navigationJump to search
m
 
m
 
Line 1: Line 1:
Setting up Trixbox for H323 <-> SIP telephony is not a straightforward procedure. There is basically only one source of information and that is the Trixbox forum. The people on this forum who have a working configuration all integrate a hardware H323 system (like cisco call manager) with the trixbox. We started out trying to directly connect our H323 extensions to the trixbox but this did not seem possible. As a solution we started working with an H323 gatekeeper to handle H323 functionality and let the Trixbox function as gateway. After playing around with the configuration of clients, gk and Trixbox we are able to let H323 -> SIP and SIP -> H323 ring but as soon as it is picked up the call is terminated by the Trixbox. We can handle H323 -> H323 by the just the gatekeeper. At first we thought this might be a codec problem but when we use the same client with SIP there is no problem. Also enabling just one codec on both the SIP and H323 client gives the same problem with no reference to a codec problem in any of the logs.  
+
Setting up Trixbox for H323 <-> SIP telephony is not a straightforward procedure. There is basically only one source of information and that is the Trixbox forum. The people on this forum who have a working configuration all integrate a hardware H323 system (like cisco call manager) with the trixbox. We started out trying to directly connect our H323 extensions to the trixbox but this did not seem possible. As a solution we started working with an H323 gatekeeper to handle H323 functionality and let the Trixbox function as gateway. After playing around with the configuration of clients, gk and Trixbox we are able make SIP -> H323 call. We can let H323 -> SIP ring but as soon as it is picked up the call is terminated by the Trixbox. We can handle H323 -> H323 by the just the gatekeeper.  
  
To have come this far we have had extensive help from one person on the Trixbox forum who has a large H323 and sip network and we followed all his suggestions. What follows is the configuration of Trixbox, GnuGK gatekeeper and different H323 clients as we have it right now. We have intensely studied the output of the asterisk OOH323 and SIP debugger and the gatekeeper logs to figure out what goes wrong with this configuration but they do not show what the problem is. We think that it might be that the gatekeeper does not offer enough functionality to replace the hardware solutions other people have found.
+
To have come this far we have had extensive help from one person on the Trixbox forum who has a large H323 and SIP network and we followed mostly his suggestions. What follows is the configuration of Trixbox, GnuGK gatekeeper and different H323 clients as we have it right now.  
 
 
There is another post on the forum by somebody who seems to do it in a different way. If he talking about integrating a network or loose extensions is not clear. We have not had time to investigate his solution. It seems like an awful lot of compiling but it might be worth a try.  
 
  
 
Several people on the forum advise to use trixbox 1.2.3 since they find ooh323 does not work on trixbox 2.0. They also use a very specific version of the asterisk add-ons.
 
Several people on the forum advise to use trixbox 1.2.3 since they find ooh323 does not work on trixbox 2.0. They also use a very specific version of the asterisk add-ons.

Latest revision as of 14:09, 8 March 2007

Setting up Trixbox for H323 <-> SIP telephony is not a straightforward procedure. There is basically only one source of information and that is the Trixbox forum. The people on this forum who have a working configuration all integrate a hardware H323 system (like cisco call manager) with the trixbox. We started out trying to directly connect our H323 extensions to the trixbox but this did not seem possible. As a solution we started working with an H323 gatekeeper to handle H323 functionality and let the Trixbox function as gateway. After playing around with the configuration of clients, gk and Trixbox we are able make SIP -> H323 call. We can let H323 -> SIP ring but as soon as it is picked up the call is terminated by the Trixbox. We can handle H323 -> H323 by the just the gatekeeper.

To have come this far we have had extensive help from one person on the Trixbox forum who has a large H323 and SIP network and we followed mostly his suggestions. What follows is the configuration of Trixbox, GnuGK gatekeeper and different H323 clients as we have it right now.

Several people on the forum advise to use trixbox 1.2.3 since they find ooh323 does not work on trixbox 2.0. They also use a very specific version of the asterisk add-ons.