Open GoogleCodeExporter opened 9 years ago
If you start siprtmp.py with -d option you can see the debug trace. Was there
any exception in the trace?
I guess one reason could be that if siprtmp detects that a stream name is
already publishing, it will not allow a new publish for the same stream name,
and prints a message about it in debug mode.
This issue is not relevant if you cleanup the NetConnection after a call, since
all streams are cleanup after connection is closed.
I think if you can send the debug trace it will be more useful in identifying
the problem.
Thanks
Original comment by kundan10
on 30 Sep 2011 at 9:37
Original issue reported on code.google.com by
eag...@gmail.com
on 30 Sep 2011 at 3:14Attachments: