- h323plus - lists.packetizer.com

OpenMCU protocol connection error
by leandro.alvares＠caixa.gov.br 14 Jul '10

14 Jul '10

Hi guys, I didn't do any modifications (like actualizations, etc... ) at my environment... At last days, I'm getting a lot of complain. When some endpoints connect to openMCU, I'm getting a protocol error. Maybe it can be caused by a wrong parameter at gnugk, but I'm not sure... I'm sending the log. Thanks a lot. cd0000cv011:/etc/init.d# cat temp.txt 18:23:27.622 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.623 LogChanRx:...Rx:8410400 PLUGIN Partial Frame received H.263-CIF Ignoring rendering. 18:23:27.623 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.624 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.624 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.627 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.642 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.644 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.644 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.644 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.644 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.652 LogChanRx:...Rx:8410400 PLUGIN Partial Frame received H.263-CIF Ignoring rendering. 18:23:27.653 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.653 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.653 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.654 LogChanRx:...Rx:87bcc48 PVC Set Renderer frame size to 352x288 18:23:27.654 LogChanRx:...Rx:87bcc48 PLUGIN Write data to video renderer 18:23:27.654 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.659 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.659 LogChanTx:...Tx:80b6f20 H323RTP Transmitter sent timestamp 303974010 18:23:27.674 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.674 LogChanTx:...Tx:8777198 H323RTP Transmitter sent timestamp 244205820 18:23:27.685 LogChanRx:...Rx:8410400 PLUGIN Partial Frame received H.263-CIF Ignoring rendering. 18:23:27.686 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.686 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.686 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.687 LogChanRx:...Rx:87bcc48 PVC Set Renderer frame size to 352x288 18:23:27.687 LogChanRx:...Rx:87bcc48 PLUGIN Write data to video renderer 18:23:27.687 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.691 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.708 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.708 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.716 LogChanRx:...Rx:87bcc48 H323RTP Receiver written timestamp 244180279 18:23:27.716 LogChanRx:...Rx:8410400 H323RTP Receiver written timestamp 303995341 18:23:27.717 LogChanRx:...Rx:87bcc48 PVC Set Renderer frame size to 352x288 18:23:27.717 LogChanRx:...Rx:87bcc48 PLUGIN Write data to video renderer 18:23:27.717 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.718 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.718 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.718 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.719 H323 Liste...er:80a6ad0 H323TCP Started connection: host=10.192.37.70:20034, if=10.192.37.70:1720, handle=26 18:23:27.719 H323 Liste...er:80a6ad0 PWLib Created thread 0x81e2678 H225 Answer:%0x 18:23:27.719 H323 Liste...er:80a6ad0 TCP Waiting on socket accept on ip$*:1720 18:23:27.720 H225 Answe...er:81e2678 PWLib Started thread 0x81e2678 H225 Answer:81e2678 18:23:27.720 H225 Answe...er:81e2678 H225 Started incoming call thread 18:23:27.720 H225 Answe...er:81e2678 H225 Awaiting first PDU 18:23:27.721 H225 Answe...er:81e2678 H225 Receiving PDU [ip$10.192.37.70:1720/ip$10.192.37.70:20034] : { q931pdu = { protocolDiscriminator = 8 callReference = 23911 from = originator messageType = Setup IE: Bearer-Capability = { 88 18 84 a5 .... } IE: Display = { 53 43 2e 53 52 2e 46 4c 4f 52 49 41 4e 4f 50 4f SC.SR.FLORIANOPO 4c 49 53 LIS } IE: Called-Party-Number = { 81 39 39 31 .991 } IE: User-User = { 60 b0 06 00 08 91 4a 00 04 02 03 80 7b 59 58 34 `.....J.....{YX4 40 12 00 53 00 43 00 2e 00 53 00 52 00 2e 00 46 @..S.C...S.R...F 00 4c 00 4f 00 52 00 49 00 41 00 4e 00 4f 00 50 .L.O.R.I.A.N.O.P 00 4f 00 4c 00 49 00 53 22 c0 59 00 ae 03 16 41 .O.L.I.S".Y....A 65 74 68 72 61 20 56 65 67 61 53 74 61 72 53 69 ethra VegaStarSi 6c 76 65 72 5f 45 0d 56 35 2e 31 2e 34 20 30 34 lver_E.V5.1.4 04 31 31 30 35 00 00 01 01 00 cc 40 02 87 73 2c dd 1105......@..s,. 96 76 13 10 6c 56 34 34 34 34 ef 00 7d 0f 98 07 .v..lV4444..}... 00 0a c0 25 46 06 b9 11 00 02 87 73 2c dd 96 76 ...%F......s,..v 13 10 6b 56 34 34 34 34 ef 01 00 01 00 13 10 00 ..kV4444........ 37 00 33 00 30 00 37 00 5f 00 65 00 6e 00 64 00 7.3.0.7._.e.n.d. 70 01 00 01 00 01 00 01 40 02 80 01 00 00 05 10 p.......@....... 63 61 6c 6c 5f 75 73 65 72 5f 74 6f 5f 75 73 65 call_user_to_use 72 r } } h225pdu = { h323_uu_pdu = { h323_message_body = setup { protocolIdentifier = 0.0.8.2250.0.4 sourceAddress = 2 entries { [0]=dialedDigits "48262501" [1]=h323_ID 19 characters { 0053 0043 002e 0053 0052 002e 0046 004c SC.SR.FL 004f 0052 0049 0041 004e 004f 0050 004f ORIANOPO 004c 0049 0053 LIS } } sourceInfo = { vendor = { vendor = { t35CountryCode = 89 t35Extension = 0 manufacturerCode = 44547 } productId = 23 octets { 41 65 74 68 72 61 20 56 65 67 61 53 74 61 72 53 Aethra VegaStarS 69 6c 76 65 72 5f 45 ilver_E } versionId = 14 octets { 56 35 2e 31 2e 34 20 30 34 31 31 30 35 00 V5.1.4 041105. } } terminal = { } mc = FALSE undefinedNode = FALSE } destinationAddress = 1 entries { [0]=dialedDigits "991" } activeMC = FALSE conferenceID = 16 octets { 02 87 73 2c dd 96 76 13 10 6c 56 34 34 34 34 ef ..s,..v..lV4444. } conferenceGoal = create <<null>> callType = pointToPoint <<null>> sourceCallSignalAddress = ipAddress { ip = 4 octets { 0a c0 25 46 ..%F } port = 1721 } callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } mediaWaitForConnect = FALSE canOverlapSend = FALSE endpointIdentifier = 9 characters { 0037 0033 0030 0037 005f 0065 006e 0064 7307_end 0070 p } multipleCalls = FALSE maintainConnection = FALSE presentationIndicator = presentationAllowed <<null>> screeningIndicator = userProvidedVerifiedAndFailed } h245Tunneling = FALSE } user_data = { protocol_discriminator = 5 user_information = 17 octets { 63 61 6c 6c 5f 75 73 65 72 5f 74 6f 5f 75 73 65 call_user_to_use 72 r } } } } Raw PDU: 08 02 5d 67 05 04 04 88 18 84 a5 28 13 53 43 2e ..]g.......(.SC. 53 52 2e 46 4c 4f 52 49 41 4e 4f 50 4f 4c 49 53 SR.FLORIANOPOLIS 70 04 81 39 39 31 7e 00 d2 05 60 b0 06 00 08 91 p..991~...`..... 4a 00 04 02 03 80 7b 59 58 34 40 12 00 53 00 43 J.....{YX4@..S.C 00 2e 00 53 00 52 00 2e 00 46 00 4c 00 4f 00 52 ...S.R...F.L.O.R 00 49 00 41 00 4e 00 4f 00 50 00 4f 00 4c 00 49 .I.A.N.O.P.O.L.I 00 53 22 c0 59 00 ae 03 16 41 65 74 68 72 61 20 .S".Y....Aethra 56 65 67 61 53 74 61 72 53 69 6c 76 65 72 5f 45 VegaStarSilver_E 0d 56 35 2e 31 2e 34 20 30 34 31 31 30 35 00 00 .V5.1.4 041105.. 01 01 00 cc 40 02 87 73 2c dd 96 76 13 10 6c 56 ....@..s,..v..lV 34 34 34 34 ef 00 7d 0f 98 07 00 0a c0 25 46 06 4444..}......%F. b9 11 00 02 87 73 2c dd 96 76 13 10 6b 56 34 34 .....s,..v..kV44 34 34 ef 01 00 01 00 13 10 00 37 00 33 00 30 00 44........7.3.0. 37 00 5f 00 65 00 6e 00 64 00 70 01 00 01 00 01 7._.e.n.d.p..... 00 01 40 02 80 01 00 00 05 10 63 61 6c 6c 5f 75 ..@.......call_u 73 65 72 5f 74 6f 5f 75 73 65 72 ser_to_user 18:23:27.723 H225 Answe...er:81e2678 H225 Incoming call, first PDU: callReference=23911 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: G.711-ALaw-64k <1> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: G.711-uLaw-64k <2> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: G.726-16k{sw} <3> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: G.726-24k{sw} <4> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: G.726-32k{sw} <5> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: G.726-40k{sw} <6> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: GSM-06.10{sw} <7> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: GSM-AMR{sw} <8> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: LPC-10{sw} <9> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: MS-GSM{sw} <10> 18:23:27.723 H225 Answe...er:81e2678 H323 Added capability: MS-IMA-ADPCM{sw} <11> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFNarrow-11k{sw} <12> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFNarrow-15k{sw} <13> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFNarrow-18.2k{sw} <14> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFNarrow-24.6k{sw} <15> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFNarrow-5.95k{sw} <16> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFNarrow-8k{sw} <17> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexIETFWide-20.6k{sw} <18> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexWNarrow-8k{sw} <19> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: SpeexWide-20.6k{sw} <20> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: iLBC-13k3{sw} <21> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: iLBC-15k2{sw} <22> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: H.263-CIF{sw} <23> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: H.263-QCIF{sw} <24> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: H.263{sw} <25> 18:23:27.724 H225 Answe...er:81e2678 H323 Added capability: H.263{sw} <1> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: H.239 Capabilities <26> H.263{sw} <1> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/hookflash <27> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/basicString <28> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/dtmf <29> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/RFC2833 <30> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/Navigation <31> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/Softkey <32> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/PointDevice <33> 18:23:27.725 H225 Answe...er:81e2678 H323 Added capability: UserInput/Modal <34> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 1 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: G.711-ALaw-64k <1> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 2 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: G.711-uLaw-64k <2> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 3 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: G.726-16k{sw} <3> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 4 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: G.726-24k{sw} <4> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 5 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: G.726-32k{sw} <5> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 6 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: G.726-40k{sw} <6> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 7 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: GSM-06.10{sw} <7> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 8 18:23:27.725 H225 Answe...er:81e2678 H323 Found capability: GSM-AMR{sw} <8> 18:23:27.725 H225 Answe...er:81e2678 H323 FindCapability: 9 18:23:27.726 H225 Answe...er:81e2678 H323 Found capability: LPC-10{sw} <9> 18:23:27.726 H225 Answe...er:81e2678 H323 FindCapability: 10 18:23:27.726 H225 Answe...er:81e2678 H323 Found capability: MS-GSM{sw} <10> 18:23:27.726 H225 Answe...er:81e2678 H323 FindCapability: 11 18:23:27.726 H225 Answe...er:81e2678 H323 Found capability: MS-IMA-ADPCM{sw} <11> 18:23:27.726 H225 Answe...er:81e2678 H323 FindCapability: 12 18:23:27.726 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFNarrow-11k{sw} <12> 18:23:27.726 H225 Answe...er:81e2678 H323 FindCapability: 13 18:23:27.726 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFNarrow-15k{sw} <13> 18:23:27.726 H225 Answe...er:81e2678 H323 FindCapability: 14 18:23:27.726 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.726 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFNarrow-18.2k{sw} <14> 18:23:27.727 H225 Answe...er:81e2678 H323 FindCapability: 15 18:23:27.727 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFNarrow-24.6k{sw} <15> 18:23:27.727 H225 Answe...er:81e2678 H323 FindCapability: 16 18:23:27.727 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFNarrow-5.95k{sw} <16> 18:23:27.727 H225 Answe...er:81e2678 H323 FindCapability: 17 18:23:27.727 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFNarrow-8k{sw} <17> 18:23:27.727 H225 Answe...er:81e2678 H323 FindCapability: 18 18:23:27.727 H225 Answe...er:81e2678 H323 Found capability: SpeexIETFWide-20.6k{sw} <18> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 19 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: SpeexWNarrow-8k{sw} <19> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 20 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: SpeexWide-20.6k{sw} <20> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 21 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: iLBC-13k3{sw} <21> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 22 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: iLBC-15k2{sw} <22> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 26 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: H.239 Capabilities <26> H.263{sw} <1> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 23 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: H.263-CIF{sw} <23> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 24 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: H.263-QCIF{sw} <24> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 25 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: H.263{sw} <25> 18:23:27.728 H225 Answe...er:81e2678 H323 FindCapability: 27 18:23:27.728 H225 Answe...er:81e2678 H323 Found capability: UserInput/hookflash <27> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 28 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/basicString <28> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 29 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/dtmf <29> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 30 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/RFC2833 <30> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 31 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/Navigation <31> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 32 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/Softkey <32> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 33 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/PointDevice <33> 18:23:27.729 H225 Answe...er:81e2678 H323 FindCapability: 34 18:23:27.729 H225 Answe...er:81e2678 H323 Found capability: UserInput/Modal <34> 18:23:27.729 H225 Answe...er:81e2678 H460 Endpoint Attached 18:23:27.729 H225 Answe...er:81e2678 RFC2833 Handler created 18:23:27.729 H225 Answe...er:81e2678 H323 Created new connection: ip$10.192.37.70:20034/23911 18:23:27.729 H225 Answe...er:81e2678 H225 Handling PDU: Setup callRef=23911 18:23:27.729 H225 Answe...er:81e2678 H245 Stopping MasterSlaveDetermination: state=Idle 18:23:27.729 H225 Answe...er:81e2678 H245 Stopping TerminalCapabilitySet: state=Idle 18:23:27.729 H225 Answe...er:81e2678 H225 Fast Start DISABLED! 18:23:27.729 H225 Answe...er:81e2678 H235EP Authentication Failed but allowed by policy 18:23:27.729 H225 Answe...er:81e2678 H225 Set protocol version to 4 and implying H.245 version 7 18:23:27.730 H225 Answe...er:81e2678 H225 Set remote application name: "Aethra VegaStarSilver_E V5.1.4 041105 89/44547" 18:23:27.731 H225 Answe...er:81e2678 H225 Sending call proceeding PDU 18:23:27.731 H225 Answe...er:81e2678 H460 Create FeatureSet CallProceed PDU 18:23:27.731 H225 Answe...er:81e2678 H460 FeatureSet for CallProceed PDU { replacementFeatureSet = FALSE } 18:23:27.731 H225 Answe...er:81e2678 H225 Sending PDU [ip$10.192.37.70:1720/ip$10.192.37.70:20034] : { q931pdu = { protocolDiscriminator = 8 callReference = 23911 from = destination messageType = CallProceeding IE: Display = { 4d 43 55 00 MCU. } IE: User-User = { 21 80 06 00 08 91 4a 00 04 24 c0 09 00 00 3d 17 !.....J..$....=. 50 6f 73 74 20 49 6e 63 72 65 6d 65 6e 74 20 4f Post Increment O 70 65 6e 4d 43 55 00 00 1d 32 2e 32 2e 33 20 28 penMCU...2.2.3 ( 48 33 32 33 70 6c 75 73 20 76 31 2e 32 30 61 6c H323plus v1.20al 70 68 61 32 29 00 00 20 d0 c0 11 00 02 87 73 2c pha2).. ......s, dd 96 76 13 10 6b 56 34 34 34 34 ef 01 00 01 00 ..v..kV4444..... 02 80 01 00 .... } } h225pdu = { h323_uu_pdu = { h323_message_body = callProceeding { protocolIdentifier = 0.0.8.2250.0.4 destinationInfo = { vendor = { vendor = { t35CountryCode = 9 t35Extension = 0 manufacturerCode = 61 } productId = 24 octets { 50 6f 73 74 20 49 6e 63 72 65 6d 65 6e 74 20 4f Post Increment O 70 65 6e 4d 43 55 00 00 penMCU.. } versionId = 30 octets { 32 2e 32 2e 33 20 28 48 33 32 33 70 6c 75 73 20 2.2.3 (H323plus 76 31 2e 32 30 61 6c 70 68 61 32 29 00 00 v1.20alpha2).. } } mcu = { } mc = TRUE undefinedNode = FALSE } callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } multipleCalls = FALSE maintainConnection = FALSE } h245Tunneling = FALSE } } } Raw PDU: 08 02 dd 67 02 28 04 4d 43 55 00 7e 00 65 05 21 ...g.(.MCU.~.e.! 80 06 00 08 91 4a 00 04 24 c0 09 00 00 3d 17 50 .....J..$....=.P 6f 73 74 20 49 6e 63 72 65 6d 65 6e 74 20 4f 70 ost Increment Op 65 6e 4d 43 55 00 00 1d 32 2e 32 2e 33 20 28 48 enMCU...2.2.3 (H 33 32 33 70 6c 75 73 20 76 31 2e 32 30 61 6c 70 323plus v1.20alp 68 61 32 29 00 00 20 d0 c0 11 00 02 87 73 2c dd ha2).. ......s,. 96 76 13 10 6b 56 34 34 34 34 ef 01 00 01 00 02 .v..kV4444...... 80 01 00 ... 18:23:27.733 H225 Answe...er:81e2678 H460 Create FeatureSet Alerting PDU 18:23:27.733 H225 Answe...er:81e2678 H460 FeatureSet for Alerting PDU { replacementFeatureSet = FALSE } 18:23:27.733 H225 Answe...er:81e2678 H225 Incoming call accepted 18:23:27.734 H225 Answe...er:81e2678 H460 Create FeatureSet Adm Reqest PDU 18:23:27.734 H225 Answe...er:81e2678 H460 FeatureSet for Adm Reqest PDU { replacementFeatureSet = FALSE } 18:23:27.734 H225 Answe...er:81e2678 Trans Making request: admissionRequest 18:23:27.734 H225 Answe...er:81e2678 H460 Create FeatureSet Adm Reqest PDU 18:23:27.734 H225 Answe...er:81e2678 H460 FeatureSet for Adm Reqest PDU { replacementFeatureSet = FALSE } 18:23:27.735 H225 Answe...er:81e2678 Trans Sending PDU [ip$10.192.37.70:32769/ip$10.192.37.70:1719] : admissionRequest { requestSeqNum = 31264 callType = pointToPoint <<null>> endpointIdentifier = 9 characters { 0037 0032 0038 0032 005f 0065 006e 0064 7282_end 0070 p } destinationInfo = 11 entries { [0]=h323_ID 3 characters { 004d 0043 0055 MCU } [1]=dialedDigits "990" [2]=dialedDigits "991" [3]=dialedDigits "992" [4]=dialedDigits "993" [5]=dialedDigits "994" [6]=dialedDigits "995" [7]=dialedDigits "996" [8]=dialedDigits "997" [9]=dialedDigits "998" [10]=dialedDigits "999" } destCallSignalAddress = ipAddress { ip = 4 octets { 0a c0 25 46 ..%F } port = 1720 } srcInfo = 1 entries { [0]=h323_ID 45 characters { 0053 0043 002e 0053 0052 002e 0046 004c SC.SR.FL 004f 0052 0049 0041 004e 004f 0050 004f ORIANOPO 004c 0049 0053 0020 0028 0034 0038 0032 LIS (482 0036 0032 0035 0030 0031 0029 0020 005b 62501) [ 0031 0030 002e 0031 0039 0032 002e 0033 10.192.3 0037 002e 0037 0030 005d 7.70] } } srcCallSignalAddress = ipAddress { ip = 4 octets { 0a c0 25 46 ..%F } port = 20034 } bandWidth = 100000 callReferenceValue = 23911 conferenceID = 16 octets { 02 87 73 2c dd 96 76 13 10 6c 56 34 34 34 34 ef ..s,..v..lV4444. } activeMC = FALSE answerCall = TRUE canMapAlias = TRUE callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } gatekeeperIdentifier = 7 characters { 0047 006e 0075 0047 004b 0030 0031 GnuGK01 } willSupplyUUIEs = TRUE canMapSrcAlias = FALSE } Raw PDU: size=ec pos=7fffffff.0 { 000 26 d0 7a 1f 02 00 00 37 00 32 00 38 00 32 00 5f & z 7 2 8 2 _ 00 65 00 6e 00 64 00 70 0b 40 02 00 4d 00 43 00 e n d p @ M C 55 01 00 cc 30 10 cc 40 10 cc 50 10 cc 60 10 cc U 0 @ P ` 70 10 cc 80 10 cc 90 10 cc a0 10 cc b0 10 cc c0 p 0a c0 25 46 06 b8 01 40 2c 00 53 00 43 00 2e 00 %F @, S C . 53 00 52 00 2e 00 46 00 4c 00 4f 00 52 00 49 00 S R . F L O R I 41 00 4e 00 4f 00 50 00 4f 00 4c 00 49 00 53 00 A N O P O L I S 20 00 28 00 34 00 38 00 32 00 36 00 32 00 35 00 ( 4 8 2 6 2 5 30 00 31 00 29 00 20 00 5b 00 31 00 30 00 2e 00 0 1 ) [ 1 0 . 31 00 39 00 32 00 2e 00 33 00 37 00 2e 00 37 00 1 9 2 . 3 7 . 7 30 00 5d 00 0a c0 25 46 4e 42 80 01 86 a0 5d 67 0 ] %FNB ]g 02 87 73 2c dd 96 76 13 10 6c 56 34 34 34 34 ef s, v lV4444 49 64 20 10 01 80 11 00 02 87 73 2c dd 96 76 13 Id s, v 10 6b 56 34 34 34 34 ef 0f 0c 00 47 00 6e 00 75 kV4444 G n u 00 47 00 4b 00 30 00 31 01 80 01 00 G K 0 1 } 18:23:27.736 H225 Answe...er:81e2678 Trans Waiting on response to seqnum=31264 for 3.0 seconds 18:23:27.739 Transactor...or:80bc580 H225RAS Receiving PDU [ip$10.192.37.70:32769/ip$10.192.37.70:1719] : admissionConfirm { requestSeqNum = 31264 bandWidth = 100000 callModel = gatekeeperRouted <<null>> destCallSignalAddress = ipAddress { ip = 4 octets { 0a c0 25 46 ..%F } port = 1721 } willRespondToIRR = FALSE uuiesRequested = { setup = FALSE callProceeding = FALSE connect = FALSE alerting = FALSE information = FALSE releaseComplete = FALSE facility = FALSE progress = FALSE empty = FALSE status = FALSE statusInquiry = FALSE setupAcknowledge = FALSE notify = FALSE } serviceControl = 1 entries { [0]={ sessionId = 0 contents = callCreditServiceControl { callStartingPoint = connect <<null>> } reason = refresh <<null>> } } } Raw PDU: size=27 pos=27.0 { 000 2a 00 7a 1f 80 01 86 a0 40 0a c0 25 46 06 b9 22 * z @ %F " 00 c0 80 01 00 0b 80 01 f8 01 00 01 00 01 00 01 00 05 01 40 00 60 a4 @ ` } 18:23:27.739 Transactor...or:80bc580 Trans Using credentials from request: CAT<no-pwd>,MD5<no-pwd> 18:23:27.740 Transactor...or:80bc580 SvcCtrl OnChange Call Credit service control debit 0 18:23:27.740 Transactor...or:80bc580 Trans Reading PDU 18:23:27.740 H225 Answe...er:81e2678 H323 Bandwidth used: 0 18:23:27.740 H225 Answe...er:81e2678 H460 Create FeatureSet Connect PDU 18:23:27.741 H225 Answe...er:81e2678 H460 FeatureSet for Connect PDU { replacementFeatureSet = FALSE } 18:23:27.741 H225 Answe...er:81e2678 MCU Joining room specified by destination address 991 18:23:27.741 H225 Answe...er:81e2678 H323 Answering call: AnswerCallNow 18:23:27.741 H225 Answe...er:81e2678 H225 TCP Listen for H245 on 10.192.37.70:41962 18:23:27.741 H225 Answe...er:81e2678 PWLib Created thread 0xb6134d00 H245:%0x 18:23:27.742 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.741 H225 Answe...er:81e2678 H225 Sending PDU [ip$10.192.37.70:1720/ip$10.192.37.70:20034] : { q931pdu = { protocolDiscriminator = 8 callReference = 23911 from = destination messageType = Connect IE: Bearer-Capability = { 80 90 a5 ... } IE: Display = { 4d 43 55 00 MCU. } IE: User-User = { 22 c0 06 00 08 91 4a 00 04 00 0a c0 25 46 a3 ea ".....J.....%F.. 24 c0 09 00 00 3d 17 50 6f 73 74 20 49 6e 63 72 $....=.Post Incr 65 6d 65 6e 74 20 4f 70 65 6e 4d 43 55 00 00 1d ement OpenMCU... 32 2e 32 2e 33 20 28 48 33 32 33 70 6c 75 73 20 2.2.3 (H323plus 76 31 2e 32 30 61 6c 70 68 61 32 29 00 00 20 02 v1.20alpha2).. . 87 73 2c dd 96 76 13 10 6c 56 34 34 34 34 ef 17 .s,..v..lV4444.. 0c 20 11 00 02 87 73 2c dd 96 76 13 10 6b 56 34 . ....s,..v..kV4 34 34 34 ef 01 00 01 00 01 00 02 80 01 00 444........... } } h225pdu = { h323_uu_pdu = { h323_message_body = connect { protocolIdentifier = 0.0.8.2250.0.4 h245Address = ipAddress { ip = 4 octets { 0a c0 25 46 ..%F } port = 41962 } destinationInfo = { vendor = { vendor = { t35CountryCode = 9 t35Extension = 0 manufacturerCode = 61 } productId = 24 octets { 50 6f 73 74 20 49 6e 63 72 65 6d 65 6e 74 20 4f Post Increment O 70 65 6e 4d 43 55 00 00 penMCU.. } versionId = 30 octets { 32 2e 32 2e 33 20 28 48 33 32 33 70 6c 75 73 20 2.2.3 (H323plus 76 31 2e 32 30 61 6c 70 68 61 32 29 00 00 v1.20alpha2).. } } mcu = { } mc = TRUE undefinedNode = FALSE } conferenceID = 16 octets { 02 87 73 2c dd 96 76 13 10 6c 56 34 34 34 34 ef ..s,..v..lV4444. } callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } multipleCalls = FALSE maintainConnection = FALSE fastConnectRefused = <<null>> } h245Tunneling = FALSE } } } Raw PDU: 08 02 dd 67 07 04 03 80 90 a5 28 04 4d 43 55 00 ...g......(.MCU. 7e 00 7f 05 22 c0 06 00 08 91 4a 00 04 00 0a c0 ~...".....J..... 25 46 a3 ea 24 c0 09 00 00 3d 17 50 6f 73 74 20 %F..$....=.Post 49 6e 63 72 65 6d 65 6e 74 20 4f 70 65 6e 4d 43 Increment OpenMC 55 00 00 1d 32 2e 32 2e 33 20 28 48 33 32 33 70 U...2.2.3 (H323p 6c 75 73 20 76 31 2e 32 30 61 6c 70 68 61 32 29 lus v1.20alpha2) 00 00 20 02 87 73 2c dd 96 76 13 10 6c 56 34 34 .. ..s,..v..lV44 34 34 ef 17 0c 20 11 00 02 87 73 2c dd 96 76 13 44... ....s,..v. 10 6b 56 34 34 34 34 ef 01 00 01 00 01 00 02 80 .kV4444......... 01 00 .. 18:23:27.743 LogChanTx:...Tx:8220128 H323RTP Transmitter sent timestamp 21708000 18:23:27.744 H225 Answe...er:81e2678 H323 InternalEstablishedConnectionCheck: connectionState=HasExecutedSignalConnect fastStartState=FastStartDisabled 18:23:27.744 H225 Answe...er:81e2678 H323 InternalEstablishedConnectionCheck: connectionState=HasExecutedSignalConnect fastStartState=FastStartDisabled 18:23:27.744 H225 Answe...er:81e2678 H225 Reading PDUs: callRef=23911 18:23:27.744 H245:b6134...5:b6134d00 PWLib Started thread 0xb6134d00 H245:b6134d00 18:23:27.744 H245:b6134...5:b6134d00 H245 Started thread 18:23:27.744 H245:b6134...5:b6134d00 H245 TCP Accept wait 18:23:27.745 RTP Jitter...er:83ff7c0 RTP SentSenderReport: ssrc=525559091 ntp=3488100691.1586280892 rtp=21707760 psent=90449 osent=21707760 18:23:27.745 RTP Jitter...er:83ff7c0 RTP SentReceiverReport: ssrc=1259027969 fraction=0 lost=36 last_seq=27577 jitter=18 lsr=0 dlsr=0 18:23:27.745 RTP Jitter...er:83ff7c0 RTP Sending SDES: root@cd0000cv011 18:23:27.748 LogChanRx:...Rx:8410400 PLUGIN Partial Frame received H.263-CIF Ignoring rendering. 18:23:27.749 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.750 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.750 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.751 LogChanRx:...Rx:87bcc48 PVC Set Renderer frame size to 352x288 18:23:27.751 LogChanRx:...Rx:87bcc48 PLUGIN Write data to video renderer 18:23:27.751 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.759 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.776 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.776 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.776 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.780 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.780 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.780 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.781 LogChanRx:...Rx:87bcc48 PVC Set Renderer frame size to 352x288 18:23:27.781 LogChanRx:...Rx:87bcc48 PLUGIN Write data to video renderer 18:23:27.781 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.791 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.808 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.812 LogChanRx:...Rx:8410400 PLUGIN Partial Frame received H.263-CIF Ignoring rendering. 18:23:27.814 LogChanRx:...Rx:8410400 PVC Set Renderer frame size to 352x288 18:23:27.814 LogChanRx:...Rx:8410400 PLUGIN Write data to video renderer 18:23:27.814 LogChanRx:...Rx:8410400 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.820 LogChanRx:...Rx:87bcc48 PVC Set Renderer frame size to 352x288 18:23:27.821 LogChanRx:...Rx:87bcc48 PLUGIN Write data to video renderer 18:23:27.821 LogChanRx:...Rx:87bcc48 PVC ::Write, frame size is 352x288 VideoGrabber is unavailabile 18:23:27.825 LogChanTx:...Tx:80b6f20 PLUGIN Sent I-Frame 18:23:27.829 H225 Answe...er:81e2678 H225 Receiving PDU [ip$10.192.37.70:1720/ip$10.192.37.70:20034] : { q931pdu = { protocolDiscriminator = 8 callReference = 23911 from = originator messageType = ReleaseComplete IE: Cause - Protocol error, unspecified = { 80 ef .. } IE: User-User = { 25 80 06 00 08 91 4a 00 02 01 11 00 02 87 73 2c %.....J.......s, dd 96 76 13 10 6b 56 34 34 34 34 ef 02 80 01 00 ..v..kV4444..... } } h225pdu = { h323_uu_pdu = { h323_message_body = releaseComplete { protocolIdentifier = 0.0.8.2250.0.2 callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } } h245Tunneling = FALSE } } } Raw PDU: 08 02 5d 67 5a 08 02 80 ef 7e 00 21 05 25 80 06 ..]gZ....~.!.%.. 00 08 91 4a 00 02 01 11 00 02 87 73 2c dd 96 76 ...J.......s,..v 13 10 6b 56 34 34 34 34 ef 02 80 01 00 ..kV4444..... 18:23:27.829 H225 Answe...er:81e2678 H225 Handling PDU: ReleaseComplete callRef=23911 18:23:27.830 H225 Answe...er:81e2678 H225 Set protocol version to 2 and implying H.245 version 3 18:23:27.830 H225 Answe...er:81e2678 H225 Call End Reason Protocol error, unspecified 18:23:27.830 H225 Answe...er:81e2678 H323 Clearing connection ip$10.192.37.70:20034/23911 reason=EndedByQ931Cause 18:23:27.830 H225 Answe...er:81e2678 H323 Call end reason for ip$10.192.37.70:20034/23911 set to EndedByQ931Cause 18:23:27.830 H225 Answe...er:81e2678 H225 Sending release complete PDU: callRef=23911 18:23:27.830 H225 Answe...er:81e2678 H460 Create FeatureSet ReleaseComplete PDU 18:23:27.830 H225 Answe...er:81e2678 H460 FeatureSet for ReleaseComplete PDU { replacementFeatureSet = FALSE } 18:23:27.830 H225 Answe...er:81e2678 H225 Sending PDU [ip$10.192.37.70:1720/ip$10.192.37.70:20034] : { q931pdu = { protocolDiscriminator = 8 callReference = 23911 from = destination messageType = ReleaseComplete IE: Cause - Protocol error, unspecified = { 80 ef .. } IE: User-User = { 25 80 06 00 08 91 4a 00 02 01 11 00 02 87 73 2c %.....J.......s, dd 96 76 13 10 6b 56 34 34 34 34 ef 02 80 01 00 ..v..kV4444..... } } h225pdu = { h323_uu_pdu = { h323_message_body = releaseComplete { protocolIdentifier = 0.0.8.2250.0.2 callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } } h245Tunneling = FALSE } } } Raw PDU: 08 02 dd 67 5a 08 02 80 ef 7e 00 21 05 25 80 06 ...gZ....~.!.%.. 00 08 91 4a 00 02 01 11 00 02 87 73 2c dd 96 76 ...J.......s,..v 13 10 6b 56 34 34 34 34 ef 02 80 01 00 ..kV4444..... 18:23:27.832 H225 Answe...er:81e2678 H323 Clearing connection ip$10.192.37.70:20034/23911 reason=EndedByTransportFail 18:23:27.833 H323 Cleaner H323 Cleaning up connections 18:23:27.834 H323 Cleaner H323 Connection ip$10.192.37.70:20034/23911 closing: connectionState=HasExecutedSignalConnect 18:23:27.834 H323 Cleaner H245 Stopping MasterSlaveDetermination: state=Idle 18:23:27.834 H323 Cleaner H245 Stopping TerminalCapabilitySet: state=Idle 18:23:27.834 H225 Answe...er:81e2678 H225 Signal channel closed. 18:23:27.834 H323 Cleaner PWLib Closing channel, fd=69 18:23:27.834 H323 Cleaner PWLib Unblocking I/O fd=70 thread=H245:b6134d00 18:23:27.834 ThreadID=0xb555db70 PWLib Ended thread 0x81e2678 H225 Answer:81e2678 18:23:27.834 H245:b6134...5:b6134d00 PWLib Unblocked I/O fd=70 18:23:27.836 H245:b6134...5:b6134d00 H225 Accept for H245 failed: Interrupted system call 18:23:27.836 ThreadID=0xb54ddb70 PWLib Ended thread 0xb6134d00 H245:b6134d00 18:23:27.842 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.842 LogChanTx:...Tx:8777198 PLUGIN Sent I-Frame 18:23:27.845 H323 Cleaner H323 H323Transport::Close 18:23:27.845 H323 Cleaner H323 H323Transport::CleanUpOnTermination for H245:b6134d00 18:23:27.845 H323 Cleaner PWLib WaitForTermination(10.000) 18:23:27.845 H323 Cleaner PWLib Unblocking I/O fd=70 thread=H245:b6134d00 18:23:27.845 H323 Cleaner PWLib Destroyed thread 0xb6134d00 H245:b6134d00(id = 0) 18:23:27.846 H323 Cleaner H323 H323Transport::Close 18:23:27.846 H323 Cleaner PWLib Closing channel, fd=26 18:23:27.846 H323 Cleaner H323 H323Transport::CleanUpOnTermination for H225 Answer:81e2678 18:23:27.846 H323 Cleaner PWLib WaitForTermination(10.000) 18:23:27.846 H323 Cleaner PWLib Unblocking I/O fd=46 thread=H225 Answer:81e2678 18:23:27.848 H323 Cleaner PWLib Destroyed thread 0x81e2678 H225 Answer:81e2678(id = 0) 18:23:27.848 LogChanRx:...Rx:80cb100 H323RTP Receiver written timestamp 30197440 18:23:27.848 H323 Cleaner H460 Create FeatureSet Dis Request PDU 18:23:27.848 H323 Cleaner H460 FeatureSet for Dis Request PDU { replacementFeatureSet = FALSE } 18:23:27.848 H323 Cleaner Trans Making request: disengageRequest 18:23:27.849 H323 Cleaner H460 Create FeatureSet Dis Request PDU 18:23:27.849 H323 Cleaner H460 FeatureSet for Dis Request PDU { replacementFeatureSet = FALSE } 18:23:27.850 H323 Cleaner Trans Sending PDU [ip$10.192.37.70:32769/ip$10.192.37.70:1719] : disengageRequest { requestSeqNum = 31265 endpointIdentifier = 9 characters { 0037 0032 0038 0032 005f 0065 006e 0064 7282_end 0070 p } conferenceID = 16 octets { 02 87 73 2c dd 96 76 13 10 6c 56 34 34 34 34 ef ..s,..v..lV4444. } callReferenceValue = 23911 disengageReason = normalDrop <<null>> callIdentifier = { guid = 16 octets { 02 87 73 2c dd 96 76 13 10 6b 56 34 34 34 34 ef ..s,..v..kV4444. } } gatekeeperIdentifier = 7 characters { 0047 006e 0075 0047 004b 0030 0031 GnuGK01 } answeredCall = TRUE usageInformation = { nonStandardUsageFields = 0 entries { } connectTime = 1279111891 endTime = 1279111891 } terminationCause = releaseCompleteCauseIE 2 octets { 80 80 .. } } Raw PDU: size=60 pos=7fffffff.0 { 000 3e 7a 20 10 00 37 00 32 00 38 00 32 00 5f 00 65 >z 7 2 8 2 _ e 00 6e 00 64 00 70 02 87 73 2c dd 96 76 13 10 6c n d p s, v l 56 34 34 34 34 ef 5d 67 22 b1 18 11 00 02 87 73 V4444 ]g" s 2c dd 96 76 13 10 6b 56 34 34 34 34 ef 0f 0c 00 , v kV4444 47 00 6e 00 75 00 47 00 4b 00 30 00 31 01 80 0c G n u G K 0 1 30 00 c0 4c 3d b2 d2 c0 4c 3d b2 d2 03 40 80 80 0 L= L= @ } 18:23:27.850 H323 Cleaner Trans Waiting on response to seqnum=31265 for 3.0 seconds 18:23:27.857 Transactor...or:80bc580 H225RAS Receiving PDU [ip$10.192.37.70:32769/ip$10.192.37.70:1719] : disengageConfirm { requestSeqNum = 31265 } Raw PDU: size=3 pos=3.0 { 000 40 7a 20 @z } 18:23:27.857 Transactor...or:80bc580 Trans Using credentials from request: CAT<no-pwd>,MD5<no-pwd> 18:23:27.857 Transactor...or:80bc580 Trans Reading PDU 18:23:27.858 H323 Cleaner H323 Connection ip$10.192.37.70:20034/23911 terminated. 18:23:27.858 H323 Cleaner H323 Connection ip$10.192.37.70:20034/23911 deleted. 18:23:27.860 H323 Cleaner H323 Cleaning up connections cd0000cv011:/etc/init.d#

