Answer’s inline…
From:
resiprocate-users-bounces@xxxxxxxxxxxxxxx
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Sumana
Mitra
Sent: Friday, June 06, 2008 12:40 AM
To: resiprocate-users@xxxxxxxxxxxxxxx
Cc: avnish.tyagi@xxxxxxx; Sn Shylaja
Subject: [reSIProcate-users] Regarding ReSIProcate integration with
Thirdparty RTP media stack
Dear All,
We are planning
to use Conversation Manager for our application development. Our system will
use DSP boards to have RTP connectivity with other end.
These DSP
boards have ethernet interfaces. We need to integrate ReSIProcate with this RTP
stack.
Please address
following queries regarding integration:
1. Is it
a good idea to use Conversation Manager for this implementation?
[Scott] Without know anything about your application it’s
hard to tell – but I suspect it will be a good place for you start with
resiprocate. How many simultaneous SIP sessions would you need to support?
2. Which
component should we use to deal with SDP?
[Scott] There are a two options:
1.
You could continue to use just the sipXsdp (that will also
require sipXport) from the sipXtapi project.
2.
You could rewrite the SDP handling code by building equivalent
SDP containers using resiprocate like containers – this would mean you
could eliminate sipXtapi project entirely.
3. What
feature does sipXtapi provides to Conversation Manager?
[Scott] I’ve added this info to a new wiki page that I’m
currently working on: http://www.resiprocate.org/Recon_Overview#What_is_sipXtapi.3F
The wiki page is still a work in progress.
4. Please
tell us the components we need to concentrate on to integrate ReSIProcate with
our RTP.
[Scott] If you read the readme.txt in the recon directory there
are some pointers about this there. Look at the TODO list. https://svn.resiprocate.org/viewsvn/resiprocate/main/resip/recon/readme.txt?view=markup
Good luck!
Scott
Thanks &
Regards,
Sumana Mitra
Mailto: sumana.mitra@xxxxxxx
Website: http://www.tcs.com
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you