[Asterisk-video] patches for proper h324m ZAP signaling (was:h324m_call - extensions.conf)

[Sergio Garcia]

Great work Klaus! Have you been able to test also the amr patch?

Best regards
Sergio


---------- Original Message ----------------------------------
From: Klaus Darilion <klaus.mailinglists at pernau.at>
Reply-To: Development discussion of video media support in Asterisk<asterisk-video at lists.digium.com>
Date:  Tue, 17 Jul 2007 12:20:15 +0200

>Hi!
>
>H324M uses User Information Layer 1 in Bearer Capability IE to signal 
>H324M (H223+H245). This information is discarded in Asterisk and also 
>outgoing calls do not set it correctly.
>
>Thus, I wrote 2 patches for asterisk/libpri to handle this correctly:
>
>1. libpri: http://bugs.digium.com/view.php?id=10189
>- updates the debug logs
>- allows setting of UIL1 also for EUROISDN
>
>2. asterisk/chan_zap: http://bugs.digium.com/view.php?id=10217
>- reading and setting of the user information layer 1 using the CHANNEL 
>function. (func_channel.c)
>- copy the user information layer 1 value from incoming to outgoing call 
>leg. This is needed when an incoming ZAP call is immediately sent out 
>again. (app_dial.c)
>- change chan_zap to use the defined ulser information layer 1 value 
>when making digital calls instead of setting it always to -1.
>
>
>examples:
>
>fetch current UIL1 value:
>exten => 107,n,Set(ul1=${CHANNEL(userinformationlayer1)})
>
>set transfer capability to unrestricted digital and UIL1 to H324M and 
>then dial out with a h324m_call():
>
>[xcon]
>exten => 665,1,h324m_call(666 at xcon)
>exten => 666,1,Set(CHANNEL(transfercapability)=VIDEO)
>exten => 666,n,NoOp(transfer=${CHANNEL(transfercapability)})
>exten => 666,n,Set(CHANNEL(userinformationlayer1)=38)
>exten => 666,n,NoOp(ul1=${CHANNEL(userinformationlayer1)})
>exten => 666,n,Dial,Zap/g2/06991116123445567
>
>
>regards
>Klaus
>
>
>
>
>
>Currently Asterisk does
>
>Klaus Darilion wrote:
>> Sergio Garcia Murillo wrote:
>>> Hi,
>>>
>>> there are some issues to solve prior making an outgoing videocall.
>>> The first is to chage the q931 call type, which needs a patch to the channel
>>> driver in order to be able to set it upa correctly from the dialplan.A dirty
>>> hack is fixing the type in q931.c so every outgoing call is a videocall.
>> 
>> Hi Sergio!
>> 
>> fYI: patch for libpri is on the tracker, patch for chan_zap and 
>> func_channel (to set user information layer 1 from extension.conf) will 
>> follow tomorrow.
>> 
>> regards
>> klaus
>> 
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> 
>> asterisk-video mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-video
>
>_______________________________________________
>--Bandwidth and Colocation Provided by http://www.api-digital.com--
>
>asterisk-video mailing list
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-video
>