2 1

H323Plus and thirdparty video integration
by Sherwin Sim 12 Jul '10

12 Jul '10

Hey guys Currently I'm using h323plus for h323 signaling for my audi application. All is well and now I want to add video support. I already have my own implementations of h263 and h264 and I was wondering how I should go about integrating them. What I think I have to do is 1) Write my own VideoCapability class for each 263 and 264 2) I have my own impl of H323Connection code, and I probably want to seup the CreateRealtimeLogicalChannel to return the video ip and ports in a H323Channel Does this sound right? Also any examples of this would be great Sherwin Sim mailto:sherwin.sim@magorcorp.com North America toll free: 1 877 888-5468 T: +1 613 686-1731 ext. 5504 C: +1 613 851 3876 Magor Communications 350 Terry Fox Drive, Suite 300 Ottawa, Ontario Canada K2K 2W5 http://www.magorcorp.com

2 3

open source project
by andrew wang 08 Jun '10

08 Jun '10

Hi all, I want to participate in the development of some open source project. I want to some help and advice. Thanks! Best Regards Andrew

2 1

Support of Text encoding of the protocol for H248 protocol in H323 Plus
by Mayank Jain 04 Jun '10

04 Jun '10

Hi, Does H323 plus have support for Text encoding of H248.1 specification Annex B in http://www.itu.int/rec/T-REC-H.248.1-200509-I/en. Regards, Mayank Jain

