Message |
[+]
DMCC APIs
» IP Office Recording, 23/10/2019 09:54:12
» Go to message
|
|
Hi Fergos,
Centralised CTI web services require Avaya One-X portal license , is this some additional license to be purchased with Avaya IP office ?
THanks and Regards
Rasheed
|
|
[+]
DMCC APIs
» IP Office Recording, 17/10/2019 09:17:35
» Go to message
|
|
Hello,
Apologies for posting the question here , but i couldnt find a forum to raise this query. We would wish to develop a recording application for IP office using the Voice Mail pro . which document should i refer to do this ? i was checking the devconnect site but i couldnt find any.
Thanks & Regards
Abdul Rasheed
|
|
[+]
DMCC APIs
» Call Barring, 06/02/2019 07:01:38
» Go to message
|
|
Thanks a lot John and Martin for your support.
Best Regards
Rasheed
|
|
[+]
DMCC APIs
» Call Barring, 05/02/2019 07:45:46
» Go to message
|
|
Thanks Martin. Does the SMS API consume any licenses from AES ?
Best Regards
Abdul Rasheed
|
|
[+]
DMCC APIs
» Call Barring, 05/02/2019 06:09:05
» Go to message
|
|
Thanks Martin.
we are ok to block the call after the far end rings. So this method seems to be fine. However it will consume 1 TSAPI license per monitored station. So i would like to know also if there is any other way to block programatically the outgoing calls from a particular extension? For example any configuration webservice API which can bring in some Class of restriction for the particular monitored extensions which will block the outgoing calls from that extension .
we were able to do that for Avaya IP office by changing the user to a new user rights group which bars the outgoing calls.
Thanks and Regards
Abdul Rasheed
|
|
[+]
DMCC APIs
» Call Barring, 05/02/2019 05:25:01
» Go to message
|
|
Hello,
we have a call recording application which uses Multi registration mode of recording with DMCC. we have a specific requirement in
which we need to block the monitored extension from making any more outgoing call . we require to block the extension
automatically or manually the DMCC / TSAPI monitored extension . Is it possible to bar the extension from making any more
outgoing call using any features in DMCC or TSAPI?
Thanks and Regards
Abdul Rasheed
|
|
[+]
DMCC APIs
» Avaya IP Office TAPI Compatibility on Windows 2016 server, 02/10/2018 07:36:02
» Go to message
|
|
Hello,
i was trying to get an information on Avaya IP office TAPI client version 10, if it can be installed on Windows 2016 server 64 bit OS.
please let me know as i couldnt find any information regarding this from the related documents.
Thanks & Regards
Abdul Rasheed
|
|
[+]
IP Office Contact Center Web Services Collection (WSC) (Read-Only Archive June 2021)
» Block outgoing facility of extension , 20/12/2017 04:31:18
» Go to message
|
|
I have a query about IP office.I did n't find a forum for IP office , so that I am asking here..
I need to block outgoing facility of some extensions . How can I do this with c#,.net environment? Or is there have a predefined web services for that? please explain..
Please help me....
|
|
[+]
DMCC APIs
» Multiple registration Issue, 08/11/2017 11:26:38
» Go to message
|
|
Thanks Martin,
i will try it out and will get back to you soon.
Best Regards
Rasheed
|
|
[+]
DMCC APIs
» Multiple registration Issue, 07/11/2017 11:49:33
» Go to message
|
|
Hello Martin,
It took me some time to get back to you on this issue. I added a listener for EndpointRegistered event. But still the end points get unregistered without any events like EndpointRegistered not being triggered to the application. But i could take a DMCC log from the AES which clearly shows that there was a unregister happened in the station as given below.
FINE: invokeID= 1372 Received session[null] ch.ecma.csta.binding.reset.ResetApplicationSessionTimerPosResponse@1b8cbb1<mailto:ch.ecma.csta.binding.reset.ResetApplicationSessionTimerPosResponse@1b8cbb1> in response to session[session 223EF2EDDDDC4095BB6A01ACA16332A9-119] ch.ecma.csta.binding.reset.ResetApplicationSessionTimer@18fcc77<mailto:ch.ecma.csta.binding.reset.ResetApplicationSessionTimer@18fcc77>
2017-09-26 07.22.44,077 com.avaya.mvcs.station.h323.ras.IncomingRASHandlerImpl receivedUnregistrationRequest
FINE: [10.100.115.75:2820:0] Received unregistration request (URQ)
2017-09-26 07.22.44,077 com.avaya.mvcs.station.h323.ras.OutgoingRASHandlerImpl shutdown
FINE: [10.100.115.75:2820:0] Shutting down registration.
2017-09-26 07.22.44,077 com.avaya.mvcs.station.h323.ras.OutgoingRASHandlerImpl sendUnregistrationConfirmation
FINE: [10.100.115.75:2820:0] Send unregistration confirm (UCF)
2017-09-26 07.22.44,078 com.avaya.mvcs.terminal.h323.TerminalH323 tearDownDevice
FINE: [10.100.115.75:2820:0] Tearing down station
2017-09-26 07.22.44,078 com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice cancelQ931DisconnectTimer
FINE: [10.100.115.75:2820:0] cancelling Q931Disconnect timer
2017-09-26 07.22.44,078 com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice unregisterDevice
FINE: [10.100.115.75:2820:0] Client API call - unregisterDevice
2017-09-26 07.22.44,078 com.avaya.mvcs.station.h323.ras.DefaultTerminalDevice cancelQ931DisconnectTimer
FINE: [10.100.115.75:2820:0] cancelling Q931Disconnect timer
Please find the attached complete logs which contain the above extract of logs also. Hoping to get a quick response from you soon.
Thanks and Regards
Rasheed
|
|
[+]
DMCC APIs
» IP Office TAPI, 04/10/2017 09:38:46
» Go to message
|
|
Hi Cameron ,
The issue has been resolved. In fact the IP address being used in TAPI configuration of the system was the IP office server IP. But there were controllers to which the extensions to be monitored belong to. Those controllers were not updated with the CTI LINK PRO license. we updated those licenses in controllers and also changed the IP address to controller IP. Then it starts working fine. Thanks Cameron.
One more small query. In a call scenario in which Mobile phone A calls IPO extension B and B picked up call and talking. extension C calls extension B , then B puts A on hold and talk to C. Then B disconnected call with C and resumed the call with A. It was noticed that there are no LINE_CONNECTED TAPI events being triggered when the call with A is resumed by B .
But if Mobile phone A calls B , B picks up call , then B put A on hold , then B resume the call with A.. In this scenario , the during the last resuming the call LINE_CONNECTED TAPI event is getting triggered.
Any help is highly appreciated.
Thanks and Regards
Abdul Rasheed
|
|
[+]
DMCC APIs
» IP Office TAPI, 26/09/2017 05:55:57
» Go to message
|
|
Hi Cameron,
Thanks for your quick reply. we tried the options which you mentioned in your mail. Reboot the system and then apply the configuration again and rebooted again. Also tried to set the option of Single user mode and then set to Third party mode and then restarted Telephony service and tried again. In all these options it is not able to show the lines or Avaya TAPI is not able to get hold of the lines. Is there any logs to be enabled to check and analyse what is going wrong.
Thanks and Regards
Rasheed
|
|
[+]
DMCC APIs
» IP Office TAPI, 25/09/2017 06:08:07
» Go to message
|
|
Hello,
I know that this forum is not for Avaya IP Office TAPI based queries. But i couldnt find a forum for the same in devconnect program to raise this query. we have an IP office 500 Version 8 installed at our premise. It is enabled with CTILINKPRO license. when we install TAPI client in windows 7 64 Bit OS and WIndows xp , we are able to view the TAPI lines from IP office in the windows dialer application. we configured the TAPI in third party monitoring mode. But when we tried it using Windows 2012 Server R2 64 Bit OS , it is not showing any lines. Any help on this issue is really appreciated.
Thanks and Regards
Abdul Rasheed
|
|
[+]
DMCC APIs
» Multiple registration Issue, 14/07/2017 05:29:50
» Go to message
|
|
Hi John,
THanks for your response. Everything work perfect with the application at the time of registration and we are getting media and other events as expected. But after running it for 1 day, we notice that the dependent stations are not getting any events from the corresponding phones and these stations are shown as of status IDLE in the AES and ofcourse we didnt get any unregister event. So our worry is why these stations are going to an IDLE state without any events and the reason for this need to be identified. Is it related to the number of switch connections between AES and CM ? I am asking this because if a dependent station goes to IDLE state even when the main station to which the dependent station is registered with , is still working. can this be becuase AES-CM switch connection is not allowing enough messages to be passed between it and hence it make the station as IDLE since there is no HEART BEAT . Its just my thought , i dont have any logs available with me to prove it now. THe DMCC logs which i have taken didnt say anything about this issue in it.
Thanks and Regards
Rasheed
|
|
[+]
DMCC APIs
» Multiple registration Issue, 07/07/2017 07:55:56
» Go to message
|
|
Hello,
we test our DMCC based call recording application by registering 140 stations. Registration in Dependent mode went very well and all the phones were registered. BUt while we run it for 3 to 4 days , it was noticed that some of the stations are not registered and not generating any media events at all. AES version is 5.2.3 , CM version 6.0 . When checking the status of DMCC stations registerd in dependent mode in multiple registration with corresponding monitored stations, those DMCC stations are showing IDLE status in the AES. But from our DMCC application , we are not getting any unregistered events or any notifications when the DMCC station get unregistered. Any possible reason for this behaviour ? Any help on resolving this issue is highly appreciated.
Thanks and Regards
Rasheed
|
|