Hi Brett, Avin
I have my explanation about this and have already posted in the forum. Please
check the previous posts.
I want to ask Avin for assistance in clarifying exactly what steps should be
done in order to fix this issue. I am ready to contribute and have already made
a patch for Progress-Indicator, but the step with the voice cut-through is more
difficult and is not done yet.
I found many users reported about this problem, so please Avin, give some help!
Thank you!
BR
mortex
>-------- Оригинално писмо --------
>От: "Brett" <[EMAIL PROTECTED]>
>Относно: Re: ooh323 q931 signalling problem
>До: <ooh323c-devel@lists.sourceforge.net>
>Изпратено на: Вторник, 2006, Юни 6 18:20:07 EEST
>----------------------------------
>
>Mortex , Avin
>
>I have found the same issue in that ooh323 sends an "Alerting" message
>prematurely regardless of whether the remote endpoint
>is ringing or not. I believe ooh323 should be sending Progress and Proceeding
>messages instead. This behaviour can be
>observed by using an h323 endpoint with verbose trace / debug capability like
>ohphone , simph323 or simpleopal.
>I didn't get any responses to my previous posts, so I have included the
>details below (including the Asterisk debug)
>
>Could anyone please explain why ooh323 generates an "onAlerting" message when
>the
>corresponding alerting message hasn't been received by Q.931 ? I am using
>asterisk-ooh323c-0.5 and when I place a call to a bogus phone number (ie.
>remote endpoint
>which is engaged or out of order) then ooh323 will still generate an
>"onAlerting" message
>immediatley after the call is initiated and subsequently the call will fail
>and no ringback
>is heard.
>
>I use an h.323 application which dials via an asterisk server to several
>remote isdn gateways. The application bases it's call success on
>receiving the h225 / q.931 progress indicators in the correct order (ie.
>setup -> call proceeding -> progress -> alerting -> connect) . It
>appears the ooh323 driver on asterisk server is sending an "alerting
>indication" immediately after the call is placed by the application,
>even though the remote end is not sending alert (ringing) and thus
>making the application think a call is proceeding when it has in fact
>failed.
>
>Asterisk debug
>
> Connected to Asterisk 1.2.7.1 currently running on asterisk (pid = 5396)
> Verbosity is at least 3
> asterisk*CLI> pri debug span 1
> Enabled debugging on span 1
> asterisk*CLI>
> asterisk*CLI> ooh323 debug
> OOH323 Debugging Enabled
> asterisk*CLI>
> --- onNewCallCreated ooh323c_3
> +++ onNewCallCreated ooh323c_3
> --- ooh323_onReceivedSetup ooh323c_3
> --- find_userI>
> +++ find_user
> Adding capabilities to call(incoming, ooh323c_3)
> gsoamelsAdding g711 ulaw capability to call(incoming, ooh323c_3)
> --- configure_local_rtp
> +++ configure_local_rtp
> +++ ooh323_onReceivedSetup - Determined context default, extension
> 055554103
> --- onAlerting ooh323c_3
> --- find_call
> +++ find_callI>
> -- Executing Dial("OOH323/323app-25e4", "Zap/g1/55554103") in new
> stack
> +++ onAlerting ooh323c_3
> -- Making new call for cr 32770
> -- Requested transfer capability: 0x00 - SPEECH
> > Protocol Discriminator: Q.931 (8) len=31
> > Call Ref: len= 2 (reference 2/0x2) (Originator)
> > Message type: SETUP (5)
> > [04 03 80 90 a3]
>
-----------------------------------------------------------------
http://www.sportni.bg/worldcup/ - Германия 2006 - Световното първенство по
футбол наближава!
_______________________________________________
ooh323c-devel mailing list
ooh323c-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ooh323c-devel