1 0

GNU Gatekeeper 2.3.2 released
by Jan Willamowius 26 May '10

26 May '10

Hi, a new stable version of the GNU Gatekeeper is now available. Source code and executables can be downloaded from http://www.gnugk.org/h323download.html Executables are available for - Linux (32 bit and 64 bit - now statically linked) - Windows (XP, Vista, Windows7, ...) - MacOSX (PPC and Intel) - Solaris 10 - FreeBSD - OpenBSD Whats new in GnuGk 2.3.2 ? New features: - rewritten srv policy, add handling of LRQs and Setups (needed for Tandberg compatibility) - support for multiple DefaultDomains - new accounting events: AcctAlert, AcctRegister, AcctUnregister - added H.460.24 Annex B support - new switch [RoutedMode]NATStdMin for registering endpoints behind NAT to support NAT standard. - statusport commands UnregisterIP and DisconnectIP now find endpoints on non-standard ports - new status port command BindAndRouteToGateway - new setting [Neighbor::...] SendAliases= to specify aliases to send to the neighbor - new setting [EP::...] AddNumbers= to add numeric aliases to an endpoint - new variable for sql routing: %{client-auth-id} - new switch [RoutedMode]RemoveFaxUDPOptionsFromRM=1 to remove t38FaxUdpOptions from t38FaxProfile eg. for Avaya Communication Manager (thanks Denis Kochmashev) - support SRVs lookup when registering as endpoint Changed default: - change default for [CTI::MakeCall]UseH450= to 0 (supported by more endpoints) Bug fixes: - fix memory leaks - fix race condition when unregistering child - always check if DecodeSubType() to avoid crash - consider H245Routed setting for implied [ModeSelection] rules for internal networks (based on patch by Denis Kochmashev) - make sure explicit [ModeSelection] rules override implied rules for internal networks - don't start GnuGk, if we can't open a signaling port in routed mode - make sure MySQL config from /etc/my.cnf gets read - remove supportedFeature H.460.19 from Setup when called party doesn't support it Please use the latest H323Plus and PTLib 2.8.1 to compile. Please see http://www.gnugk.org/compiling-gnugk.html Regards, Jan -- Jan Willamowius, jan(a)willamowius.de, http://www.gnugk.org/

1 0

H.263 VIDEO FREEZE when connect 3 endpoints
by Pablo Sotomayor 15 May '10

15 May '10

I just notice another problem with H263 video. When using openmcu with polycom pvx clients, the video is ok when 2 endpoints are connected, when i connect a third pvx software, the video freezes but the audio keep ok. Openmcu and endpoint seems like send receiving data/audio/video. When i connect a fourth pvx endpoint, it shows the frozen video and audio is ok. stats of send/receive data shows traffic too. When i disconnect the second and third endpoint, the video unfreeze and i got video on 4th endpoint. Any help with this H263 issues will be appreciated. Pablo

2 1

H.263 VC MODES
by Pablo Sotomayor 13 May '10

13 May '10

Using openmcu with 3 polycom pvx software endpoints, i have good video in all stations, but when i select "force split video" on openmcu settings, i have many pink artifacts, lines, blur in the video squares on the screen.Im currently using h323plus 1.2.2 / ptlib 2.8.1. How can i fix the split video mode?

1 0

H.263 + Polycom VSX 7000 + VSX 5000 + PVX
by Pablo Sotomayor 12 May '10

12 May '10

I've been testing the 1.2.2 version of h323plus since last friday and got some H.263 problems. On the testing lab we have a quad-core xeon dell poweredge server running ubuntu 10.04. I installed from ubuntu repositories some system dependencies like ffmpeg, ffmpeg-devel (0.52), libx264, libx264-devel (85), libxvidcore4, libxvidcore-dev, libtheora, etc. From libopalvoip sourceforge files i got ptlib 2.66. From h323plus sourceforge cvs repo, got h323plus and applications. I compiled ptlib, set the PTLIBDIR env variable. Then i compiled h323plus and plugins and set the respective env variables too. Then i compiled openmcu. I run openmcu with loglevel 4 or 5, and i can see all the audio/video codec plugins loading. Focusing on the H263 codec testing, i remove h261 and h264 plugins. Running openmcu only with h263 plugin, i can connect polycom vpx an pacphone endpoints at a openmcu conference room with audio and video support. Audio G711ALaw and H263 CIF video. When i connect the polycom VSX 7000, the openmcu seems like sending/receiving network traffic, but the VSX 7000 show 0K/s on video receve rate on call statistics screen. At the other side, on Polycom PVX software, i can see the video incomming from vsx 7000. Im doing something wrong? There is some polycom configuration that i forgot? Im testing with some Polycom VSX 7000A, VSX 7000A(128) and Polycom VSX 5000 with 8.03, 8.53 and 8.71 firmware versions. Is that a plugin/codec or unexpected header issue? Pablo

1 0

H.264 hardware acceleration
by Pablo Sotomayor 10 May '10

10 May '10

