ThiloMinator
Technical User
Hello Forum, hello world,
We have a strange problem with our Definity.
We have a Definity 9.5gsi with a MapD (Rel 2.0, issue 2.1) board. We use it for developmental purposes and it it has been running perfect since approx 8 years, oldie but goldie ;-) .
There a about 20 digital phones configured, some agents, VDNs, etc. We were able to monitor all devices via ASAI, make call control etc. This was always the status in the recent years. When I write "monitoring a device" or "device monitor" it means "Third-Party Domain Control" in terms of ASAI.
Now, last friday I wanted to run a test. I tried to start device monitors for three devices. The MonitorStart request for the third device failed. The Third-Party Domain Control request for the third device is asnwered by RELeasCOMplete by the Definity, the cause for rejection is "resource not available". The following lines show the RELeaseCOMplete message as raw ASAI and decoded.
______________________________________________________________________________________________
08 00 00 17 08 02 ff e2 5a 96 1c 0f 91 a3 0c 02 01 01 02 01 c4 40 04 08 02 e1 a8
______________________________________________________________________________________________
2012-12-21 12:54:38,123 DEBUG [J] Handling Response (turnaround time ca-->pbx-->ca was 16ms):
ASAIMessage [08]
CRV [] (byte[]) = ffe2
RELeaseCOMplete [5a]
CodeShift96 [96] (null) =
IEFacility [1c]
ServiceDiscriminator [] (byte) = 91
ReturnErrorComponent [a3]
DEInvokeId [02] (byte) = 01
DEOperationValue [02] (byte) = c4: OV_3RD_PARTY_DOM_CONTR_REQ (Third Party Domain (Station) Control Request)
DEArgument [40]
IECause [08] (int) = 57768: CAUSE_UNAVAILABLE_RES (Resources not available)
______________________________________________________________________________________________
While debugging the problem I noticed that the problem is not device-specific. I can monitor maximum two devices. If I have already started monitors for devices A and B monitorStart for device C fails. Now if I release monitor B then I can start the monitor for device C. If I now try to also monitor device B again the monitorStart is rejected for device B, etc.
When I reboot the DLG or the PBX I can monitor all devices afterwards. After some time between some minutes and approx. a day the ability to monitor all devices is getting lost again.
When I start all monitors directly after the reboot, then leave the monitors activated, and then wait a day all monitors are still available and usable. When I now release a monitor an immediately after try to restart it the MonitorStart is rejected.
It appears to be a problem where the fault condition can be resetted by a MapD or PBX reboot but it reoccurs like a refilling rain tub within between some minutes and a day.
Also the problem can be triggered immediately by trying to monitor a not-existing device number. In this case there finally remains one monitorable device - until the next reboot.
DISPLAY CAPACITY shows all available licenses, no license conditions have changed. I am the only one administering at the PBX so I am shure that nobody makes changes at the configuration.
I have no idea where to search for the problem. Any hints and help appreciated
Many thanks!
Cheers,
Thilo
We have a strange problem with our Definity.
We have a Definity 9.5gsi with a MapD (Rel 2.0, issue 2.1) board. We use it for developmental purposes and it it has been running perfect since approx 8 years, oldie but goldie ;-) .
There a about 20 digital phones configured, some agents, VDNs, etc. We were able to monitor all devices via ASAI, make call control etc. This was always the status in the recent years. When I write "monitoring a device" or "device monitor" it means "Third-Party Domain Control" in terms of ASAI.
Now, last friday I wanted to run a test. I tried to start device monitors for three devices. The MonitorStart request for the third device failed. The Third-Party Domain Control request for the third device is asnwered by RELeasCOMplete by the Definity, the cause for rejection is "resource not available". The following lines show the RELeaseCOMplete message as raw ASAI and decoded.
______________________________________________________________________________________________
08 00 00 17 08 02 ff e2 5a 96 1c 0f 91 a3 0c 02 01 01 02 01 c4 40 04 08 02 e1 a8
______________________________________________________________________________________________
2012-12-21 12:54:38,123 DEBUG [J] Handling Response (turnaround time ca-->pbx-->ca was 16ms):
ASAIMessage [08]
CRV [] (byte[]) = ffe2
RELeaseCOMplete [5a]
CodeShift96 [96] (null) =
IEFacility [1c]
ServiceDiscriminator [] (byte) = 91
ReturnErrorComponent [a3]
DEInvokeId [02] (byte) = 01
DEOperationValue [02] (byte) = c4: OV_3RD_PARTY_DOM_CONTR_REQ (Third Party Domain (Station) Control Request)
DEArgument [40]
IECause [08] (int) = 57768: CAUSE_UNAVAILABLE_RES (Resources not available)
______________________________________________________________________________________________
While debugging the problem I noticed that the problem is not device-specific. I can monitor maximum two devices. If I have already started monitors for devices A and B monitorStart for device C fails. Now if I release monitor B then I can start the monitor for device C. If I now try to also monitor device B again the monitorStart is rejected for device B, etc.
When I reboot the DLG or the PBX I can monitor all devices afterwards. After some time between some minutes and approx. a day the ability to monitor all devices is getting lost again.
When I start all monitors directly after the reboot, then leave the monitors activated, and then wait a day all monitors are still available and usable. When I now release a monitor an immediately after try to restart it the MonitorStart is rejected.
It appears to be a problem where the fault condition can be resetted by a MapD or PBX reboot but it reoccurs like a refilling rain tub within between some minutes and a day.
Also the problem can be triggered immediately by trying to monitor a not-existing device number. In this case there finally remains one monitorable device - until the next reboot.
DISPLAY CAPACITY shows all available licenses, no license conditions have changed. I am the only one administering at the PBX so I am shure that nobody makes changes at the configuration.
I have no idea where to search for the problem. Any hints and help appreciated
Many thanks!
Cheers,
Thilo