Results 1 to 10 of 10

Thread: Multicasting stream creating error

  1. #1

    Question Multicasting stream creating error

    Hi,

    Previously in my system, I was receiving a (mpeg2) multicast stream as: for address 224.120.120.101 and 7000 port:

    tcpdump -i eth1 dst host 224.120.120.101 used to show.

    07:03:15.612887 IP 10.120.120.20.afs3-fileserver > 224.120.120.101.afs3-fileserver: rx type 231 (1316)
    07:03:15.613589 IP 10.120.120.20.afs3-fileserver > 224.120.120.101.afs3-fileserver: rx type 61 (1316)
    07:03:15.614291 IP 10.120.120.20.afs3-fileserver > 224.120.120.101.afs3-fileserver: rx type 51 (1316)
    07:03:15.614993 IP 10.120.120.20.afs3-fileserver > 224.120.120.101.afs3-fileserver: rx type 0 (1316)
    07:03:15.615695 IP 10.120.120.20.afs3-fileserver > 224.120.120.101.afs3-fileserver: rx type 14 (1316)

    Now this stream is no more available, and we have a new stream (H.264) for ip 224.111.111.100 and 5000 port

    tcpdump -i eth1 dst host 224.111.111.100 shows

    06:11:03.319492 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.319744 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.319978 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.320198 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.320479 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.320701 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.320975 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.321228 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.321493 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.321834 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.322096 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.322383 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.322591 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316
    06:11:03.322884 IP 192.168.1.11.filenet-tms > 224.111.111.100.commplex-main: UDP, length 1316


    both are being injected at eth1. in My VHost the config is same which is:

    <MulticastBindToAddress>true</MulticastBindToAddress>
    <MulticastInterfaceAddress>10.120.120.10</MulticastInterfaceAddress>

    where 10.120.120.10 is ip of eth1.

    But now, with the new stream it is throwing error saying:

    ERROR server comment 2013-06-06 06:06:28 - - - - - 61.835 - - - - - - - - RTPMulticastListener.unbind: java.net.SocketException: Cannot assign requested address


    What could be the reason?

    Thanks in Advance
    Birendra

  2. #2

    Default

    The later stream is a Unicast stream, Is there different way for unicast stream?

    Thanks,
    Birendra

  3. #3
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Take a look at the port sharing article:

    http://www.wowza.com/forums/content....and-multicast)

    Also, please don't open multiple threads with the same issue.

    Richard

  4. #4

    Default

    Quote Originally Posted by rrlanham View Post
    Take a look at the port sharing article:

    http://www.wowza.com/forums/content....and-multicast)

    Also, please don't open multiple threads with the same issue.

    Richard
    Hi Richard,

    I have already enabled UDP port sharing. Still I am recei
    ERROR server comment 2013-06-06 08:28:51 - - - - - 153.135 - - - - - -- - RTPMulticastListener.unbind: java.net.SocketException: Cannot assign requested address


    Further regarding the stream, I have these info:



    Thanks,
    Birendra
    Last edited by dhamibirendra; 06-06-2013 at 05:54 AM.

  5. #5
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Is a set of RTPMulticastListener.bind messages followed immediately by RTPMulticastListener.unbind messages with no firstpacket message in between? It might just be udp ports are not open in your firewall or mapped in your network.

    Otherwise, do a short test and send to support. First restart Wowza. Then test to reproduce this. Then zip up /conf and current access log showing above re-start and test to support@wowza.com

    Richard

  6. #6
    Join Date
    Dec 2007
    Posts
    21,962

  7. #7

    Default

    Hi Richard,

    The udp ports are open.

    [root@localhost logs]# iptables -n -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
    ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0
    ACCEPT all -- 0.0.0.0/0 0.0.0.0/0
    ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2288
    ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:1935
    ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8086
    ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8084
    ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:8085
    ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:5000
    ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0
    ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:5000
    ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:7000
    REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination
    REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination

    For new stream, I have set my .stream file as:
    udp://224.111.111.100:5000?audioPID=0x1b1&videoPID=0x1b0

    Am I missing something?
    Or shall I post it to support@wowza.com

    Thanks

  8. #8
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Yes, please open a support ticket. This might be related to a problem we are working on regarding mpeg-ts streams.

    Did you just upgrade to 3.6.1?

    Richard

  9. #9

    Default

    Hi Richard,

    I have opened the ticked.

    I had upgraded the wowza with

    http://www.wowza.com/downloads/Wowza....x.x-3.6.1.zip

    Even after the patch, it was working with older stream.

    Also, the new stream is H.264 not MPEG2.

    Thanks,
    Birendra

  10. #10
    Join Date
    Dec 2007
    Posts
    21,962

    Default

    Sorry, Birendra, Check the ticket for another update.

    Richard

Similar Threads

  1. Error creating <ServerListener>
    By papiandy in forum General Forum
    Replies: 9
    Last Post: 05-10-2013, 07:52 PM
  2. Error creating snapshot of stream
    By DWBN Streaming in forum AddOn: Transcoder
    Replies: 7
    Last Post: 08-13-2012, 04:23 AM
  3. Replies: 3
    Last Post: 11-23-2011, 08:32 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •