[Asterisk-video] (no subject)

Nico Gundacker nico.gundacker at dynetic.de
Wed Apr 30 08:46:40 CDT 2008


Here is the capture that I took with wireshark. The initiation seems to be
fine and at package-line 51 you will find the first h263-1998 package. Note:
192.168.100.225 is the asterisk location and 192.168.100.100 is the
sip-client-location. 


No.     Time        Source                Destination           Protocol
Info
     28 9.212562    192.168.100.100       192.168.100.225       SIP/SDP
Request: INVITE sip:204 at 192.168.100.225, with session description
     29 9.220217    192.168.100.225       192.168.100.100       SIP
Status: 407 Proxy Authentication Required
     30 9.220598    192.168.100.100       192.168.100.225       SIP
Request: ACK sip:204 at 192.168.100.225
     31 9.220809    192.168.100.100       192.168.100.225       SIP/SDP
Request: INVITE sip:204 at 192.168.100.225, with session description
     32 9.222617    192.168.100.225       192.168.100.100       SIP
Status: 100 Trying
     33 9.223352    192.168.100.225       192.168.100.100       SSH
Encrypted response packet len=212
     34 9.223930    192.168.100.225       192.168.100.100       SIP/SDP
Status: 200 OK, with session description
     35 9.223938    192.168.100.225       192.168.100.100       SSH
Encrypted response packet len=228
     36 9.223943    192.168.100.225       192.168.100.100       SSH
Encrypted response packet len=68
     37 9.223955    192.168.100.100       192.168.100.225       TCP
pwrsevent > ssh [ACK] Seq=1 Ack=509 Win=65027 [TCP CHECKSUM INCORRECT] Len=0
     38 9.226188    192.168.100.225       192.168.100.100       SSH
Encrypted response packet len=68
     39 9.227649    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40739, Time=160 
     40 9.227796    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40740, Time=320 
     41 9.227903    192.168.100.100       192.168.100.225       RTCP
Receiver Report   Source description   
     42 9.227982    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40741, Time=480 
     43 9.227988    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40742, Time=640 
     44 9.228005    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40743, Time=800 
     45 9.228105    192.168.100.100       192.168.100.225       RTCP
Receiver Report   Source description   
     46 9.228263    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40744, Time=960 
     47 9.228268    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40745, Time=1120 
     48 9.228270    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40746, Time=1280 
     49 9.228361    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40747, Time=1440 
     50 9.228453    192.168.100.225       192.168.100.100       RTP
PT=ITU-T G.711 PCMU, SSRC=0x5F709ADC, Seq=40748, Time=1600 
     51 9.229151    192.168.100.225       192.168.100.100       H.263
RFC4629  PT=H263-1998, SSRC=0xBE31207, Seq=11748, Time=1710, Mark 
     52 9.229591    192.168.100.225       192.168.100.100       SSH
Encrypted response packet len=1172
     53 9.229601    192.168.100.100       192.168.100.225       TCP
pwrsevent > ssh [ACK] Seq=1 Ack=1749 Win=65535 [TCP CHECKSUM INCORRECT]
Len=0

----------------------------------------------------------------------------
---------------

HERE IS THE CONTENT OF THE PACKAGE FROM LINE NUMBER 51

Frame 51 (755 bytes on wire, 755 bytes captured)
Ethernet II, Src: Vmware_c8:e5:9a (00:0c:29:c8:e5:9a), Dst: Dell_f4:60:c0
(00:1e:4f:f4:60:c0)
Internet Protocol, Src: 192.168.100.225 (192.168.100.225), Dst:
192.168.100.100 (192.168.100.100)
User Datagram Protocol, Src Port: 18250 (18250), Dst Port: 64686 (64686)
Real-Time Transport Protocol
    [Stream setup by SDP (frame 31)]
    10.. .... = Version: RFC 1889 Version (2)
    ..0. .... = Padding: False
    ...0 .... = Extension: False
    .... 0000 = Contributing source identifiers count: 0
    1... .... = Marker: True
    Payload type: H263-1998 (115)
    Sequence number: 11748
    [Extended sequence number: 77284]
    Timestamp: 1710
    Synchronization Source identifier: 0x0be31207 (199430663)
ITU-T Recommendation H.263 RTP Payload header (RFC4629)
    0000 0... .... .... = Reserved: 0
    .... .1.. .... .... = P: True
    .... ..0. .... .... = V: False
    .... ...0 0000 0... = PLEN: 0
    .... .... .... ..00 = PEBIT: 0
    H.263 RFC4629 payload
        1000 00.. = H.263 Picture start Code: 0x20
        .... ..00  0000 00.. = H.263 Temporal Reference: 0
        0... .... = H.263 Split screen indicator: Off
        .0.. .... = H.263 Document camera indicator: Off
        ..0. .... = H.263 Full Picture Freeze Release: Off
        ...0 10.. = H.263 Source Format: QCIF 176x144 (2)
        .... ..0. = H.263 Picture Coding Type: INTRA (I-picture)
        .... ...0 = H.263 Optional Unrestricted Motion Vector mode: Off
        0... .... = H.263 Optional Syntax-based Arithmetic Coding mode: Off
        .0.. .... = H.263 Optional Advanced Prediction mode: Off
        ..0. .... = H.263 Optional PB-frames mode: Normal I- or P-picture
        ...0 1001 = H.263 Quantizer Information (PQUANT): 9
        0... .... = H.263 Continuous Presence Multipoint and Video Multiplex
(CPM): Off
        .0.. .... = H.263 Extra Insertion Information (PEI): 0

----------------------------------------------------------------------------
-----------------------------------------

HERE IS THE ANALIZING FROM THE ASTERISK WHEN USING THE FOLLOWING COMMNAND:
rtp debug ip 192.168.100.100
...............
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006115, ts
1562080, len 000160)
Sent RTP packet to      192.168.100.100:56818 (type 115, seq 061689, ts
038751, len 000020)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006116, ts
1562240, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006117, ts
1562400, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006118, ts
1562560, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006119, ts
1562720, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006120, ts
1562880, len 000160)
Got  RTP packet from    192.168.100.100:56818 (type 126, seq 003057, ts
000000, len 000004)
[Apr 30 06:32:15] NOTICE[2199]: rtp.c:1287 ast_rtp_read: Unknown RTP codec
126 received from '192.168.100.100'
Got  RTP packet from    192.168.100.100:56818 (type 126, seq 003057, ts
000000, len 000004)
[Apr 30 06:32:15] NOTICE[2199]: rtp.c:1287 ast_rtp_read: Unknown RTP codec
126 received from '192.168.100.100'
Got  RTP packet from    192.168.100.100:56818 (type 126, seq 003057, ts
000000, len 000004)
[Apr 30 06:32:15] NOTICE[2199]: rtp.c:1287 ast_rtp_read: Unknown RTP codec
126 received from '192.168.100.100'
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006121, ts
1563040, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006122, ts
1563200, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006123, ts
1563360, len 000160)
Sent RTP packet to      192.168.100.100:56818 (type 115, seq 061690, ts
051609, len 000020)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006124, ts
1563520, len 000160)
Got  RTP packet from    192.168.100.100:43884 (type 00, seq 006125, ts
1563680, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044145, ts
009312, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044146, ts
009472, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044147, ts
009632, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044148, ts
009792, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044149, ts
009952, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044150, ts
010112, len 000160)
Sent RTP packet to      192.168.100.100:43884 (type 00, seq 044151, ts
010272, len 000160)
..........



Regards Nico

-----Ursprüngliche Nachricht-----
Von: asterisk-video-bounces at lists.digium.com
[mailto:asterisk-video-bounces at lists.digium.com] Im Auftrag von Klaus
Darilion
Gesendet: Mittwoch, 30. April 2008 15:05
An: Development discussion of video media support in Asterisk
Betreff: Re: [Asterisk-video] (no subject)



Nico Gundacker schrieb:
> Here is a part of what eyebeam is logging. I do not know how to check the
> sending of RTP in any other way, except using some special
> package-analyzing-software, which is analyzing the hole traffic at the
> network.

Use wireshark. Get the RTP ports for audio and video from the SDP of the 
INVITE and 200 OK. Then check if there are RTP packets sent to/from the 
UDP ports used for the video stream.

regards
klaus


> 
> [08-04-30]09:14:00.624 | Info | Conferencing | "Receiving video frame on
> stream 00000047" | sua::CVideoConferencingManager::OnIncomingVideoFrame
> [08-04-30]09:14:00.624 | Warning | Conferencing | "Unable to locate stream
> 71" | sua::CVideoConferencingManager::OnIncomingVideoFrame
> [08-04-30]09:14:00.624 | Debug | Video | "Drawing I420 secondary surface"
|
> sua::CDirectXVideoFrameRenderer::DrawI420orIYUVSurface
> [08-04-30]09:14:00.624 | Debug | Video | "Result of blit to primary
surface
> is 0" | sua::CDirectXVideoFrameRenderer::BlitImageToPrimarySurface
> [08-04-30]09:14:00.625 | Debug | Jitter | "Packet hold time is: 41 avg
> latency: 38.9856 seq: 45686" | sua::CJitterBuffer::DeliverPacket
> [08-04-30]09:14:00.625 | Info | Audio | "Adding 160 samples to latency
> reducer" | sua::CAudioManager::DeliverIncomingData
> 
> -----Ursprüngliche Nachricht-----
> Von: asterisk-video-bounces at lists.digium.com
> [mailto:asterisk-video-bounces at lists.digium.com] Im Auftrag von Klaus
> Darilion
> Gesendet: Dienstag, 29. April 2008 16:40
> An: Development discussion of video media support in Asterisk
> Betreff: Re: [Asterisk-video] (no subject)
> 
> Nico Gundacker wrote:
>> You are right, when I use express-talk with the same videos there are no
>> such error-reports as there are shown with x-lite. But still there is no
>> video shown on both sip-phones.
> 
> Does Asterisk send video RTP packets to the SIP client?
> 
> regards
> klaus
> 
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-video mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-video
> 
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-video mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-video

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

asterisk-video mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-video




More information about the asterisk-video mailing list