It is possible for the openmcu to take advantage of some hardware h264 acceleration devices like these tiny usb dongles (http://www.fastvdo.com/SmartCapture/) or bigger devices like playstation3 runnung linux or the apple iphone/ipad devices? Pablo

2 1

Updated H.264 Plugin
by Simon Horne 09 May '10

09 May '10

An updated H.264 plugin has been added to the CVS. Quite a lot of fixes have been made especially in the HD area. 720p support has been enabled. Simon

2 2

oh323_tut make fails
by Alex Katebi 23 Apr '10

23 Apr '10

Hello everyone, When I tried to make the oh323tut I get the below error. THANKS! Alex akatebi@client:~/share/H323Plus/oh323tut-1.1-1$ make "CFLAGS=-DP_USE_INTEGER_BOOL" g++ -DPTRACING=1 -D_REENTRANT -fno-exceptions -Wall -DNDEBUG -I/home/akatebi/share/H323Plus/ptlib-2.4.5//include -DPTRACING -I/home/akatebi/share/H323Plus/h323plus/include -Os -DP_USE_INTEGER_BOOL -felide-constructors -Wreorder -c ep.cxx -o obj_linux_x86/ep.o g++ -DPTRACING=1 -D_REENTRANT -fno-exceptions -Wall -DNDEBUG -I/home/akatebi/share/H323Plus/ptlib-2.4.5//include -DPTRACING -I/home/akatebi/share/H323Plus/h323plus/include -Os -DP_USE_INTEGER_BOOL -felide-constructors -Wreorder -c oh323tut.cxx -o obj_linux_x86/oh323tut.o g++ -DPTRACING=1 -D_REENTRANT -fno-exceptions -Wall -DNDEBUG -I/home/akatebi/share/H323Plus/ptlib-2.4.5//include -DPTRACING -I/home/akatebi/share/H323Plus/h323plus/include -Os -DP_USE_INTEGER_BOOL -felide-constructors -Wreorder -c nullchan.cxx -o obj_linux_x86/nullchan.o g++ -DPTRACING=1 -D_REENTRANT -fno-exceptions -Wall -DNDEBUG -I/home/akatebi/share/H323Plus/ptlib-2.4.5//include -DPTRACING -I/home/akatebi/share/H323Plus/h323plus/include -Os -DP_USE_INTEGER_BOOL -felide-constructors -Wreorder -c wavchan.cxx -o obj_linux_x86/wavchan.o make -C /home/akatebi/share/H323Plus/ptlib-2.4.5//src/ptlib/unix opt make[1]: Entering directory `/home/akatebi/share/H323Plus/ptlib-2.4.5/src/ptlib/unix' make[1]: *** No rule to make target `opt'. Stop. make[1]: Leaving directory `/home/akatebi/share/H323Plus/ptlib-2.4.5/src/ptlib/unix' make: *** [/home/akatebi/share/H323Plus/ptlib-2.4.5//lib_linux_x86/libpt.so] Error 2

2 1

H.235 Media Encryption Help
by Jad el-Hage 22 Apr '10

22 Apr '10

I am trying to setup secure calls with H.323 endpoints. I am currently testing with polcom PVX. I can negotiate a shared secret using diffie-hellman and the first 8 bytes of the shared secret match the PVX's check code. But how to derive the media encryption keys from the shared secret ? >From H.235.6 I understand that the shared secret must be used to decrypt encryptedSessionKey, but the decryption is failing? Thanks, Jad

1 0

CreateRealTimeLogicalChannel not getting called
by Ashwin Kallaje 01 Apr '10

01 Apr '10

Hi, I am developing a small VideoConferencing application using H.323 version 1.22 from cvs. The Ptlib version is 2.8 My problem is, The CreateRealTimeLogicalChannel is not getting called. The OnStart, OnCreateLogicalChannels and CreateRealTimeLogicalChannel are all getting called, but not the CreateRealTimeLogicalChannel. I am not sure what I need to enable, so that MyH323Connection::CreateRealTimeLogicalChannel, gets called. Thank you Ashwin Kallaje

1 0

openmcu hangs when second client accepts invitation
by Sander 29 Mar '10

29 Mar '10

Dear all, I'm trying to do a three-way videoconferencing with openmcu. After inviting two ekiga clients to the same conference room (from within the webinterface), openmcu hangs. Hangs means: http://10.0.0.1:1420/Status doesn't refresh anymore (reload times out eventually) and openmcu has to be killed with -9. When inviting the first ekiga client, the client sees the openmcu logo as 'remote video', and that client gets listed on the status page. When inviting the second ekiga client to the same room, that client sees it's own video, and 'remote video' is grayed out. If the second client is invited to a different room from the first instead, both clients see the openmcu logo (and openmcu doens't hang and the status page gets refreshed with both clients listed in their rooms). This all happened back in early february too. Now I found the time to try again. I've read al mails in the archive at http://lists.packetizer.com/pipermail/h323plus/ from november 2009 till now, but didn't find a similar case. The system on which all software is compiled and which is running openmcu, is an up to date Debian Sid (unstable) amd64, and selfcompiled kernel 2.6.32-rc6. The clients are a Debian Sid on Intel Core2 Duo and a Debian Sid on ARM (SheevaPlug). How can I debug what happens to openmcu? Or is there an obvious mistake in the steps below? With kind regards, Sander # ldd `which openmcu` linux-vdso.so.1 => (0x00007fff1f1ff000) libh323_linux_x86_64_.so.1.22.0 => /usr/local/h323plus/lib/libh323_linux_x86_64_.so.1.22.0 (0x00007eff1581c000) libresolv.so.2 => /lib/libresolv.so.2 (0x00007eff15606000) libpt.so.2.9-beta0 => /usr/local/ptlib/lib/libpt.so.2.9-beta0 (0x00007eff150c8000) libpthread.so.0 => /lib/libpthread.so.0 (0x00007eff14eac000) librt.so.1 => /lib/librt.so.1 (0x00007eff14ca4000) libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007eff14a7b000) libdl.so.2 => /lib/libdl.so.2 (0x00007eff14877000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007eff14563000) libm.so.6 => /lib/libm.so.6 (0x00007eff142e0000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007eff140ca000) libc.so.6 => /lib/libc.so.6 (0x00007eff13d76000) /lib64/ld-linux-x86-64.so.2 (0x00007eff16278000) http://10.0.0.1:1420/Status (one client): Room Name Room Members Name Duration Codec RTP Packets/Bytes tx RTP Packets/Bytes rx TX Video frame rate/RX Video frame rate conference Sander 2:07.003 G.711-ALaw-64k/G.711-ALaw-64k 6350/1016000 6391/1022560 10.0007/9.68926 H.261-CIF/H.261-CIF The steps: svn checkout svn://svn.ffmpeg.org/ffmpeg/trunk ffmpeg cvs -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus login cvs -z3 -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus co h323plus cvs -z3 -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus co applications svn co http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/trunk ptlib svn co http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk opal wget ftp://ftp.videolan.org/pub/videolan/x264/snapshots/x264-snapshot-20100315-2… tar jcf ptlib.tar.bz2 ptlib & tar jcf opal.tar.bz2 opal & tar jcf h323plus.tar.bz2 h323plus & tar jcf extensions.tar.bz2 extensions & tar jcf applications.tar.bz2 applications & tar jcf ffmpeg.tar.bz2 ffmpeg & export PKG_CONFIG_PATH=/usr/local/ffmpeg/lib/pkgconfig:/usr/local/ptlib/lib/pkgconfig export LD_LIBRARY_PATH=/usr/local/ffmpeg/lib:/usr/local/ptlib/lib export PTLIBDIR=/usr/src/h323/ptlib export OPENH323DIR=/usr/src/h323/h323plus export PTLIBPLUGINDIR=/usr/local/ptlib/lib/pwlib cd /usr/src/h323 tar xf x264-snapshot-20100315-2245.tar.bz2 cd x264-snapshot-20100315-2245 ./configure --enable-shared > /dev/null && \ make -j4 > /dev/null && \ make install > /dev/null cd /usr/src/h323 tar xf ffmpeg.tar.bz2 cd ffmpeg ./configure --prefix=/usr/local/ffmpeg --enable-shared --enable-libx264 \ --enable-libtheora --enable-libvorbis --enable-gpl --enable-decoder=h263 \ --enable-decoder=h263i --enable-decoder=h264 --enable-decoder=theora \ --enable-encoder=h263 --enable-encoder=h263p --enable-encoder=libx264 \ --enable-encoder=libtheora && \ make -j4 > /dev/null && \ make install > /dev/null ldconfig cd /usr/src/h323 tar xf ptlib.tar.bz2 cd ptlib export PTLIBDIR=/usr/src/h323/ptlib ./configure --prefix=/usr/local/ptlib && \ make -j4 > /dev/null && \ make install > /dev/null cd /usr/src/h323 tar xf h323plus.tar.bz2 cd h323plus ./configure --prefix=/usr/local/h323plus && \ make -j4 > /dev/null && \ make install > /dev/null cd /usr/local/include ln -s /usr/local/ffmpeg/include/libavcodec/ ffmpeg cd /usr/src/h323 cd extensions/plugins ./configure --prefix=/usr/local/ptlib && \ make -j4 > /dev/null && \ make install > /dev/null cp -a /usr/local/ptlib/lib/pwlib /usr/local/ cd /usr/src/h323 tar xf applications.tar.bz2 cd applications/openmcu/ make -j4 > /dev/null && \ make install > /dev/null /etc/ld.so.conf.d/openmcu.conf: /usr/local/h323plus/lib cd /usr/local/ptlib/lib/pwlib/ ln -s /usr/local/ffmpeg/lib/libavcodec.so ldconfig cd /bin/openmcu -d -- Humilis IT Services and Solutions http://www.humilis.net

2 5

H264 PLUGIN in H323Plus
by ooi khai chin 19 Mar '10

19 Mar '10

Hi All, In my latest status, I able to have the conference with polycom and other softphone using H.264 plugin. But I face the problem of delaying (my movement only show on the other endpoint after around 5 seconds in local network). I think this problem occur because of fragmentation of 1 encoded picture that has size greater than 1.4KB to multiple slices, then sent it out. Currently, my default frame rate is 10fps. My question is how to solve the delaying problem because I see polycom PVX 8.0.2 and other softphone do not have any delay? Another question, If my default frame rate is 10fps, is it means that my program will call Codec Encode function 10 times in a second? As I know, inside the encode function, every time it will check for remanding frame length for last packet, if exist it repeatably packet it with size less than 1.4KB until finish, then it only start to encode a new frame. So, Let say I have one encoded picture that consist of 10 slices, is it means that I only able to sent one complete picture in 1 second (if my fps=10)? Thanks.

5 11

Re: [h323plus] [h323implementers] How does the H323Plus handles the codecs
by Simon Horne 23 Feb '10

23 Feb '10

This should be on the h323plus mailing list. You place the plugins directory next to src and header directories in the h323plus directory and then compile them seperately. This will create seperate **_p[t-w]libplugin.so files in the /release or /debug directory which you copy to your application directory or set the PTLIBPLUGINDIR env variable to point to directory you have placed your plugins. The plugins are automatically detected and loaded when you start your application. Simon _____ From: h323implementers-bounces(a)lists.packetizer.com [mailto:h323implementers-bounces@lists.packetizer.com] On Behalf Of Thiago Martins de Sousa Sent: Wednesday, 24 February 2010 7:47 AM To: h323implementers(a)lists.packetizer.com Subject: [h323implementers] How does the H323Plus handles the codecs Hi, I'm studying the H323Plus library to start a project but I have a doubt. How does it handles with de audio and video codecs? I look the source code and thought that I have to download the plugin and put then at the /include and then compile all together or I compile the source of the plugins and then put the archives *.o at the /include folder? _____ Fique protegido enquanto navega na Internet. Instale o Internet <http://go.microsoft.com/?linkid=9707132> Explorer 8.

1 0

Re: [h323plus] RES: h323plus working plugins
by Carlos Haj 29 Jan '10

29 Jan '10

