[ previous ] [ next ] [ threads ]
 To :  Yate mailing list <yate@v...>
 From :  Paul Chitescu <paulc@v...>
 Subject :  Re: [yate] SIP to H323
 Date :  Sat, 31 Mar 2007 18:54:48 +0300 (EEST)
Hi!

Please look at the answers inline.

Paul

On Thu, 29 Mar 2007, tsp.international@c... wrote:
> Hello All,
>
> I have the yate and I'm trying to send traffic to a H323 quintum 
> gateway. The problem is that I'm not getting the answer request form the 
> H323 gateway on the for end. To make matter no better I have a cisco 
> gateway doing the SBC for me because I'm using YateAdmin and I could not 
> get the H323 YateAccount to come online so All calls were failing 
> because the account is "offline". I would like to stop using the 
> YateAdmin so where would I find the files I need to configure without 
> using yateadmin. I see yate in /usr/src/yateadmin, and also in 
> /usr/local/etc on the Ubuntu version I'm using. Can someone please help? 
> Please see below an explanation of my issue: Also do yate support 
> G729br8 or G729r8?

You can write a section in accfile.conf to connect to a remote gatekeeper:

[test-h323]
enabled=yes
protocol=h323
username=xxxxx
password=yyyyy
server=aa.bb.cc.dd
gkttl=60
; set another local port
port=1730

To route calls there you will need to route to something like h323/number 
with the parameter line=test-h323

> When doing h323 slowstart, the h225 messaging progresses as it 
> should...but once we receive a CONNECT from the Quintum...it never sends 
> us any h245 parameters for negotiation, so the cisco gateway waits for 
> h245 negotiation.  Because of this the gateway cannot send a 200 OK with 
> a media SDP to the SIP server.  How come the Quintam never sends h245 
> media negotiation? See "cisco2621xm_debug3.txt" for debugs of what I 
> mean.

Uh, didn't you forget to attach the log file?

> When doing Faststart, the negotiation starts as it should...and h225 is 
> done, while h245 starts...but then the Quintum sends a release complete 
> which kills the call right away.  Why is the Quintum disconnecting the 
> call?

Well, no idea, you have to look at the H.323 communication logs. Even then 
it may not be any sign of what is wrong. The Quintum logs hold the final 
answer.