Hi,
We want to create an application which controls call time of extensions. If any extension's call state is over certain time, we will kill or transfer call. To develop this application, we need to see all busy extensions' states.
We have OmniTouch XML WEB Server Release 5.0.1 Application Programming Interface. But we don't have any information about which sample we can get as base, or which web service we can use.
Can anyone help us?
Thank You,
Fatma
XML Web Services Application Roadmap
-
cavagnaro
Re: XML Web Services Application Roadmap
XML API Framework is the base. For such info I'd go for MyPhone XML API as it will monitor by using CSTA the status of desired extensions.
-
Fatma
Re: XML Web Services Application Roadmap
Hi,
We want to get call list which monitors extension numbers, status and duration. Yet, we don't use CSTA. I want to ask if we can get call list by using XML API Framework and XML web services. If so, which web services, do we need?
Also can we close a call which I see the call's status by using XML API Framework?
Thank You,
Fatma
We want to get call list which monitors extension numbers, status and duration. Yet, we don't use CSTA. I want to ask if we can get call list by using XML API Framework and XML web services. If so, which web services, do we need?
Also can we close a call which I see the call's status by using XML API Framework?
Thank You,
Fatma
-
cavagnaro
Re: XML Web Services Application Roadmap
The framework is:
OXE as base
CSTA as communication protocol
OTS as CSTA client
Myphone/XML API as client
So you need no matter what CSTA (Myphone) enabled to do your requirement.
And yes, using XML API to cut a call which will send an order to OTS which will send the order using CSTA.
OXE as base
CSTA as communication protocol
OTS as CSTA client
Myphone/XML API as client
So you need no matter what CSTA (Myphone) enabled to do your requirement.
And yes, using XML API to cut a call which will send an order to OTS which will send the order using CSTA.
-
vsc77420
Re: XML Web Services Application Roadmap
Hello,
Well maybe you should you the phone events from the XML API Framework.
For each user declared on your XML API Server you do a login and then suscribe to a web server who should log all your call state changes.
So that each time a user makes an ringingOutgoing call , your web server starts a timer for this user because he receives the event and when he gets the releasing state for this phone it shall stop the timer and sum the total time in his account. Meanwhile if he exceed the amount of time allowed you invoke the SOAP action from the XML Phone API clearcall.
You should have all the info on open api on the application alcatel web site http://www.applicationpartner.alcatel-lucent.com/
The program should do:
- log to the api framework with login and password : should give you an FwId (frameworkId) which is a string
- for each user declared on the api server, on the XmlPhone API:
login(fwId,"http://yournotificationurl","") the third parameter is for the event types you want to discard , it shall give you a loginId which is the phone number of the set. You could remove http://yournotificationurl and implement this on a further command called subscribe.
Than your web sever (your notification url) should listen to all SOAP Message , parse the message to get the call state and then answer an SOAP Answer.
Hope it helps
Well maybe you should you the phone events from the XML API Framework.
For each user declared on your XML API Server you do a login and then suscribe to a web server who should log all your call state changes.
So that each time a user makes an ringingOutgoing call , your web server starts a timer for this user because he receives the event and when he gets the releasing state for this phone it shall stop the timer and sum the total time in his account. Meanwhile if he exceed the amount of time allowed you invoke the SOAP action from the XML Phone API clearcall.
You should have all the info on open api on the application alcatel web site http://www.applicationpartner.alcatel-lucent.com/
The program should do:
- log to the api framework with login and password : should give you an FwId (frameworkId) which is a string
- for each user declared on the api server, on the XmlPhone API:
login(fwId,"http://yournotificationurl","") the third parameter is for the event types you want to discard , it shall give you a loginId which is the phone number of the set. You could remove http://yournotificationurl and implement this on a further command called subscribe.
Than your web sever (your notification url) should listen to all SOAP Message , parse the message to get the call state and then answer an SOAP Answer.
Hope it helps
-
vsc77420
Re: XML Web Services Application Roadmap
Maybe you should consider subscribe events with myphoneApi.
The application should make the followings:
- Log to the api framework with login(fwUser,fwPass) which should give you a fwId (framework identificator for all operations you'll make after) this login operation must be done on the XmlApiFramework
- For each registered user declared on the API XML Server you should make a "login" (fwId,NotificationURL="",undesirable events ="") operation (gives you a loginid) followed with a subscribe(fwId,"http://yourwebservernotificationplace","") operation (gathering it with a webserver url) from the XmlPhone
Your server Url will handle all the SOAP notification from the API XML Server , acknowledging it and if:
- State notification of a phone is ringingOutgoing: starts a timer and store callref
- State notification of a phone is Releasing and callref is known: stops the timer
- timer + oldtimer > allowedtime than clearcall operation to the XMLPhone providing fwId,loginId and callref as argument.
I don't know in what are you coding , but take a look on the wsdl on application partner web site , the xmlphone.wsdl and xmlphoneevent.wsdl
Regards
The application should make the followings:
- Log to the api framework with login(fwUser,fwPass) which should give you a fwId (framework identificator for all operations you'll make after) this login operation must be done on the XmlApiFramework
- For each registered user declared on the API XML Server you should make a "login" (fwId,NotificationURL="",undesirable events ="") operation (gives you a loginid) followed with a subscribe(fwId,"http://yourwebservernotificationplace","") operation (gathering it with a webserver url) from the XmlPhone
Your server Url will handle all the SOAP notification from the API XML Server , acknowledging it and if:
- State notification of a phone is ringingOutgoing: starts a timer and store callref
- State notification of a phone is Releasing and callref is known: stops the timer
- timer + oldtimer > allowedtime than clearcall operation to the XMLPhone providing fwId,loginId and callref as argument.
I don't know in what are you coding , but take a look on the wsdl on application partner web site , the xmlphone.wsdl and xmlphoneevent.wsdl
Regards
