18 Apr
2008
18 Apr
'08
2:28 p.m.
hmmm, it might be an option to implement this uaCSTA functionality in * but
anyways i need openSER in my architecture, as this SIP/CSTA messages from
OCS are sent via TCP (or TLS) and my * box (v1.2.x) doesn't understand this
transport protocol(s).
on the other hand if this module is implemented in openSER it may be
re-usable with other configurations...
well i see that this uaCSTA is currently not supported in openSER, so i'll
have to decide which way i wanna go (e.g. implement an own OCS_CTI module
for openSER, thinking about an asterisk solution, ...)
thx & cheers
-hugo
-----Original Message-----
From: Juha Heinanen [mailto:jh@tutpro.com]
Sent: Friday, April 18, 2008 11:09 AM
To: Hugo Koblmueller
Cc: users(a)lists.openser.org
Subject: RE: [OpenSER-Users] uaCSTA support in openser
Hugo Koblmueller writes:
my goal is now to establish this telephony link to *.
but as * doesn't >
understand SIP/CSTA, i thought of a box (e.g. my openSER
box) which can do
this uaCSTA to SIP translation.
looks to me like a problem in pbx space, i.e., since new code is required,
it would be better to write it in asterisk. that would eliminate need for
one more translating box from the architecture. i would see openser's role
as upstream proxy for OCS mediation server (if it speaks standard SIP to
outside).
-- juha