oops, sorry about that, i didn't mean to. :( i'm speaking about the integration of asterisk with microsoft's offics communication server (OCS) 2007, which itself speaks the CSTA (computer supported telecommunications application) standard (phase III) to communication internally to it's components (like the office communicator 2007, which is the an IM softphone application, or to the OCS mediation server, which is a kind of SIP/CSTA gateway to the outside world). for the computer telephony integration (CTI) of the OCS it is mandatory to speak this CSTA language. This language was standardized by the ECMA, the european computer manufacturers association, for implementing computer supported telecom applications via XML (also EMCA-323 - http://www.ecma-international.org/publications/standards/Ecma-323.htm). now the uaCSTA (user agent CSTA) is kind of a subset of the CSTA XML language, which is mainly used for observing and controlling voice and non-voice media calls, and is defined in EMCA TR/87 (http://www.ecma-international.org/publications/techreports/E-TR-087.htm). as CSTA XML only specifies only the XML protocol itself, uaCSTA is implementing this XML protocol via SIP messages, using only the two SIP message types INVITE and INFO. the XML payload itself is transported in the SIP message body. so now what i'm looking for is a module (or a perl script) which understands uaCSTA (aka. CSTA XML over SIP) or at least the subset the OCS is using and can translate it into standard SIP messages and vice versa, as this is needed to implement the CTI integration for OCS 2007. hope this clarifies my intention... cheers -hugo -----Original Message----- From: Juha Heinanen [mailto:jh@tutpro.com] Sent: Friday, April 18, 2008 9:10 AM To: Hugo Koblmueller Cc: users(a)lists.openser.org Subject: [OpenSER-Users] uaCSTA support in openser Hugo Koblmueller writes: huh, your email was full of acronyms i have never heard. -- juha

well on the microsoft side we have the two main scenarios which interact not only in MS environment: - one is the softphone integration, where office communicator acts as single user agent (having its own phonenumber). in this case all the SIP traffic is routed to this OCS mediation server to communicate with the 'outer' (non-MS) world using the OCS mediation server as gateway. - the other scenario is CTI, which means one phonenumber can either be routed to your office communicator client or to any hardphone connected to your pbx (which is in my case *). this has also the effect, that if for example i setup a call on my mobile the office communicator is informed about that to indicate in its presence indications, that i'm in a call. or for example you wanna setup a call by just clicking on one of your outlook contacts (click-to-call) but you want to use your deskphone (e.g. you wanna use your deskphone-headset). this just clicking on your outlook contact triggers an INVITE event letting your deskphone ring. when you pick up the receiver the call is issued to your callee. in this second scenario the SIP/CSTA traffic coming from OCS is not routed to the OCS mediation server but to a kind of external server which controls the telephony integration something like the siemens TCL (telephony control link) server. 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. cheers -hugo -----Original Message----- From: Juha Heinanen [mailto:jh@tutpro.com] Sent: Friday, April 18, 2008 10:11 AM To: Hugo Koblmueller Cc: users(a)lists.openser.org Subject: RE: [OpenSER-Users] uaCSTA support in openser Hugo Koblmueller writes: understands > uaCSTA (aka. CSTA XML over SIP) or at least the subset the OCS is using and > can translate it into standard SIP messages and vice versa, as this is > needed to implement the CTI integration for OCS 2007. a question: why does openser need to map CSTA XML over SIP to SIP if microsoft OCS mediation server already exists that gateways CSTA to SIP? -- juha

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: 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

well this is definitely worth to think about... thx for the input! cheers -hugo -----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Friday, April 18, 2008 1:08 PM To: Juha Heinanen Cc: Hugo Koblmueller; users(a)lists.openser.org Subject: Re: [OpenSER-Users] uaCSTA support in openser Juha Heinanen schrieb: I think this is the better approach. I have no clue about CSTA about to me it sounds like having an CSTA<->AMI (Asterisk Manager Interface) would be the way to go. As openser is not dialog stateful, you can not send the status of the SIP clients to the OCS - as openser does not know. Again, as Asterisk is dialog statefull, Asterisk can. regards klaus

18 apr 2008 kl. 11.09 skrev Juha Heinanen: I would be very interested to see how Asterisk's AMI matches up to CSTA. Where can I find the specs? /O