Hello,

o [email protected] [02/17/09 05:09]:
Hi,

Often, we I start multiple outbound sessions at about the same time,
one of the sessions will connect, but then have something go wrong
with the transmission of RTP audio.  The problem begins when my
onSessionStart() queues a item on an AmPlaylist, which is attached to
the session's output channel.  From the session's point of view, it
appears that the item never plays, because the session never gets a
completion message from the playlist. In the sems log, I also see the
following error, which seems to suggest that something is going wrong
with transmission of the RTP packets.

ERROR: [afff4b90] send (AmRtpPacket.cpp:212): while sending RTP packet: 
Operation not permitted
usually you get this error back from the stack if you try to send against some firewall rule. I would try turning off the firewall and see whether you run into the same error.

Alternatively, try waiting a few milliseconds in between the calls.


If my program retries the same call a minute or so later, everything
works fine.  Also, when one session fails, there could be as many as
ten other sessions active at the same time that work fine.  All of
these sessions are running exactly the same code, the only difference
being that they are connecting to different URIs.

Anyone know what might be cause the RTP error?

Reading the AmSession code, it appears that the audio channel doesn't
get completely set up until after my onSessionStart() is called.
Should I delay starting any audio output until a later point in the
startup sequence?
no, this is the preferred place to start audio output. If you connect input/output in onSessionStart, it will add the session to media processing thus start sending RTP.

Stefan



--
Stefan Sayer
VoIP Services

[email protected]
www.iptego.com

IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany

Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to