On Tuesday 15 March 2005 13:01, hamed akhavan wrote: > Hi, > > Appears the problem with the large number of concurrent calls on the system > has been resolved! however the disconnect cause 4 is still there! > > I understand that this disconnect cause is generated from the terminting > ISDN equipment, however this error only appears when the call is crossing > this GK, if i send the call directly to the terminating GW we never see > disconnect cause 4! but as soon as the gnugk is involved i see disconnect > cause 4 passed back to to main GK that sent LRQ to the gnugk! I completely understand that this happens only if the call is passed via GnuGK. The issue is to understand WHY... And the answer can be given via a debug at the ISDN switch that issues the DC No 4. > > one other strange thing is that in the mysql cdr logs, we also dont see > disconnect cause 4! so what is the main GK that sent the LRQ is seeing the > causes as "4"? could this be a problem at the main GK such as > mis-interpreting the code which is highly unlikely! or a communication > problem between the two? > Maybe I will sound funny, but why don't you try a "direct H225 connection" between the two gatekeepers (also called in GnuGK - "Permanent Endpoint")? Just as a test. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