Hello, I noticed that encoder_set_options of h263-ffmpeg plugin only works while codec initialising. So if you are interested to change bandwidth or quality setting during a videocall you must modify the plugin. in encoder_set_options: add context->Lock(); context->CloseCodec(); /* here options changing ... */ context->OpenCodec(); context->Unlock(); Then add two function Lock and UnLock to H263_Base_EncoderContext with a mutex to ensure no encoding frames while openning or closing a codec! CriticalSection _mutex; void Lock() { _mutex.Wait(); } void Unlock() { _mutex.Signal(); } Add a mutex signal to the beginning of H263EncoderContext::~H263EncoderContext() { WaitAndSignal m(_mutex); /* function code...*/ and int H263EncoderContext::EncodeFrames(const BYTE * src, unsigned & srcLen, BYTE * dst, unsigned & dstLen, unsigned int & flags) { WaitAndSignal m(_mutex); /* function code...*/ So the parameters of ffmepg h263 become usable at least! Anyone tried with h263-1998 ? I'm still not able to make it working for h323 for same reasons I mentioned in my first post. Could be interesting to share some ideas! Greetings, Carlo Subject: RES: [h323plus] h323plus working plugins Date: Fri, 22 Jan 2010 14:48:41 -0200 From: leandro.alvares(a)caixa.gov.br To: unazona(a)hotmail.com Hi Carlos, I got the same results as you.... I’m not happy with my vídeo quality (CIF) and I need to activate the H.264 or H.263 4CIF, but I’m having a lot of dificults.... Regards, Leandro Oliveira Alvares De: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] Em nome de Carlos Haj Enviada em: sexta-feira, 22 de janeiro de 2010 08:38 Para: h323plus(a)lists.packetizer.com Assunto: [h323plus] h323plus working plugins Hello Everyone, I've been experimenting Opal plugins on h323plus stack. I would like to share you my experience as it seems to me that most opal plugins doesn't work for h323plus. I compiled plugins along with correct ffmpeg and x264 revisions, on both windows and linux platforms. Here is my test results: H.261vic OK H.263_ffmpeg OK H.263_1998 * Crashes before packetising process, it works after I delay the packetiser function. * Video pixels are melting strikes, even while disabling all h263 annexes. MPEG4 * AVCodec crashes on encoder function H.264 * It doesn't compile at all after activating H323_H264_TEST * Complains about some missing constants, which I added * Compilation errors in structure definitions (h323 capabilities) Theora Not tested I'm unsure about the development priority and/or status of video plugins, as no document states that. Anyone tried to experiment video codecs using h323plus?! do you have same results as me?! Thanks, I appreciate. Vous cherchez l'intégrale des clips de Michael Jackson ? Bing ! Trouvez ! Subject: RES: [h323plus] h323plus working plugins Date: Fri, 22 Jan 2010 14:48:41 -0200 From: leandro.alvares(a)caixa.gov.br To: unazona(a)hotmail.com Hi Carlos, I got the same results as you.... I’m not happy with my vídeo quality (CIF) and I need to activate the H.264 or H.263 4CIF, but I’m having a lot of dificults.... Regards, Leandro Oliveira Alvares De: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] Em nome de Carlos Haj Enviada em: sexta-feira, 22 de janeiro de 2010 08:38 Para: h323plus(a)lists.packetizer.com Assunto: [h323plus] h323plus working plugins Hello Everyone, I've been experimenting Opal plugins on h323plus stack. I would like to share you my experience as it seems to me that most opal plugins doesn't work for h323plus. I compiled plugins along with correct ffmpeg and x264 revisions, on both windows and linux platforms. Here is my test results: H.261vic OK H.263_ffmpeg OK H.263_1998 * Crashes before packetising process, it works after I delay the packetiser function. * Video pixels are melting strikes, even while disabling all h263 annexes. MPEG4 * AVCodec crashes on encoder function H.264 * It doesn't compile at all after activating H323_H264_TEST * Complains about some missing constants, which I added * Compilation errors in structure definitions (h323 capabilities) Theora Not tested I'm unsure about the development priority and/or status of video plugins, as no document states that. Anyone tried to experiment video codecs using h323plus?! do you have same results as me?! Thanks, I appreciate. Vous cherchez l'intégrale des clips de Michael Jackson ? Bing ! Trouvez ! _________________________________________________________________ Découvrez Windows 7 en 7 secondes ! http://clk.atdmt.com/FRM/go/181574577/direct/01/

3 3

Re: [h323plus] Video Resolution
by Carlos Haj 22 Jan '10

22 Jan '10

Hello Simon, Thanks for your time and effort. I had the same problem using H263 plugin on both windows and linux. I found the glitch finally in h323plus code, the following function calls fine but sends absolutly nothing to the video plugin DLL h323pluginmgr.cxx::730 PBoolean SetCodecControl(...): you can verify that by tracing "encoder_set_options" in the video plugin dll!! Codec options can't be changed during a call, including framewidth, bandwidth, quality, etc... on the other hand, the call to encoder_set_options in H323PluginVideoCodec constructor works, that's why the plugin has initial default profile values. h323pluginmgr.cxx::1590 PluginCodec_ControlDefn * ctl = GetCodecControl(codec, SET_CODEC_OPTIONS_CONTROL); etc... I modified the SetCodecControl static function, here is it static PBoolean SetCodecControl(const PluginCodec_Definition * codec, void * context, const char * name, const char * parm, const char * value) { PluginCodec_ControlDefn * codecControls = GetCodecControl(codec, name); if (codecControls == NULL) return FALSE; PStringArray list; list += parm; list += value; char ** _options = list.ToCharArray(); unsigned int optionsLen = sizeof(_options); bool result = (*codecControls->control)(codec, context, SET_CODEC_OPTIONS_CONTROL, _options, &optionsLen); free(_options); return result; /* old Code .... char const * options[2] = { parm, value }; unsigned optionsLen = 2; return (*codecControls->control)(codec, context, SET_CODEC_OPTIONS_CONTROL, options, &optionsLen); */ } With that, I'm able to have a CIF-QCIF and QCIF-CIF calls!! Hope this was helpful, good luck appreciate your effort. Greetings, Carlos From: s.horne(a)packetizer.com To: unazona(a)hotmail.com Subject: RE: [h323plus] Video Resolution Date: Mon, 18 Jan 2010 22:50:42 +1000 Carlos The framesize information is passed to the encoder as part of the frame header information. The codec should adjust the frame size according to the header information passed to it. This would be a bug in the H.261 encoder. Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Carlos Haj Sent: Monday, 18 January 2010 9:19 PM To: h323plus(a)lists.packetizer.com Subject: Re: [h323plus] Video Resolution Simon, I've been working on this, I have more detailed results. First of all, my webcam VideoInputDevice has the correct qCIF size before the attachVideoReader, while tracing the read of the codec it the rawChannel and grabwidth and grabheight are correct. I traced the plugin DLL. When H323plus callback OpenVideoChannel, the videoCodec framesize is already set using H261EncoderContext::SetFrameSize(352,288); which corresponds to default frame size I suppose. The only problem.. A further call to codec.SetFrameSize sets the new framesize only in h323 capabilities, and it never reachs the plugin DLL I have traced one call to h261encodecontext::SetFrameSize. No trace for h261 setframesize while invoking the codec.setframesize. So, each call of H261 EncodeFrames(...) returns 0 on TRACE(1,"H261\tPayload of grabbed frame too small for full frame"); as assigned frameSize is different than the videoDevice. It seems that mediaFormat.SetOptionInteger never tell the pluginDLL about the frameSize option changing. Have you and idea? Regards, Carlos From: s.horne(a)packetizer.com To: unazona(a)hotmail.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Date: Sat, 16 Jan 2010 04:05:25 +1000 Carlos Maybe I should rephase my last email The old openH323 behaviour in the OpenVideoChannel allowed the user to safely set the webcam framesize to the default size of the codec because it was always fixed. So if your codec was CIF webcam was CIF. So that is why QCIF/CIF in both directions works. Now you have changed the frame size of CIF capability to QCIF in the codec it won't. Why? You must make sure in your code the framesize coming out of the VideoInputdevice when you create it is set to QCIF otherwise it will be CIF and the encoder will expect QCIF and that is why you are getting the codec encoder call returning 0 and the channel being closed down. Did I miss something? Simon From: Carlos Haj [mailto:unazona@hotmail.com] Sent: Saturday, 16 January 2010 3:24 AM To: s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Simon, I used fixed width and height to determine display and reader working, and I traced again my application. This time I went deeper into the h323plus library, I think it's a bug of h323plus, between the library and the video codec plugin. Bug Scenario: I have set AddAllCapabilities(0, P_MAX_INDEX, "*"); I only use H261 this time SetVideoFrameSize(H323Capability::cifMPI); Set the maximum Frame size and send a kind of parameter cifTag to the plugin on my OnVideoChannel I initialise if (encoder) codec.SetFrameSize(176, 144); This is the call stack by chronological order for an h323 video call using a CIF<->QCIF endpoint (trace is for endpoint that sending qcif) 1) H323PluginVideoCodec::H323PluginVideoCodec(...) it creates the encoder, and set frame size to CIF (the default plugin maximum value) 2) H323PluginVideoCodec::SetFrameSize(...) it adjusts the frame size, called from my OnVideoChannel, with qcif Value 3) H323PluginVideoCodec::Read(...) All work, my rawChannel, renderer, etc... until I reach line 1690 H323pluginmgr.cxx::1690 - THE FIRST READ call to encode video fails int retval = (codec->codecFunction)(codec, context, bufferRTP.GetPointer(), &fromLen, dst.GetPointer(), &toLen, &flags); retval = 0, which results into closing the channel as it returns false, if I change SetVideoFrameSize(H323Capability::cifMPI); into SetVideoFrameSize(H323Capability::qcifMPI); The codec function works again, but naturally with qCIF on both sides I think that once the codec parameter was tagged to use a cif or a qcif it can't change resolution during the call. so the encoding function fail for a resolution different than one setted using the SetVideoFrameSize. It's likely that the SetVideoFrameSize send an additional information to plugin code using a setcontrolcodec which are required later so the encoding function works properly. I noticed, that video resolution fail is only a local behaviour, and has nothing to do with remote endpoint. I will be debugging more, I still don't know the plugin code so much, so you might have a clearer idea than me? I think if you make a simple test you would encounter the same behaviour! Thanks From: s.horne(a)packetizer.com To: unazona(a)hotmail.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Date: Sat, 16 Jan 2010 01:37:07 +1000 Carlos You cannot know what the remote will send when you call OpenVideoChannel for the decoding side, that can only be done when you receive the first RTP packets. You need to do a level 6 trace to work out who and why the channel is being closed. I don't think it is a capability issue, usually the problem comes from either the video encoder device (webcam) or the display device. Check to see that you have set the video input device to send at the same size as your encoder. The old openH323 used to do be able to do that automatically as the frame size for the capability was known. You have to make sure the input to the encoder from the webcam is correct. Version of h323plus would be irrelevent in this case. Simon From: Carlos Haj [mailto:unazona@hotmail.com] Sent: Saturday, 16 January 2010 1:06 AM To: s.horne(a)spranto.com.au; s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Simon, Thanks for valuable information. What is happening literally in a minimised case: I derived OnVideoChannel on the Local endpoint if (encoding) { codec.SetFrameSize(352, 288); ..... } else { cout << codec.GetWidth(); cout << codec.GetHeight(); // I receive CIF (ERROR) ..... } on the Remote endpoint if (encoding) { codec.SetFrameSize(176, 144); ..... } else { cout << codec.GetWidth(); cout << codec.GetHeight(); // I receive CIF (normal) ..... } I looked into H323 trace Log, (remote endpoint which supposed to send QCIF) PLUGIN Error encoding frame from plugin H.261-CIF H245 Request CloseLogicalChannel H323RTP Transmit H.261-CIF thread ended It seems that the H.261 channel is closed prematurely. As my local endpoint received an incorrect video size I suppose that local endpoint causes remote to close the transmission channel. Could this be related to the version of the plugin or h323plus lib which I use? it's likely that the video resolution is sent before codec.SetFrameSize is invoked! Did you in practice used different video resolution under the same capability? e.g. CIF<->QCIF calls Carlos From: s.horne(a)spranto.com.au To: unazona(a)hotmail.com; s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Date: Fri, 15 Jan 2010 23:14:23 +1000 Carlos The current behaviour is correct. The old OpenH323 used to only send CIF with *-CIF{sw} capability and only QCIF with *-QCIF{sw} . This was changed with the video plugins so the capability could do up to CIF so it would also supported QCIF. This is perfectly H.245 legal. In this way only 1 capability can do both frame sizes. This is the way most manufacturers implement the capability exchange. The capability has a flag for the size it supports so the old CIF capability used to say QCIF - 0 CIF - 1. So if you wanted to do QCIF you had to use the *-QCIF{sw} capability as the QCIF flag in the *-CIF{sw} was 0. This was changed so that the *-CIF{sw} capability had the QCIF flag so it could also support QCIF. Then it was safe to remove the *-QCIF{sw} capability and only exchange using the *-CIF{sw}. Now SetVideoFrameSize() will set the global frame size limit so regardless of the direction that will be the maximum size permitted (if CIF only up to CIF capability is available). The codec.FrameSize() in the MyH323Endpoint::OpenVideoChannel() allows the implementor to set the actual frame size to send. Is there something else I missed? Simon From: Carlos Haj [mailto:unazona@hotmail.com] Sent: Friday, 15 January 2010 8:39 PM To: s.horne(a)packetizer.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Video Resolution Simon, Thanks for your quick answer, just noticed that I had a bad thread name;) Well, I have the codec.SetFrameSize(w, h); in my OpenVideoChannel When adding capabilities I use AddAllCapabilities(0, P_MAX_INDEX, "*"); SetVideoFrameSize(H323Capability::cifMPI); Capabilities table shows as Set 0: 0: audio 1: H.261-CIF{sw} I receive an OpenVideoChannel for encoder, I open channel and attach video reader + colourConverter, just after that I receive a close video signal from a H245Negotation, here I join Call Stack > testApp.exe!mmDDSVideoOutputBridge::close2() Ligne 359 C++ testApp.exe!mmVideoInputDevice::~mmVideoInputDevice() Ligne 43 + 0x1b C++ testApp.exe!mmVideoInputDevice::`scalar deleting destructor'() + 0x2b C++ testApp.exe!PVideoChannel::CloseVideoReader() Ligne 203 + 0x24 C++ testApp.exe!PVideoChannel::Close() Ligne 145 C++ testApp.exe!H323Codec::CloseRawDataChannel() Ligne 488 + 0x11 C++ testApp.exe!H323VideoCodec::Close() Ligne 747 C++ testApp.exe!H323Channel::CleanUpOnTermination() Ligne 716 C++ testApp.exe!H323_RTPChannel::CleanUpOnTermination() Ligne 1160 C++ testApp.exe!H245NegLogicalChannel::Release() Ligne 1219 C++ testApp.exe!H245NegLogicalChannel::HandleCloseAck(const H245_CloseLogicalChannelAck & __formal={...}) Ligne 1086 C++ testApp.exe!H245NegLogicalChannels::HandleCloseAck(const H245_CloseLogicalChannelAck & pdu={...}) Ligne 1372 + 0xf C++ testApp.exe!H323Connection::OnH245Response(const H323ControlPDU & pdu={...}) Ligne 3293 + 0x22 C++ testApp.exe!H323Connection::HandleControlPDU(const H323ControlPDU & pdu={...}) Ligne 3189 + 0x12 C++ testApp.exe!H323Connection::HandleControlData(PPER_Stream & strm={...}) Ligne 3170 + 0x18 C++ testApp.exe!H323Connection::HandleReceivedControlPDU(bool readStatus=true, PPER_Stream & strm={...}) Ligne 3103 + 0x12 C++ testApp.exe!H323Connection::HandleControlChannel() Ligne 3085 + 0x13 C++ testApp.exe!H245TransportThread::Main() Ligne 700 C++ If I remove the "SetVideoFrameSize(H323Capability::cifMPI);", I get the following capabilities set 1: H.261-CIF{sw} H.261-QCIF{sw} H.261{sw} with exactly same strange behaviour, QCIF is not sending while CIF is being received, by the way qcif endpoint says Local Video Codec - H.261-CIF{sw} Local Resolution - 176x144 Remote Video Codec - H.261-CIF{sw} Remote Resolution - 352x288 I tried a "ReorderCapabilities(PStringArray("QCIF"));" after my addcapabilities, I ended up with both endpoints using QCIF and ignoring my SetFrameSize anyway!! Is there a glitch using H323Plus video plugins? my code works perfectly on openh323 stack. "SetVideoFrameSize(H323Capability::cifMPI);" is supposed to define a maximum video resolution?! as you said in API doc "... to set the maximum framesize allowed to the specified value " Is that usual to have H.261-CIF with a QCIF resolution? On which order codec plugins can be added to avoid such problems of negotiation? Regards From: s.horne(a)packetizer.com To: unazona(a)hotmail.com; h323plus(a)lists.packetizer.com Subject: RE: [h323plus] Valid sessionID in OpenLogicalChannel command Date: Fri, 15 Jan 2010 08:12:54 +1000 Carlos In your derived H323EndPoint::OpenVideoChannel(() (isEncoding) codec.SetFrameSize(w,h); Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Carlos Haj Sent: Friday, 15 January 2010 12:59 AM To: h323plus(a)lists.packetizer.com Subject: Re: [h323plus] Valid sessionID in OpenLogicalChannel command Hello Guys, I would like to have different frame sizes for two endpoints, first I tried to play around with H323Endpoint::SetVideoFrameSize, but it seems that part changes the maximum allowed size, which means that if I switch the videoFrameSize to qCIF, I wouldn't be able to receive CIF from the other endpoint. my test only received QCIF. I tried also to modify the OpalMediaFormat by using a GetWritableMediaFormat for a capability, that ended with unusual CIF format while having a QCIF resolution. On the other hand, I looked Opal examples where they use an OpalManager, but unfortuntly that seems incompatible with h323plus, while old openh323 tutorials and exampls don't have any video plugins support. How I can manage to receive and send different resolutions (frame sizes) using H323plus? I appreciate a lot your help Carlos Discute avec tes amis partout, grâce à Messenger sur ton mobile. Cliquez ici ! Avec Internet Explorer, surfez en toute discrétion sur internet Cliquez ici ! Avec Internet Explorer, surfez en toute discrétion sur internet Cliquez ici ! Discute avec tes amis partout, grâce à Messenger sur ton mobile. Cliquez ici ! _________________________________________________________________ Découvrez Windows 7 en 7 secondes ! http://clk.atdmt.com/FRM/go/181574577/direct/01/

2 3

Generating docs
by Rogerio F Cunha 19 Jan '10

19 Jan '10

Hi All, I'm trying to generate the doxygen docs on 1.21.0 (make docs), but the openh323_cfg.dxy is missing. Is there any source for this file? Thanks Rogerio.

2 1

Valid sessionID in OpenLogicalChannel command
by Igor Pavlov 18 Jan '10

18 Jan '10

Hi. I have problem when I reject OpenLogicalChannel (audio) while communicating with Tandberg T1000. In most cases Tandberg send me OpenLogicalChannel again with sessionID=0 so my application falls in assertion in file rtp.cxx line 760 : PAssert(id > 0 && id < 256, PInvalidParameter); I could not find valid value range for sessionID, but I don't like when application crashes in this case :( What can I do in this situation? Igor Pavlov

4 17

Myphone2 FPS problem
by ooi khai chin 15 Jan '10

15 Jan '10

Hi All, Currently, I found that when I start the myphone2 application (compiled from myphone2 source code), the settings->device(settings dialog box) can not change to my own driver name, it show Microsoft WDM Image Capture <Win32>. I run the myphone2 exe provided, it show me my own device is "Logitech QuickCamPro 4000". If I used my own compiled version, It only show me the 10fps during conference with the other. While if I used the myphone2 exe provided(able show device "Logitech qucikCamPro 4000"). It can achieve 25-30fps. It happen for any video codec (H.261, H.263, H.264). Anyone, What is the problem? Thanks.

3 2

Re: [h323plus] Adding H263 codec to openmcu
by Michael Bondi 12 Jan '10

12 Jan '10

Hi Jan, I tried the ffmpeg 0.4.7 patched version you sent but the following happens: voyage:~/ffmpeg# make make -C libavcodec all make[1]: Entering directory `/root/ffmpeg/libavcodec' gcc -O3 -Wall -fPIC -g -DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o msmpeg4.o msmpeg4.c msmpeg4.c: In function 'msmpeg4_pred_dc': msmpeg4.c:845: warning: pointer targets in assignment differ in signedness msmpeg4.c: At top level: msmpeg4.c:660: warning: 'ff_old_msmpeg4_dc_scale' defined but not used wmv2.c:103: warning: 'wmv2_encode_end' defined but not used wmv2.c:481: warning: 'ff_wmv2_decode_init' defined but not used msmpeg4.c: In function 'msmpeg4_decode_dc': msmpeg4.c:734: error: can't find a register in class 'BREG' while reloading 'asm' common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints bswap.h:26: error: 'asm' operand has impossible constraints common.h:281: error: 'asm' operand has impossible constraints msmpeg4.c:734: error: 'asm' operand has impossible constraints msmpeg4.c:698: error: 'asm' operand has impossible constraints msmpeg4.c:698: error: 'asm' operand has impossible constraints make[1]: *** [msmpeg4.o] Error 1 make[1]: Leaving directory `/root/ffmpeg/libavcodec' make: *** [lib] Error 2 voyage 0.6.2 apt-get install flex bison build-essential subversion cvs pkg-config Mike Jan Willamowius wrote: > Hi Michael, > > here's my patched ffmpeg source. Its really just a quick fix until the > updated codec is ready. > > Regards, > Jan > > Michael Bondi wrote: > >> Hi Jan, >> >> Any idea of when the new ffmpeg 0.5 will be able to be compiled with >> h323 support? >> >> Are you able to supply me with your patched ffmpeg 0.4.7 so I can >> continue with my current compilation with gcc 4.3, albeit an inelegant >> solution? >> >> I'd like to learn how the openmcu works with your fantastic gnugk before >> the day is over. >> >> Mike >> >> Jan Willamowius wrote: >> >>> Yes, the old ffmpeg code doesn't compile with gcc 4.x. >>> >>> Jan >>> >>> Michael Bondi wrote: >>> >>> >>>> Hi Jan, >>>> >>>> It appears that I have ver 4.3 of gcc. >>>> >>>> Could that be the reason for the ffmpeg 0.4.7 make failure? >>>> >>>> Thanks >>>> >>>> Mike >>>> >>>> >>>> Jan Willamowius wrote: >>>> >>>> >>>>> I have a patched version of ffmpeg-0.4.7, that compiles with gcc 4.4.x, >>>>> but there is work going on to let the H.323-ffmpeg plugin compile with >>>>> current versions of ffmpeg, which is a much better solution. >>>>> >>>>> Regards, >>>>> Jan >>>>> >>>>> Michael Bondi wrote: >>>>> >>>>> >>>>> >>>>>> Thanks Prasad, >>>>>> >>>>>> I try install ffmpeg 0.4.7 from >>>>>> http://www.voxgratia.org/bin/ffmpeg-0.4.7.tar.gz but I get the following: >>>>>> >>>>>> voyage:~/ffmpeg-0.4.7# make >>>>>> make -C libavcodec all >>>>>> make[1]: Entering directory `/root/ffmpeg-0.4.7/libavcodec' >>>>>> gcc -O3 -Wall -g -DHAVE_AV_CONFIG_H -I.. -D_FILE_OFFSET_BITS=64 >>>>>> -D_LARGEFILE_SOURCE -D_GNU_SOURCE -c -o common.o common.c >>>>>> In file included from avcodec.h:14, >>>>>> from common.c:27: >>>>>> common.h:65: error: array type has incomplete element type >>>>>> common.h:69: error: array type has incomplete element type >>>>>> make[1]: *** [common.o] Error 1 >>>>>> make[1]: Leaving directory `/root/ffmpeg-0.4.7/libavcodec' >>>>>> make: *** [lib] Error 2 >>>>>> >>>>>> But I proceed and continue to configure and make and make install the >>>>>> a/v pugins in the ~/h323plus/plugins directory. >>>>>> >>>>>> I create a directory ~/codecs and copy both >>>>>> h263-ffmpeg_video_pwplugin.so and libavcodec.so (from the >>>>>> libavcodec-0.4.7-linux.bin.tar.gz file) into there. I rename >>>>>> libavcodec.so to avcodec >>>>>> >>>>>> I set export P_T_LIBPLUGINDIR=~/codecs (does this have to be >>>>>> P_W_LIBPLUGINDIR ?????) >>>>>> >>>>>> I run openmcu and connect with Polycom PVX, and I see the video >>>>>> window!! But the video has strange lines with pink and blue colours, >>>>>> but it is the video from the webcam! >>>>>> >>>>>> I assume it may be because I do not have the ffmpeg 0.4.7 installed >>>>>> correctly? >>>>>> >>>>>> I will have a look at installing ffmpeg 0.4.7 direct from ffmpeg site. >>>>>> >>>>>> So I am closer.... >>>>>> >>>>>> Thanks again for the help. >>>>>> >>>>>> Mike >>>>>> >>>>>> >>>>>> Prasad Mohire wrote: >>>>>> >>>>>> >>>>>> >>>>>>> HI Michael, >>>>>>> >>>>>>> I guess you have compiled PTLIB and H323plus and OpenMCU correctly. >>>>>>> H323plus doesn't need ffmpeg. ffmpeg is needed by h323plus avplugin. >>>>>>> You were able to hear audio because h323plus comes with G711 codecs. >>>>>>> You will need to build H263 plugin separately. >>>>>>> >>>>>>> h263 plugin needs ffmpeg version 0.47. To install it: >>>>>>> run ./configure --enable-shared, then make and make install in ffmpeg >>>>>>> directory. >>>>>>> >>>>>>> Once that is done, download the plugins directory from h323plus.com >>>>>>> <http://h323plus.com>. >>>>>>> untar the direcory under h323plus directory so that you will have >>>>>>> plugins directory under h323plus. >>>>>>> Goto plugins directory. >>>>>>> run ./configure >>>>>>> You should see h263 : yes in output of configure script. This means it >>>>>>> will build H.263 plugin. If it is 'no' there is something wrong with >>>>>>> prerequisites i.e. ffmpeg. make sure that libavcodec.h file is in >>>>>>> include path. >>>>>>> >>>>>>> once you see H.263: yes as output, run make and make install in >>>>>>> plugins directory. >>>>>>> create a directory to store the plugins. Set environment variable >>>>>>> PWLIBPLUGINDIR pointing to that directory. Copy >>>>>>> h323plus/plugins/video/h.263/h263-ffmpeg_video_pwplugin.so file to >>>>>>> $PWLIBPLUGINDIR. Copy libavcoded.so to $PWLIBPLUGINDIR and rename it >>>>>>> to avcodec. >>>>>>> >>>>>>> Now start openmcu, it should load with H.263 capability. >>>>>>> >>>>>>> File "C:\\traces.txt" will be created in directory from which you will >>>>>>> start openmcu. You can see what all capabilities are added while >>>>>>> openmcu is started in that file. >>>>>>> >>>>>>> >>>>>>> Thanks and Regards, >>>>>>> Prasad. >>>>>>> >>>>>>> >>>>>>> On Fri, Jan 8, 2010 at 3:32 PM, Michael Bondi >>>>>>> <mike(a)bridgeconference.co.za <mailto:mike@bridgeconference.co.za>> wrote: >>>>>>> >>>>>>> Hi all and Happy 2010! >>>>>>> >>>>>>> This may have been asked before, but I cannot help myself but to >>>>>>> ask again. >>>>>>> >>>>>>> I have compiled ptlib 2.4.5 and h323plus 1.21 and openmcu 2.2.5 on >>>>>>> a Debian 5 machine. >>>>>>> >>>>>>> I am able to connect and hear the tones and message for connecting >>>>>>> but am unable to get video on the screen. >>>>>>> >>>>>>> I have tried compiling h323plus with only the 0.4.7 ffmpeg >>>>>>> libavcodec.so placed in a directory /root/codec and compiled with >>>>>>> ./configure --enable-rfc2190avcodec=/root/ffmpeg switch, all >>>>>>> compiles fine, but still no h.263 video. Is there any more I need >>>>>>> to do here? >>>>>>> >>>>>>> Also, I am getting confused where to unpack and install the a/v >>>>>>> plugins from file >>>>>>> http://www.h323plus.org/source/download/plugins-v1_21_0.tar.gz >>>>>>> >>>>>>> Thanks >>>>>>> >>>>>>> Mike >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> >>>>> >>> >>> > > >

3 3

Adding H263 codec to openmcu
by Michael Bondi 11 Jan '10

11 Jan '10

Hi all and Happy 2010! This may have been asked before, but I cannot help myself but to ask again. I have compiled ptlib 2.4.5 and h323plus 1.21 and openmcu 2.2.5 on a Debian 5 machine. I am able to connect and hear the tones and message for connecting but am unable to get video on the screen. I have tried compiling h323plus with only the 0.4.7 ffmpeg libavcodec.so placed in a directory /root/codec and compiled with ./configure --enable-rfc2190avcodec=/root/ffmpeg switch, all compiles fine, but still no h.263 video. Is there any more I need to do here? Also, I am getting confused where to unpack and install the a/v plugins from file http://www.h323plus.org/source/download/plugins-v1_21_0.tar.gz Thanks Mike

3 7

H264 PLUGIN in H323plus
by ooi khai chin 24 Dec '09

24 Dec '09

Hi All, In my situation, I have set my marker to 1 when it is the last partial frame, And it able to display on the remote endpoint every frame I sent. The problem is it just delay around 5s for all frame picture. Why? I already do some testing on my x264 encoder, it can encode frame with acceptable speed, So it wouldn't be encoder problem. Thanks.

2 2

Karl Ma has invited you to Dropbox
by Dropbox 22 Dec '09

22 Dec '09

We're excited to let you know that Karl Ma has invited you to Dropbox! Karl Ma has been using Dropbox to sync and share files online and across computers, and thought you might want it too. Visit http://www.dropbox.com/link/20.op9FTprDrn/NjY4MzAwMDk3 to get started. - The Dropbox Team ____________________________________________________ To stop receiving invites from Dropbox, please go to http://www.dropbox.com/bl/56c7d1c0a6d5/h323plus%40lists.packetizer.com

1 0

Peer Element support in H323plus
by Hossein Aminaiee 13 Dec '09

13 Dec '09

Hi, We are trying to implement a gatekeeper with border element supported, such as the one in Tenor-Axx gatekeepers. I am curious to know whether it is supported by H323plus project or not. We have implemented the gatekeeper functionality with GnuGK and the platform is based on the latest version of Asterisk. Any advise is appreciated in advance. Thanks, Hossein Aminaiee

1 0

GPL awareness week
by Jan Willamowius 07 Dec '09

07 Dec '09

Hi, as most of you probably know, the GNU Gatekeeper is covered by the GNU Public license (GPL v2). Using GnuGk commercially is fine and it is also no problem to include it into commercial offerings as long as long as the proper credit is given and the modified source code is made available. Usually this works out fine, but sometimes a vendor needs a friendly reminder. So I would like to start a "GPL awareness week" where we all keep an open eye which products include the GNU Gatekeeper and check if they give credit and if the source code is available. I started a page to publish the code patches from vendors who bundle GnuGk at http://www.gnugk.org/gnugk-bundle.html If you know more applications that ship with GnuGk or have questions about the licensing details, please contact me off list. Let make sure everybody who uses GnuGk knows about it and enjoys the full benefits that the GPL guarantees! Regards, Jan -- Jan Willamowius, jan(a)willamowius.de, http://www.gnugk.org/

1 0

H264 PLUGIN in H323Plus
by ooi khai chin 07 Dec '09

07 Dec '09

Hi All, Currently, I would like to know how a NAL unit is organized inside an encoded data. Then, I read about the H.264 documentation, it mention about how to organize the NAL unit is outside of specification. So, anyone know any information or details on how the NAL organized? Thanks.

1 0

H264PLUGIN in H323plus
by ooi khai chin 02 Dec '09

02 Dec '09

Hi All, Currently, my H.264 encoded data is generated from hardware, not using software encoder libx264. And that hardware API only return me the whole encoded data buffer, and it's total size. So, is there anyway to extract, format the whole encoded data into NAL slice(less than 1.4KB) manually? Thanks.

1 0

H264 PLUGIN In H323Plus
by ooi khai chin 02 Dec '09

02 Dec '09

Hi All, I read about the RFC3984 for H.264, one of the type it can support is fragmentation Unit Mode(FU). In FU mode, the packet must add FU indicator(1 byte) and FU Header (1 byte). Indicator format F|NRI|TYPE Header format S|E|R|TYPE my question is why we need to include the NAL type twice in RTP packet of this (FU)mode? Thanks.

2 1

compiling h323 on Fedora 12
by mimiller＠ncsa.illinois.edu 01 Dec '09

01 Dec '09

I've compiled PTLib on Fedora 12 and all went well. But when compiling h323, it can't find the ptlib files it needs. Below is a listing of what I did and some results along the way. Let me know what I'm doing wrong. thanks Michael 21 mkdir sources 22 cd sources/ 24 svn co http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/trunk ptlib 25 svn co http://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/trunk opal 27 sudo yum install bison 28 sudo yum install flex cd ptlib 34 ./configure --enable-debug 35 make debug 36 sudo make install *******error can't find libpt_s.a 37 ls lib_linux_x86/ 40 cp lib_linux_x86/libpt_d_s.a lib_linux_x86/libpt_s.a 41 sudo make install *******PTLib appears to be installed in /usr/local/lib 42 cd .. 43 cd opal/ 46 export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig 48 export LD_LIBRARY_PATH=/usr/local/lib 49 export PTLIBPLUGINDIR=/usr/local/lib/ptlib-2.7.1 53 export PTLIBDIR=/usr/local/lib/ 54 ./configure --enable-debug ******* CXXFLAGS: -felide-constructors -Wreorder DEBUG: -L/usr/local/lib -lpt_d RELEASE: -L/usr/local/lib -lpt checking ptlib version... 2.7.1 configure: error: Could not find a linkable ptlib in specified environment to verify symbols (debug ptlib: yes) ******* 62 sudo ln -s /home/mimiller/sources/ptlib/lib_linux_x86 /usr/local/lib/ptlibdir 64 export PTLIBDIR=/usr/local/lib/ptlibdir 65 cd ~/sources/opal/ 66 ./configure --enable-debug ******* CXXFLAGS: -felide-constructors -Wreorder DEBUG: -L/usr/local/lib -lpt_d RELEASE: -L/usr/local/lib -lpt checking ptlib version... 2.7.1 configure: error: Could not find a linkable ptlib in specified environment to verify symbols (debug ptlib: yes) ******* 77 export PTLIBDIR=/usr/local/lib 78 ./configure --enable-debug ******* CXXFLAGS: -felide-constructors -Wreorder DEBUG: -L/usr/local/lib -lpt_d RELEASE: -L/usr/local/lib -lpt checking ptlib version... 2.7.1 configure: error: Could not find a linkable ptlib in specified environment to verify symbols (debug ptlib: yes) ******* 80 sudo cp /home/mimiller/sources/ptlib/lib_linux_x86/*.* /usr/local/lib/ptlib-2.7.1/ 83 export PTLIBDIR=/usr/local/lib/ptlib-2.7.1 84 set 85 ./configure --enable-debug ******* CXXFLAGS: -felide-constructors -Wreorder DEBUG: -L/usr/local/lib -lpt_d RELEASE: -L/usr/local/lib -lpt checking ptlib version... 2.7.1 configure: error: Could not find a linkable ptlib in specified environment to verify symbols (debug ptlib: yes) ******* 106 cvs -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus login 110 cvs -z3 -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus co h323plus 112 cvs -z3 -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus co extensions 113 cvs -z3 -d:pserver:anonymous@h323plus.cvs.sourceforge.net:/cvsroot/h323plus co applications 115 export PTLIBDIR=/usr/local/lib 116 cd h323plus/ ******* configure: gcc version is 4.4.2 checking if gcc version is valid... yes checking for working bit scan intrinsic... yes configure: Opal version is 3.7.1 checking where plugins are being installed... /usr/local/lib/opal-3.7.1 checking wether to build a shared library... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking Debugging support... no Found PTLIB in PTLIBDIR /home/mimiller/sources/ptlib/ Version: 2.7.1 CFLAGS: -DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/local/include CXXFLAGS: -felide-constructors -Wreorder DEBUG: -L/usr/local/lib -lpt_d RELEASE: -L/usr/local/lib -lpt checking ptlib version... 2.7.1 configure: error: Could not find a linkable ptlib in specified environment to verify symbols (debug ptlib: no) ******* 118 ./configure 119 export PTLIBDIR=/home/mimiller/sources/ptlib/ 120 ./configure ******* configure: gcc version is 4.4.2 checking if gcc version is valid... yes checking for working bit scan intrinsic... yes configure: Opal version is 3.7.1 checking where plugins are being installed... /usr/local/lib/opal-3.7.1 checking wether to build a shared library... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking Debugging support... no Found PTLIB in PTLIBDIR /home/mimiller/sources/ptlib/ Version: 2.7.1 CFLAGS: -DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/local/include CXXFLAGS: -felide-constructors -Wreorder DEBUG: -L/usr/local/lib -lpt_d RELEASE: -L/usr/local/lib -lpt checking ptlib version... 2.7.1 configure: error: Could not find a linkable ptlib in specified environment to verify symbols (debug ptlib: no) ******* "If you're clear in your vision and trust the people in your team with clear objectives, they will invariably do their best to achieve everything desired, and usually deliver everything you could have hoped for and even more." -Paul Debevec "If you're clear in your vision and trust the people in your team with clear objectives, they will invariably do their best to achieve everything desired, and usually deliver everything you could have hoped for and even more." -Paul Debevec

2 1

IPSocks and errno Headers
by Marcos Fábio Jardini 01 Dec '09

01 Dec '09

Hello all Report about porting ptlib solution to Visual Studio 2010: ** PTLib_2008.sln (can correspondent projects [.vcproj]) successfully ported to PTLib_2010.sln (and [.vcxproj | .filters]): removed all reference to Windows Mobile cause VS2010Beta2 don't work with mobile. ** Only have compilation warnings, so the lib update and compile without errors LOG: "[...]ptlib\include\ptlib\msos/ptlib/ipsock.h [several] warning C4005: 'XXXXXXXXXX' : macro redefinition" >>Visual Studio getting more close to standard C (C++0x), the macros in ipsock.h already defined in [...]Microsoft Visual Studio 10.0\VC\include\errno.h /*** *errno.h - system wide error numbers (set by system calls) * * Copyright (c) Microsoft Corporation. All rights reserved. * *Purpose: * This file defines the system-wide error numbers (set by * system calls). Conforms to the XENIX standard. Extended * for compatibility with Uniforum standard. * [System V] * * [Public] * ****/ << "collect.cxx(54)(241)(417)(452)(457): warning C4244: 'initializing' : conversion from 'std::streamsize' to 'int', possible loss of data" "pchannel.cxx(124): warning C4244: 'argument' : conversion from '__int64' to 'off_t', possible loss of data" "ptime.cxx(78): warning C4244: 'initializing' : conversion from 'std::streamsize' to 'int', possible loss of data" "ptime.cxx(88): warning C4244: 'argument' : conversion from 'std::streamsize' to 'int', possible loss of data " "asner.cxx(981)(1142)(1612)(2089)(2267)(2354): warning C4244: 'initializing' : conversion from 'std::streamsize' to 'int', possible loss of data "snmp.cxx(34)(313)(427)(524): warning C4244: 'initializing' : conversion from 'std::streamsize' to 'int', possible loss of data" >> Visual Studio getting more close to standard C (C++0x), strong typing waring << **Hello_world static: work! OK **Hello_world dynamic: work! OK -- ----- Jogue RPG, alimente o lado criativo!

2 1

PacPhone 2.3.0 Released
by Simon Horne 30 Nov '09

30 Nov '09

Guys www.pacphone.com PacPhone 2.3.0 has been released. It has been extensively tested with the latest GnuGk release. Special thanks to all the people who tested the pre-Release and provided feedback. Anyone has any questions let me know. Simon

1 0

missing RTP Frames
by Igor Pavlov 27 Nov '09

27 Nov '09

Hello. I missing RTP frames, when connect with my H264 plugin on connection speed greater then approximately 256 kBps. I inserted logging of rtp frames sequencenumber in function RTP_Session::SendReceiveStatus RTP_UDP::ReadDataPDU(RTP_DataFrame & frame); after call SendReceiveStatus status = ReadDataOrControlPDU(*dataSocket, frame, TRUE); and periodicaly I have holes in sequence of numbers. At the same time I have working sniffer, and I see that RTP packet missing in my logs is present in sniffers statistics. I tryed to find the place in h323plus sources where can I miss RTP packets, but couldn't find it :( The missed group of packets (even if length of group is 1 - single packet) always ends with rtp packet which have marker=0 Help me to find out the reason why I missing packets. Because of speed?

1 0

GNU Gatekeeper 2.3.1 released
by Jan Willamowius 26 Nov '09

26 Nov '09

Hi, a new stable version of the GNU Gatekeeper is now available. Source code and executables can be downloaded from http://www.gnugk.org/h323download.html Executables are available for - Linux (32 bit and 64 bit) - Windows (XP, Vista, Windows7, ...) - MacOSX (PPC and Intel) - Solaris 10 - FreeBSD - OpenBSD What's new in 2.3.1 ? - lots of interoperability fixes for H.460.18/.19 based on the feedback from the community - new routing policy "CatchAll" - new [ModeSelection] section to fine tune when to proxy calls - support for setting the proxy mode per call using Radius - support for ignoring case and alias type (calling "FOO" will match alias "foo") - H.460.23/.24 support updated to the now approved standard - many bug fixes, eg. for direct mode and URI dialing - a unified binary for MacOS X that works both on PPC and Intel - Firebird database driver updated - many small improvements in the manual See below for the full list of changes. Enjoy, Jan -- Jan Willamowius, jan(a)willamowius.de http://www.gnugk.org/ http://www.willamowius.de/gnugk-support.html Changes from 2.3.0 to 2.3.1 =========================== - Firebird database driver updated for Firebird 2.0.x and 2.1.x - BUGFIX(Toolkit.cxx) don't ignore ExternalIP settings when NetworkInterfaces= is set - BUGFIX(SoftPBX.cxx) make response messages more consistent - the old format (2.0) to specify neighbor gatekeepers is deprecated now and has been removed from the manual; it still works, but may be removed from future versions - BUGFIX(ProxyChannel.cxx) only close endpoints logical channel on CloseLogicalChannel, use [Proxy]SearchBothSidesOnCLC=1 to retain the old behavior - BUGFIX(Toolkit.cxx) Enable RewritePString to rewrite address correctly if unregistered full URI. - BUGFIX(Neighbor.cxx) srv policy now fails calls and doesn't pass them to the next policy if a SRV record exists for a domain, but doesn't have a destination for the call - allow to set proxy mode through 'proxy' variable in Radius h323-ivr-in attribute (thanks to Yuriy Georgiewskiy) - BUGFIX(Routing.cxx) let dns policy handle LRQs that resolve locally, so URI dialing from neighbors works - the manual has been improved (thanks to Robert Kulagowski) - set Radius VSA attribute h323_rtp_proxy in stop event (thanks to Yuriy Georgiewskiy) - BUGFIX(ProxyChannel.cxx) fix memory leak when creation of a fastStart channel fails - status port command DisconnectIP now also works with unregistered endpoints using the std port - BUGFIX(ProxyChannel.cxx) fix handling of H.460.19 RTP keepalive packets - new switch [Proxy]DisableRTPQueueing=1 - BUGFIX(ProxyChannel.cxx) fully initialize UDP proxy IPs and ports - BUGFIX(Routing.cxx) don't apply dns policy to aliases of type dialedDigits - BUGFIX(Toolkit.h/.cxx) use default IP for networks specified in InternalNetwork=, not ExternalIP - enable data execution protection on Windows versions that support it (starting with XP SP3) - BUGFIX(gk.cxx) make sure Windows service writes same trace format as application (including file and line) - BUGFIX(Neighbor.cxx) fix memory leak in srv policy, only send the local part of the alias in the LRQ - new switch [RoutedMode]H46018NoNat to disable H.460.18 if no NAT detected (default enabled) - new routing policy 'catchall' to route all calls to one alias or IP - new Radius attributes on stop: h323pddtime, h323ringtime, h323routeattempts - BUGFIX(Neighbor.cxx) fix srv policy for direct mode, don't send LRQ if SRV points to us - new switch [RoutedMode]TranslateSorensonSourceInfo=1 to convert the Sorenson VP200 caller information - BUGFIX(GkStatus.cxx) don't flush status port socket when access is denied to avoid blocking - new switches in [Gatekeeper::Main]: CompareAliasType and CompareAliasCase to switch off alias type and case matching - BUGFIX(Routing.cxx) fix dns policy for direct mode - BUGFIX(Neighbor.cxx) try next policy if SRV lookup fails - neighbor type (GnuGk|CiscoGk|ClarentGk|GlonetGk) is now case insensitive - features documented: [AssignedAliases::SQL], [AssignedGatekeepers::SQL] and [GkQoSMonitor::SQL] - BUGFIX(RasTbl.cxx) use rewritten number when decrementing prefix capacity counters, so they match the increment - feature to set a ClientAuthId in SqlAuth that is provided as %{client-auth-id} on all accounting events - new status port command ResetCallCounters - changed ProxyForSameNAT default from 0 to 1 (to avoid media failure uncertainty) - BUGFIX(RasSrv.cxx) IsReachable looks at correct route table. (virtual was ignored) - changed [RoutedMode]EnableH46024= to be consistent with H.460.18 switch - BUGFIX(RasSrv.cxx) RCF messages H.460 features now supported Features not GenericData - BUGFIX(ProxyChannel.cxx) H.460.19 working with Fast Connect - BUGFIX(RasSrv.cxx,ProxyChannel.cxx) Tandberg MXP interoperability fixes - BUGFIX(ProxyChannel.cxx) check capacity on routes supplied by authenticators (Radius, SQL etc.) - BUGFIX(RasSrv.cxx) avoid cutting off status messages after 1000 chars (problem in PString::Printf) - BUGFIX(ProxyChannel.cxx) fix for fastStart with H.460.19 - new switch [RoutedMode]EnableH.460.24=, which defaults to OFF - send RTCP statistics to Radius server (thanks to Yuriy Georgiewskiy) - BUGFIX(Toolkit.cxx) fix a crash in RewriteE164() when casting aliases - new config section [ModeSelection] to specify the routing/proxy mode by IP network

1 0

OpenMCU Codec issues
by Josh Barth 25 Nov '09

25 Nov '09

I have the ptlib, h323plus, plugins, and openmcu from h323plus.org I built each successfully, but I am not having any luck getting the additional codecs loaded when I launch OpenMCU, all I get is G.711. Did I not build something right? In order I built, ptlib, h323plus, openmcu, plugins Where should the codecs be located? (they are in /usr/local/lib/pwlib) These are modular correct, I don't need to re-compile h323plus or OpenMCU? Here is my trace: 0:00.081 OpenMCU Version 2.2.5 by H323plus on Unix Linux (2.6.26-2-sparc64-sparc64) at 2009/11/17 14:43:29.321 0:00.082 OpenMCU PWLib File handle high water mark set: 15 Thread unblock pipe 0:00.082 OpenMCU PWLib Created thread 0x162c78 H323 Listener:%0x 0:00.083 OpenMCU PWLib File handle high water mark set: 16 PTCPSocket 0:00.083 OpenMCU H323 Started listener Listener[ip$*:1720] 0:00.084 OpenMCU PWLib Thread high water mark set: 6 0:00.085 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.085 OpenMCU H323 Added capability: G.711-ALaw-64k <1> 0:00.085 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.086 OpenMCU H323 Added capability: G.711-uLaw-64k <2> 0:00.086 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU EXT No Extended Capabilities found to load 0:00.088 OpenMCU H323 FindCapability: "*-QCIF*" 0:00.088 OpenMCU H323 FindCapability: "*-SQCIF*" 0:00.088 OpenMCU H323 Added capability: UserInput/hookflash <3> 0:00.088 OpenMCU H323 Added capability: UserInput/basicString <4> 0:00.088 OpenMCU H323 Added capability: UserInput/dtmf <5> 0:00.089 OpenMCU H323 Added capability: UserInput/RFC2833 <6> 0:00.089 OpenMCU H323 Added capability: UserInput/Navigation <7> 0:00.089 OpenMCU H323 Added capability: UserInput/Softkey <8> 0:00.089 OpenMCU H323 Added capability: UserInput/PointDevice <9> 0:00.089 OpenMCU H323 Added capability: UserInput/Modal <10> 0:00.089 OpenMCU MCU Codecs (in preference order): Table: G.711-ALaw-64k <1> G.711-uLaw-64k <2> UserInput/hookflash <3> UserInput/basicString <4> UserInput/dtmf <5> UserInput/RFC2833 <6> UserInput/Navigation <7> UserInput/Softkey <8> UserInput/PointDevice <9> UserInput/Modal <10> Set: 0: 0: G.711-ALaw-64k <1> G.711-uLaw-64k <2> 1: 2: UserInput/hookflash <3> UserInput/basicString <4> UserInput/dtmf <5> UserInput/RFC2833 <6> UserInput/Navigation <7> UserInput/Softkey <8> UserInput/PointDevice <9> UserInput/Modal <10> 0:00.094 OpenMCU PWLib File handle high water mark set: 17 PTCPSocket 0:00.095 OpenMCU PWLib File handle high water mark set: 19 Thread unblock pipe 0:00.095 OpenMCU PWLib Created thread 0x168620 HTTP Service 0:00.095 H323 Listener:f6f8bb90 PWLib Started thread 0x162c78 H323 Listener:f6f8bb90 0:00.095 H323 Listener:f6f8bb90 H323 Awaiting TCP connections on port 1720 0:00.095 H323 Listener:f6f8bb90 TCP Waiting on socket accept on ip$*:1720

4 9

H264 Plugin in H323Plus
by ooi khai chin 25 Nov '09

25 Nov '09

Hi All, regarding the H.241 documentation, it mention that H.264 plugin in H.323 only support single NAL mode. Then, I refer the RFC 3984, it state that single NAL mode only support type 1-23 NAL unit, no FU-A, no FU-B, ... Currently, I am using H.264 hardware encoder which used baseline profile, not libx264. My H.264 encoder(hardware) will only return the whole encoded data and it's total length, not each NAL and it's length. So, how can I make it comply to H.323 if no fragmentation is allowed in H.323? Thanks.

2 1

H264 PLUGIN in h323plus
by ooi khai chin 24 Nov '09

24 Nov '09

Hi All, For the libx264, It directly fragment the encoded data if it larger than the maxpayloadsize (1.4KB by default). If I had encoded data 5.6K. Then, it will fragment and sent out, 4 times. Is it comply to H.323 standard? Because currently other voip (polycom, Mirial...) can't display my encoded data size greater than 1.4K. Thanks.

2 1

H264 PLUGIN in H323Plus
by ooi khai chin 24 Nov '09

24 Nov '09

Hi All, Currently, my H264 plugin able to work with polycom. I found that the media statistic(polycom PVX ) only show the frame rate video format, and display the image if my sending encoded data is not more than 1.4KB. In my code, I do the fragmentation once it greater than 1.4KB(like libx264 do). However, I had read some documentations and all of them mentioned about H.241 only support the single NAL unit mode(mode 0). I wonder how this mode handle if encoded data greater than 1.4KB(usually happen)??? Any Idea? Thanks.

3 3

H264 PLUGIN in H323Plus
by ooi khai chin 23 Nov '09

23 Nov '09

Hi All, I captured the capability exchange from difference voip software like(polycom, vcon...), it show only "0.0.8.241.0.0.1", which is defined as OpalPluginCodec_Identifier_H264_Generic. 1. What is the difference with the others like (default, RFC3984 interleave, RFC3984 non interleave)? Another things is that When I use my H.264 Encoder API, it only return me the encoded data and the encoded length. 2. So, is it considered as single NAL unit? How it can be comply to H.323 since the default MTU value in H.323 is 1400bytes (like fragmentation or other)? I try to increate the MTU value, but it cause me error.

2 1

Re: [h323plus] [Openh323gk-users] PTLIB PASN_BMPString handling changes and endpoint not registered.
by Simon Horne 18 Nov '09

18 Nov '09

Guys I need to make you aware of a change that causes different registration endpoint identifier lengths to be generated based on the version of ptlib used. GnuGK 2.3.0 (ptlib 2.4.5) registrationConfirm { ... endpointIdentifier = 9 characters { 0034 0033 0039 0035 005f 0065 006e 0064 4395_end 0070 p } GnuGk 2.3.1 (ptlib cvs) registrationConfirm { ... endpointIdentifier = 10 characters { 0034 0033 0039 0035 005f 0065 006e 0064 4395_end 0070 0000 p } While this may not look too much of a problem however if you are registering a h323plus endpoint built off a later version of PTLIB (like PacPhone) on a GnuGk with an earlier version of PTLIB then your endpoint will register but will not be able to make any calls and you will get an error about endpoint not registered. This is because the gatekeeper generated a 9 character endpointIdentifer while the endpoint will send a 10 digit identifier to the gatekeeper. I have patched the latest PacPhone preRelease to resolve the problem www.pacphone.com/downloads/PacPhoneSetup230.exe I will be applying a fix to the H323plus CVS shortly. Simon

1 0

Re: [h323plus] OpenMCU Codec issues
by Simon Horne 18 Nov '09

18 Nov '09

Josh Put the plugins in /usr/lib/ptlib they will automatically be read in at application startup. There is no need to recompile OpenMCU. Simon _____ From: Josh Barth [mailto:jbarth@buttechc.com] Sent: Wednesday, 18 November 2009 10:38 AM To: 'Simon Horne' Subject: RE: [h323plus] OpenMCU Codec issues So I still have the same issue, I have set the PTLIBPLUGINDIR env var. Should the structure then be /usr/local/lib/ptlib and then each of the libraries? Or should they exist in codecs/ or codecs/audio/ and codecs/video/ I am right in thinking once these are placed properly OpenMCU should pick them up? I don't have to place them, then recompile OpenMCU do I? Thanks very much, Josh From: Simon Horne [mailto:s.horne@packetizer.com] Sent: Tuesday, November 17, 2009 5:17 PM To: Josh Barth Subject: RE: [h323plus] OpenMCU Codec issues Josh The default directory for plugins should be /usr/lib/ptlib unless you set the environment variable PTLIBPLUGINDIR to point to your plugin directory. Simon _____ From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Josh Barth Sent: Wednesday, 18 November 2009 9:45 AM To: 'h323plus(a)lists.packetizer.com' Subject: [h323plus] OpenMCU Codec issues I have the ptlib, h323plus, plugins, and openmcu from h323plus.org I built each successfully, but I am not having any luck getting the additional codecs loaded when I launch OpenMCU, all I get is G.711. Did I not build something right? In order I built, ptlib, h323plus, openmcu, plugins Where should the codecs be located? (they are in /usr/local/lib/pwlib) These are modular correct, I don't need to re-compile h323plus or OpenMCU? Here is my trace: 0:00.081 OpenMCU Version 2.2.5 by H323plus on Unix Linux (2.6.26-2-sparc64-sparc64) at 2009/11/17 14:43:29.321 0:00.082 OpenMCU PWLib File handle high water mark set: 15 Thread unblock pipe 0:00.082 OpenMCU PWLib Created thread 0x162c78 H323 Listener:%0x 0:00.083 OpenMCU PWLib File handle high water mark set: 16 PTCPSocket 0:00.083 OpenMCU H323 Started listener Listener[ip$*:1720] 0:00.084 OpenMCU PWLib Thread high water mark set: 6 0:00.085 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.085 OpenMCU H323 Added capability: G.711-ALaw-64k <1> 0:00.085 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.086 OpenMCU H323 Added capability: G.711-uLaw-64k <2> 0:00.086 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU EXT No Extended Capabilities found to load 0:00.088 OpenMCU H323 FindCapability: "*-QCIF*" 0:00.088 OpenMCU H323 FindCapability: "*-SQCIF*" 0:00.088 OpenMCU H323 Added capability: UserInput/hookflash <3> 0:00.088 OpenMCU H323 Added capability: UserInput/basicString <4> 0:00.088 OpenMCU H323 Added capability: UserInput/dtmf <5> 0:00.089 OpenMCU H323 Added capability: UserInput/RFC2833 <6> 0:00.089 OpenMCU H323 Added capability: UserInput/Navigation <7> 0:00.089 OpenMCU H323 Added capability: UserInput/Softkey <8> 0:00.089 OpenMCU H323 Added capability: UserInput/PointDevice <9> 0:00.089 OpenMCU H323 Added capability: UserInput/Modal <10> 0:00.089 OpenMCU MCU Codecs (in preference order): Table: G.711-ALaw-64k <1> G.711-uLaw-64k <2> UserInput/hookflash <3> UserInput/basicString <4> UserInput/dtmf <5> UserInput/RFC2833 <6> UserInput/Navigation <7> UserInput/Softkey <8> UserInput/PointDevice <9> UserInput/Modal <10> Set: 0: 0: G.711-ALaw-64k <1> G.711-uLaw-64k <2> 1: 2: UserInput/hookflash <3> UserInput/basicString <4> UserInput/dtmf <5> UserInput/RFC2833 <6> UserInput/Navigation <7> UserInput/Softkey <8> UserInput/PointDevice <9> UserInput/Modal <10> 0:00.094 OpenMCU PWLib File handle high water mark set: 17 PTCPSocket 0:00.095 OpenMCU PWLib File handle high water mark set: 19 Thread unblock pipe 0:00.095 OpenMCU PWLib Created thread 0x168620 HTTP Service 0:00.095 H323 Listener:f6f8bb90 PWLib Started thread 0x162c78 H323 Listener:f6f8bb90 0:00.095 H323 Listener:f6f8bb90 H323 Awaiting TCP connections on port 1720 0:00.095 H323 Listener:f6f8bb90 TCP Waiting on socket accept on ip$*:1720

1 0

[OT] New chan_h323 now Asterisk will not load
by Mark Best 17 Nov '09

17 Nov '09

First off sorry if this is a bit off topic. I've changed the Asterisk code from BOOL to PBoolean and chan_h323 compiles, but now Asterisk 1.6.0.17 crashes when I attempt to start it. There is no /var/log/asterisk/full log to check. I moved the chan_h323.so out of the /usr/lib/asterisk/modules/ folder, but it's still crashes. Anyone have any experience with this sort of thing? Does a different version of 1.6/1.4 work better than another?

1 0

OpenMCU 2.2.5 BUG?
by leandro.alvares＠caixa.gov.br 17 Nov '09

17 Nov '09

Hi, I'm getting a green screen at openmcu 2.2.5. It doesn't happen when I'm using 2.2.3 version. Any suggestion will be appreciated. Thanks. Regards, Leandro

1 0

H264 Plugin in H323plus
by ooi khai chin 17 Nov '09

17 Nov '09

Hi All, currently, I had been compiled the h264plugin from opal project, together with libx264,avcodec and any stuff to make it work. when, I do a conference on both side using my own codec in MyPhone2, It work fined. The problem occur when I communicate with other voip software like polycom, VCON... In the polycom(PVX 8.0.2) media statistic, it show both side info as below: People Tx People Rx ------------------------------------------------------- Video Protocol: H.264 H.264 Video Rate: 320 320 Video Rate Used: 319 84 Video Frame Rate: 15 0 Video Packet Lost: 0 0 Video jitter: 0 2 Video Format: QVGA ----- Audio Protocol: G.711U G.711A Audio Rate: 64 64 Audio Packets Lost: 0 0 Audio Jitter: 0 0 The frame rate and video format got problem... Do I need to specify video format and video frame rate in H323plus (generic capability), Any Idea??? Thanks.

3 2

Re: [h323plus] ast_h323.h:104: error: 'BOOL' has not been declared
by Mark Best 17 Nov '09

17 Nov '09

First I tried a newer version of Ptlib. It appears Ptlib 2.7 isn't compatible with h323plus 1.21.0. I then tried Ptlib 2.6.6 which compiled with h323plus 1.21.0, but Asterisk still gave the 'BOOL' make error. I then moved forward to finding and replacing in the Asterisk code. Globally replacing the code didn't work, but finding and replacing just 'channels/h323/ast_h323.cxx' & 'channels/h323/ast_h323.h' seemed to do the trick. [root@localhost asterisk]# ldd /usr/lib/asterisk/modules/chan_h323.so libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ab1fd5db000) libm.so.6 => /lib64/libm.so.6 (0x00002ab1fd8db000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ab1fdb5e000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ab1fdd6d000) libc.so.6 => /lib64/libc.so.6 (0x00002ab1fdf88000) /lib64/ld-linux-x86-64.so.2 (0x00000039bf200000) J From: Simon Horne [mailto:s.horne@packetizer.com] Sent: Monday, November 16, 2009 01:26 PM To: Mark Best Subject: RE: [h323plus] ast_h323.h:104: error: 'BOOL' has not been declared Mark do a global replace of BOOL with PBoolean. Simon ________________________________ From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Mark Best Sent: Tuesday, 17 November 2009 6:30 AM To: h323plus(a)lists.packetizer.com Subject: [h323plus] ast_h323.h:104: error: 'BOOL' has not been declared I'm trying to compile chan_h323 for Asterisk, I only get an error when I start the make on Asterisk. Can someone shed some light on this issue? (CentOS 5.4 x64) Here are my notes: yum -y install ncurses ncurses-devel openssl openssl-devel zlib zlib-devel bison bison-devel glibc gcc kernel-devel flex yum install gcc-c++ cd /usr/src wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-1.6.0.17.t ar.gz wget http://www.h323plus.org/source/download/h323plus-v1_21_0.tar.gz wget http://www.h323plus.org/source/download/ptlib-2.4.5.tar.bz2 tar zxvf asterisk-1.6.0.17.tar.gz mv asterisk-1.6.0.17/ ~/asterisk tar zxvf h323plus-v1_21_0.tar.gz bzip2 -cd ptlib-2.4.5.tar.bz2 | tar xvf - mv h323plus ~/h323plus mv ptlib-2.4.5 ~/ptlib export PTLIBDIR=$HOME/ptlib export OPENH323DIR=$HOME/h323plus export LD_LIBRARY_PATH=$OPENH323DIR/lib:$PTLIBDIR/lib cd $PTLIBDIR ./configure --prefix=/usr make make install cd $OPENH323DIR chmod +x configure ./configure --prefix=/usr make make opt cd lib cp libh323_linux_x86_64_.so.1.21-beta0 libh323_linux_x86_64_.so.1.21.0 cd .. make install cd ~/asterisk ./configure --prefix=/usr make menuselect [*] chan_h323 make [CC] chan_agent.c -> chan_agent.o [LD] chan_agent.o -> chan_agent.so [CC] chan_h323.c -> chan_h323.o ast_h323.h:104: error: 'BOOL' has not been declared ast_h323.h:156: error: 'BOOL' does not name a type ast_h323.h:157: error: 'BOOL' does not name a type ast_h323.h:159: error: 'BOOL' does not name a type ast_h323.cxx:2102: error: prototype for 'void MyH323Connection::MyHoldCall(PBoolean)' does not match any in class 'MyH323Connection' ast_h323.h:104: error: candidate is: void MyH323Connection::MyHoldCall(int) ast_h323.cxx:2370: error: 'BOOL' does not name a type ast_h323.cxx:2376: error: 'BOOL' does not name a type ast_h323.cxx:2387: error: 'BOOL' does not name a type make[2]: *** [ast_h323.o] Error 1 make[1]: *** [h323/libchanh323.a] Error 2 make: *** [channels] Error 2

1 0

ast_h323.h:104: error: 'BOOL' has not been declared
by Mark Best 16 Nov '09

16 Nov '09

I'm trying to compile chan_h323 for Asterisk, I only get an error when I start the make on Asterisk. Can someone shed some light on this issue? (CentOS 5.4 x64) Here are my notes: yum -y install ncurses ncurses-devel openssl openssl-devel zlib zlib-devel bison bison-devel glibc gcc kernel-devel flex yum install gcc-c++ cd /usr/src wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-1.6.0.17.t ar.gz wget http://www.h323plus.org/source/download/h323plus-v1_21_0.tar.gz wget http://www.h323plus.org/source/download/ptlib-2.4.5.tar.bz2 tar zxvf asterisk-1.6.0.17.tar.gz mv asterisk-1.6.0.17/ ~/asterisk tar zxvf h323plus-v1_21_0.tar.gz bzip2 -cd ptlib-2.4.5.tar.bz2 | tar xvf - mv h323plus ~/h323plus mv ptlib-2.4.5 ~/ptlib export PTLIBDIR=$HOME/ptlib export OPENH323DIR=$HOME/h323plus export LD_LIBRARY_PATH=$OPENH323DIR/lib:$PTLIBDIR/lib cd $PTLIBDIR ./configure --prefix=/usr make make install cd $OPENH323DIR chmod +x configure ./configure --prefix=/usr make make opt cd lib cp libh323_linux_x86_64_.so.1.21-beta0 libh323_linux_x86_64_.so.1.21.0 cd .. make install cd ~/asterisk ./configure --prefix=/usr make menuselect [*] chan_h323 make [CC] chan_agent.c -> chan_agent.o [LD] chan_agent.o -> chan_agent.so [CC] chan_h323.c -> chan_h323.o ast_h323.h:104: error: 'BOOL' has not been declared ast_h323.h:156: error: 'BOOL' does not name a type ast_h323.h:157: error: 'BOOL' does not name a type ast_h323.h:159: error: 'BOOL' does not name a type ast_h323.cxx:2102: error: prototype for 'void MyH323Connection::MyHoldCall(PBoolean)' does not match any in class 'MyH323Connection' ast_h323.h:104: error: candidate is: void MyH323Connection::MyHoldCall(int) ast_h323.cxx:2370: error: 'BOOL' does not name a type ast_h323.cxx:2376: error: 'BOOL' does not name a type ast_h323.cxx:2387: error: 'BOOL' does not name a type make[2]: *** [ast_h323.o] Error 1 make[1]: *** [h323/libchanh323.a] Error 2 make: *** [channels] Error 2

1 0

H323plus v 1.22 and ptlib 2.6.5
by Sebastian Peschko 13 Nov '09

13 Nov '09

I wonder if someone can help out here. I am having trouble with Asterisk Crashes caused by libpt and openh323 where I am using Asterisk 1.6.2rc5 and h323plus v1.19.0Beta7 and ptlib v1.12.0. In this config when compiling the 2 packages and then doing a make in the asterisk H323 directory it automatically activates the chan_h323 in the Menuselect options of Asterisk and allows me to compile asterisk with h323plus support. The problem I am having is that I am registering with a Nortel H323 GateKeeper and when this looses the registry for some or other reason as a backup I send the calls using a Gateway directly to the Nortel PBX. With this configuration in v1.4.23 it was working perfecttly with openh323 v1.18.0 and pwlib v1.10.3. The problem came when because of issues with openmfcr2 I needed to upgrade to 1.6 for the embedded openr2 support. For this reason I am no trying to compile Asterisk 1.6.2.0rc5 with the latest h323plus v1.22.0 and ptlib 2.6.5. At the moment once these 2 packages are compiled it does not allow me to activate or select chan_h323 in the Asterisk "make menuselect". How can this be activated? I hope someone can help. Sebastian

3 5

H.323v7 and H.460.23/.24 approved by the ITU
by Simon Horne 09 Nov '09

09 Nov '09

Guys Just a quick note. http://www.packetizer.com/ipmc/h323/whatsnew_v7.html It has been nearly 3 years from my first submission to final approval on H.460.23/.24 but finally it's done. H.323 now has a standard complete NAT traversal solution. Simon

2 1

simph323 - could not open sound device
by mattes 07 Nov '09

07 Nov '09

I am trying to get simph323 to work, but I having some trouble w/ the audio. Running h323plus-v1_21_0 with ptlib-2.4.5 on Linux. I run the following command: simph323 -s "HDA Intel" -n h323:192.168.15.163 H323> Could not open sound device HDA Intel - Check permissions or full duplex capability. Could not open sound device HDA Intel - Check permissions or full duplex capability. In call with Kattanekm Could not open sound device HDA Intel - Check permissions or full duplex capability. Could not open sound device HDA Intel - Check permissions or full duplex capability. .... running with trace enabled shows that the sound device is opened properly, but then it fails shortly after 0:04.512 H245:b7e3db90 H245 Default OnSelectLogicalChannels, FastStartDisabled 0:04.512 H245:b7e3db90 H323 FindCapability: G.711-ALaw-64k <1> 0:04.512 H245:b7e3db90 H323 Found capability: G.711-ALaw-64k <4> 0:04.513 H245:b7e3db90 H323 Selecting G.711-ALaw-64k <4> 0:04.513 H245:b7e3db90 H245 Opening channel: T-103 0:04.513 H245:b7e3db90 PWLib File handle low water mark set: 17 PUDPSocket 0:04.514 H245:b7e3db90 RTP_UDP Session 1 created: 192.168.15.153:5002-5003 ssrc=2757625043 0:04.514 H245:b7e3db90 RTP Adding session RTP_UDP 0:04.514 H245:b7e3db90 H323RTP Transmitter created using session 1 0:04.514 H245:b7e3db90 H323RTP OnSendingPDU 0:04.514 H245:b7e3db90 RTP OnSendingPDU 0:04.514 H245:b7e3db90 Codec G711 ALaw encoder created for at 64k, 240 samples 0:04.515 H245:b7e3db90 ALSA Open this=0x0x9627ea8 0:04.517 H245:b7e3db90 Alsa Buffer time is 85312 0:04.517 H245:b7e3db90 Alsa Period time is 85312 0:04.519 H245:b7e3db90 ALSA Device plughw:0 Opened 0:04.519 H245:b7e3db90 Codec Opened sound channel "HDA Intel" for recording at 8000 samples/second using 2x480 byte buffers. 0:04.519 H245:b7e3db90 ALSA setBuffers this=0x0x9627ea8 oshandle=0x9626698 init 1 0:04.519 H245:b7e3db90 psound isOPen basechannel 0x0x9627ea8 pchannel os_handle=-1 0:04.519 H245:b7e3db90 Codec channel 0x0x96243a8 isOpen=0 Could not open sound device HDA Intel - Check permissions or full duplex capability. 0:04.519 H245:b7e3db90 LogChan Transmit thread aborted (open fail) for G.711-ALaw-64k <4> 0:04.519 H245:b7e3db90 H323 OnSelectLogicalChannels, OpenLogicalChannel failed: G.711-ALaw-64k <4> Some debugging later I noticed that H323EndPoint::OpenAudioChannel() calls codec.AttachChannel() [codecs.cxx] and fails in channel->IsOpen(). Looking at ptlib/common/sound.cxx PSoundChannel it is baseChannel->PChannel::IsOpen() which returns FALSE For a quick test I changed the line to baseChannel->IsOpen() which makes it jump that hurdle and simph323 connects with the other h323 end and sound bits are exchanged. Here is the thing that puzzles me! I am using the same version of ptlib with opal (e.g. simpleopal) and don't see this problem. Code is build and run on the same machine. Any thoughts? mat

1 0