Has anyone here done this? I got it compiled just fine but when I make a call I do not get any audio going either way. The * box is not behind any sort of firewall or nat. My H323 client (gnomemeeting) is behind NAT but I have it set up properly to work through NAT and it will talk correctly with my other regular x86 box running H323. One odd thing I note is that when looking at the UDP traffic with tcpdump I see the * box receiving my UDP packets but never transmitting anything. SIP works just fine and is talking to my TNT. I am trying to receive incoming H323 to terminate to the call on the TNT. Linux mybox 2.6.9-1.667 #1 Tue Nov 2 14:50:10 EST 2004 x86_64 x86_64 x86_64 GNU/Linux Asterisk CVS-HEAD-11/17/04-21:47:41 built by root@bit64.dvig.com on a x86_64 running Linux From openh323 version.h: #define MAJOR_VERSION 1 #define MINOR_VERSION 15 From pwlib version.h: #define MAJOR_VERSION 1 #define MINOR_VERSION 8 -- Tracy Reed http://copilotcom.com This message is cryptographically signed for your protection. Info: http://copilotconsulting.com/sig -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.digium.com/pipermail/asterisk-users/attachments/20041122/90c85495/attachment.pgp
Tracy R Reed a ?crit :>Has anyone here done this? I got it compiled just fine but when I make a >call I do not get any audio going either way. The * box is not behind any >sort of firewall or nat. My H323 client (gnomemeeting) is behind NAT but I >have it set up properly to work through NAT and it will talk correctly >with my other regular x86 box running H323. One odd thing I note is that >when looking at the UDP traffic with tcpdump I see the * box receiving my >UDP packets but never transmitting anything. SIP works just fine and is >talking to my TNT. I am trying to receive incoming H323 to terminate to >the call on the TNT. > >Same problem here. My * box is connected to GnuGK. CVS Head 11/02/04, kernel 2.4.26-SMP>From openh323 version.h: > >#define MAJOR_VERSION 1 >#define MINOR_VERSION 15 > >From pwlib version.h: > >#define MAJOR_VERSION 1 >#define MINOR_VERSION 8 > > >Same versions. Before, I was running pwlib 1.5 and openh323 1.12 and had no problem. -- Daniel
Ok, I have some more info. The code from openh323.org will not compile on
x86_64 but the latest from the OpenH323 project on sourceforge will
compile just fine on x86_64. Asterisk 1.0 will not compile with this new
openh323 code but it looks like the latest cvs-head does. In
channels/chan_h323 I had to make a few tweaks to get it to compile since
chan_h323 assumes x86. First, I had to change the makefile from:
CFLAGS += -march=$(shell uname -m)
To:
CFLAGS += -march=athlon64
to get rid of this error:
ast_h323.cpp:1: error: bad value (x86_64) for -march= switch
ast_h323.cpp:1: error: bad value (x86_64) for -mtune= switch
Then I had to make some symlinks:
ln -s /usr/local/src/openh323/lib/libh323_linux_x86_64_r.so
/usr/local/src/openh323/lib/libh323_linux_x86_r.so
ln -s /usr/local/src/pwlib/lib/libpt_linux_x86_64_r.so
/usr/local/src/pwlib/lib/libpt_linux_x86_r.so
Well, that's got me compiling cleanly at least. However asterisk still has
problems. When I try to make an H323 call to the box the rtp stream never
gets connected. tcpdump shows the clients packets hitting the asterisk box
but asterisk never transmits anything. Another odd thing is that stop now
can no longer be used to shut down asterisk after an attempt is made at
making an h323 call but it works just fine as long as you don't try making
an h323 call. I suspect a problem in chan_h323 locking things up. If I do
a show channels after having tried to make a call I get:
bit64*CLI> show channels
Channel (Context Extension Pri ) State Appl. Data
SIP/pstn1-e7c5 (default 1 ) Up Bridged Call
H323/ip$[myip]:30005/28852
1 active channel(s)
Nov 24 02:51:14 WARNING[10527]: channel.c:494 ast_channel_walk_locked:
Avoided deadlock for 'H323/ip$[myip]:30005/28852', 10 retries!
Anyone know of any major signalling or socket differences between x86 and
x86_64?
--
Tracy Reed http://copilotcom.com
This message is cryptographically signed for your protection.
Info: http://copilotconsulting.com/sig
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20041124/db74b3d8/attachment.pgp