At 01:34 PM 10/5/2004, Franklin, Allen wrote:
Can I use the app server functionality of SER to initiate a SIP call?
In order to initiate a SIP call, the app needs to be able to specify RTP parameters to go into SDP bodies of SIP messages, and to have access to the SDP info returned by the callee.
Some entity (SER or the app?) needs to do SDP negotiation.
I don't see mention of this in the SER docs.
Am I asking for something that SER does not support?
Yes. SER is a proxy server -- it cannot initiate calls. Only a B2BUA such as AA can.
-jiri
-----Original Message----- From: Jiri Kuthan [mailto:jiri@iptel.org] Sent: Monday, October 04, 2004 7:11 PM To: Franklin, Allen; serusers@lists.iptel.org Subject: Re: [Serusers] Summary of using SER as an app server
At 12:51 AM 10/5/2004, Franklin, Allen wrote:
A very basic hook is provided that allows a script to call functions in a user-provided shared library, but this hook is only useful for rewriting the URI of the "current" message.
Thats incorrect. The shlibs can do and do much more than URI rewriting. See module list and what they do.
SER does not allow scripts or app server processes to see or modify the SDP, so an app server process could not be used to initiate a voice call.
There are modules that do SDP mangling. nathelper for example.
SER does not have a SIP parser as would be found in a traditional SIP stack.
I don't know what a traditional SIP stack is but if you mean something slow that SER doesn't have it ;) It is not available as a separate library if you mean that.
Otherwise your assessment has been correct. If you are looking for a real application server (meaning a stateful call control element) than it is not SER. We have AA (www.iptel.org/aa).
-jiri
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Jiri Kuthan wrote:
At 01:34 PM 10/5/2004, Franklin, Allen wrote:
Can I use the app server functionality of SER to initiate a SIP call?
In order to initiate a SIP call, the app needs to be able to specify RTP parameters to go into SDP bodies of SIP messages, and to have access to the SDP info returned by the callee.
Some entity (SER or the app?) needs to do SDP negotiation.
I don't see mention of this in the SER docs.
Am I asking for something that SER does not support?
Yes. SER is a proxy server -- it cannot initiate calls. Only a B2BUA such as AA can.
or any other application behind ser which uses ser's SIP stack via the FIFO. e.g. the click-to-dial or IM-send application in serweb.
klaus
Thanks for reminding me -- that's indeed an aproach which, if appplicable, I like better. No call state, much more end-2-end. Initiating a call by a B2BUA has quite some issues (ringing to name at least some).
-jiri
At 12:01 AM 10/6/2004, Klaus Darilion wrote:
or any other application behind ser which uses ser's SIP stack via the FIFO. e.g. the click-to-dial or IM-send application in serweb.
klaus
-- Jiri Kuthan http://iptel.org/~jiri/
-
Jiri Kuthan -
Klaus Darilion