Friends,
He/she would like to know somebody already did integration of OCS of Microsoft with OXE.
The customer requests the possibility of the following situation: it was made the integration with the product, on top of trunk SIP.
So that I can call OXE for OCS an access was created the route specifies where I type him/it number the extension OCS.
He would like that, for instance, if I call of I/you had gone for I number published him/it of an extension of OXE, be made an immediate deviation for the extension of OCS, but the identification of the call he would not like him to appear the key trunk of OXE and yes I number him/it external that this calling.
Is that programming possible?
Which the procedure?
Integration Microsoft OCS with OXE
-
banfield
I'm not sure I understand your exact question. I will give you some possible OXE - OCS connections:
1) An OXE can be connected to an OCS environment, using a SIP trunk.
The SIP trunk is connected to a MS Mediation server.
It's possible to call from an OCS client to an OXE user and visa versa.
OCS clients can make outgoing calls through the OXE.
OCS clients can receive incoming calls though the OXE.
So no integration, but just a connection of two pbx systems.
2) OXE - OCS integration, using MyIC
The integration with MyIC and OCS will only work dor OCS R1 clients (ALU is working on a R2 connector).
A user will have two clients installed on their pc. These clients share e.g. presence information.
OCS can be used for presence and IM, while MyIC is used for making phone calls.
advantage of this solution that a My IC user can benefit of all OXE features.
3) OXE - OCS integration, using GETS
GETS will give you a CSTA based integration.
CSTA messages can be used to have remote call-control from the OCS client.
A user can dial a phonenumber from his OCS client and his physical phone will receive csta messages to call this number.
An advantage of this solution is that it can be used with any csta-compatible pbx.
Keep in mind that, even though integration is possible at this time, Microsoft is planning to stop the support on this kind of integration.
Only the first solution will be available from that time on.
I hope this information is useful for you.
1) An OXE can be connected to an OCS environment, using a SIP trunk.
The SIP trunk is connected to a MS Mediation server.
It's possible to call from an OCS client to an OXE user and visa versa.
OCS clients can make outgoing calls through the OXE.
OCS clients can receive incoming calls though the OXE.
So no integration, but just a connection of two pbx systems.
2) OXE - OCS integration, using MyIC
The integration with MyIC and OCS will only work dor OCS R1 clients (ALU is working on a R2 connector).
A user will have two clients installed on their pc. These clients share e.g. presence information.
OCS can be used for presence and IM, while MyIC is used for making phone calls.
advantage of this solution that a My IC user can benefit of all OXE features.
3) OXE - OCS integration, using GETS
GETS will give you a CSTA based integration.
CSTA messages can be used to have remote call-control from the OCS client.
A user can dial a phonenumber from his OCS client and his physical phone will receive csta messages to call this number.
An advantage of this solution is that it can be used with any csta-compatible pbx.
Keep in mind that, even though integration is possible at this time, Microsoft is planning to stop the support on this kind of integration.
Only the first solution will be available from that time on.
I hope this information is useful for you.
-
Julio
Freedom, how are you?
Thank you for your information.
I'll be going over to the client and I will await the action that it will take.
But one thing is certain, the information that Microsoft will be stopping to make this integration was very important. Also because of the view that there will no longer support it.
Again, thank you
Thank you for your information.
I'll be going over to the client and I will await the action that it will take.
But one thing is certain, the information that Microsoft will be stopping to make this integration was very important. Also because of the view that there will no longer support it.
Again, thank you
-
chris2109
Microsoft will close the Remote Call Control interface at their next planned OCS release. There ist an announcement from Microsoft that all customers who have already the OCS 2007 environment with GETS get the RCC Interface in the next OCS without support. So the new coupling will be done with a local client integration (based on MyIC). Currently it works with OCS 2007 R1. OCS 2007 R2 compatibility is planned in the next few weeks...
-
munawarhamza
-
munawarhamza
great information !!!
please can u provide more information on option 1 mentioned above. I have OXE R9.0 with ICS 6.1 for 6500 user licenses. Also we have OCS R2 2007 on the desktop which needs to be integrated to OXE. if u can help me in interconnecting Both systems for incoming and outgoing calls using the same PSTN links on OXE please,
please can u provide more information on option 1 mentioned above. I have OXE R9.0 with ICS 6.1 for 6500 user licenses. Also we have OCS R2 2007 on the desktop which needs to be integrated to OXE. if u can help me in interconnecting Both systems for incoming and outgoing calls using the same PSTN links on OXE please,
-
cavagnaro
-
rklose
Re: OCS14Wave (Lynch)
Hi Freedom,freedom wrote:I'm not sure I understand your exact question. I will give you some possible OXE - OCS connections:
1) An OXE can be connected to an OCS environment, using a SIP trunk.
The SIP trunk is connected to a MS Mediation server.
It's possible to call from an OCS client to an OXE user and visa versa.
OCS clients can make outgoing calls through the OXE.
OCS clients can receive incoming calls though the OXE.
So no integration, but just a connection of two pbx systems.
2) OXE - OCS integration, using MyIC
The integration with MyIC and OCS will only work dor OCS R1 clients (ALU is working on a R2 connector).
A user will have two clients installed on their pc. These clients share e.g. presence information.
OCS can be used for presence and IM, while MyIC is used for making phone calls.
advantage of this solution that a My IC user can benefit of all OXE features.
3) OXE - OCS integration, using GETS
GETS will give you a CSTA based integration.
CSTA messages can be used to have remote call-control from the OCS client.
A user can dial a phonenumber from his OCS client and his physical phone will receive csta messages to call this number.
An advantage of this solution is that it can be used with any csta-compatible pbx.
Keep in mind that, even though integration is possible at this time, Microsoft is planning to stop the support on this kind of integration.
Only the first solution will be available from that time on.
I hope this information is useful for you.
my question about this topic is:
If I'll connect the 4400 Rel.9.1 with the new Lynch from Microsoft without Mediagateways only using SIP-Trunk. Is this possible?
Thanks
Ralf
