[Asterisk-video] Trouble making outbound h324m video call

Klaus Darilion klaus.mailinglists at pernau.at
Mon Mar 31 09:01:29 CDT 2008


Hi!

I supsect that the ISDN switch does not like the signaling of H324M - 
either it wants to have different format or it blocks h324m completely.

Please send the "pri debug" of an incoming SETUP with h324m. Usually 
switches expect the same format as they send.

regards
klaus

Rene van Weert schrieb:
> Hi Klaus,
>  
> Well the phone doesn't start ringing. The call doesn't get setup at all 
> in Asterisk, I get the following messages:
>  
>      -- Executing [665 at from-sip:1] h324m_call("SIP/2000-08236c10", 
> "666 at test <mailto:666 at test>") in new stack
>     -- Executing [666 at test:1] Set("Local/666 at test-1826,2 
> <mailto:Local/666 at test-1826,2>", "CHANNEL(transfercapability)=VIDEO") in 
> new stack
>     -- Executing [666 at test:2] NoOp("Local/666 at test-1826,2 
> <mailto:Local/666 at test-1826,2>", "transfer=VIDEO") in new stack
>     -- Executing [666 at test:3] Set("Local/666 at test-1826,2 
> <mailto:Local/666 at test-1826,2>", "CHANNEL(userinformationlayer1)=38") in 
> new stack
>     -- Executing [666 at test:4] NoOp("Local/666 at test-1826,2 
> <mailto:Local/666 at test-1826,2>", "ul1=38") in new stack
>     -- Executing [666 at test:5] Dial("Local/666 at test-1826,2 
> <mailto:Local/666 at test-1826,2>", "ZAP/g0/0654566635") in new stack
> -- Making new call for cr 32784
>     -- digital call, setting user information layer 1 to 38 (0x26)
>     -- zap call: h324musellc=0, ast->userinformationlayer1=38
>     -- Requested transfer capability: 0x18 - VIDEO
>  > Protocol Discriminator: Q.931 (8)  len=37
>  > Call Ref: len= 2 (reference 16/0x10) (Originator)
>  > Message type: SETUP (5)
>  > [04 03 88 90 a6]
>  > Bearer Capability (len= 5) [ Ext: 1  Q.931 Std: 0  Info transfer 
> capability: Unrestricted digital information (8)
>  >                              Ext: 1  Trans mode/rate: 64kbps, 
> circuit-mode (16)
>  >                                User information layer 1: H.223 and 
> H.245 (38)
>  > [18 03 a9 83 82]
>  > Channel ID (len= 5) [ Ext: 1  IntID: Implicit  PRI  Spare: 0  
> Exclusive  Dchan: 0
>  >                        ChanSel: Reserved
>  >                       Ext: 1  Coding: 0  Number Specified  Channel 
> Type: 3
>  >                       Ext: 1  Channel: 2 ]
>  > [6c 06 00 80 32 30 30 30]
>  > Calling Number (len= 8) [ Ext: 0  TON: Unknown Number Type (0)  NPI: 
> Unknown Number Plan (0)
>  >                           Presentation: Presentation permitted, user 
> number not screened (0)  '2000' ]
>  > [70 0b 80 30 36 31 35 30 36 34 30 38 30]
>  > Called Number (len=13) [ Ext: 1  TON: Unknown Number Type (0)  NPI: 
> Unknown Number Plan (0)  '0654566635']
>  > [a1]skdev*CLI>
>  > Sending Complete (len= 1)
> q931.c:3245 q931_setup: call 32784 on channel 2 enters state 1 (Call 
> Initiated)
>     -- Called g0/0654566635
> < Protocol Discriminator: Q.931 (8)  len=10
> < Call Ref: len= 2 (reference 16/0x10) (Terminator)
> < Message type: RELEASE COMPLETE (90)
> < [08 03 80 e4 04]
> < Cause (len= 5) [ Ext: 1  Coding: CCITT (ITU) standard (0)  Spare: 0  
> Location: User (0)
> <                  Ext: 1  Cause: Invalid information element contents 
> (100), class = Protocol Error (e.g. unknown message) (6) ]
> <              Cause data 1: 04 (4)
> -- Processing IE 8 (cs0, Cause)
> q931.c:3875 q931_receive: call 32784 on channel 2 enters state 0 (Null)
>     -- Channel 0/2, span 1 got hangup, cause 100
> NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null
> NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null
>     -- Hungup 'Zap/2-1'
>   == Everyone is busy/congested at this time (1:0/0/1)
>   == Auto fallthrough, channel 'Local/666 at test-1826,2' 
> <mailto:'Local/666 at test-1826,2'> status is 'CHANUNAVAIL'
>   == Auto fallthrough, channel 'SIP/2000-08236c10' status is 'UNKNOWN'
>  
> With kind regards,
>  
> Rene
> 
> On Mon, Mar 31, 2008 at 1:17 PM, Klaus Darilion 
> <klaus.mailinglists at pernau.at <mailto:klaus.mailinglists at pernau.at>> wrote:
> 
> 
> 
>     Rene van Weert schrieb:
>      > Dear Klaus,
>      >
>      > I did what you said (remove AST_FORMAT_ULAW from app_h324m.c) but I
>      > still get exactly the same error...
>      > What else do you think could be wrong?
> 
> 
>     What is the exact problem? Does the mobile phone starts ringing? If yes,
>     does it indicate an incoming audio or an incoming video call?
> 
>     klaus
> 
>     _______________________________________________
>     --Bandwidth and Colocation Provided by http://www.api-digital.com--
>     <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



More information about the asterisk-video mailing list