Message |
[+]
DMCC .NET API: Client Development (Archive - Oct 2013 and earlier)
» DMCC Registration issue, 24/05/2013 12:12:33
» Go to message
|
|
Thanks John,i will try adding delays to the press button activities. Going through some of the DMCC.NET FAQs i could see some suggested delays also in this regard. I also went through the AES Over view document regarding the capacities of AES and expected traffic from applications. After that i have few more concerns .
1. In the document ,for client media without encryption it is given as "100 simultaneous registrations with 20
simultaneous registrations per CLAN for a total of 5
CLANs. A gap of 10 seconds between each set of
100 registrations."
Does this mean that , there should be a gap of 10 seconds after registering 100 stations using 5 CLANS , 20 at a time in one CLAN , ?
2. I have 40 stations and 2 CLANs , Should i add these 2 CLANs in h323 gatekeeper list to provision the above distribution mentioned in query1?
3. Do i need to add a delay of 100ms between registerterminals of these 40 stations ?
Thanks and Regards
Abdul
|
|
[+]
DMCC .NET API: Client Development (Archive - Oct 2013 and earlier)
» DMCC Registration issue, 23/05/2013 14:31:13
» Go to message
|
|
Dear John,
The registrations were ok . i even given 10 seconds sleep after 20 registrations as per the AES overview document as i have 40 stations to be registered. But i havent given any delay in the code section for service observe from registered soft phones and this is called on the response of registration , Do you think that this will require delays in between onhook, pressing service observe button, offhook, dial extension etc. ?
Regards
Rasheed
|
|
[+]
DMCC .NET API: Client Development (Archive - Oct 2013 and earlier)
» DMCC Registration issue, 23/05/2013 13:34:46
» Go to message
|
|
Dear John,
i tested again today and found that i am able to do all the registrations succesfully if i comment the service observe initialization code in my application. i am calling the following code to start service observing a phone to be recorded. I am registering softphone and then on the reponse of register terminal i am doing the following code.
e.getPhone.SetHookswitchStatus(True, Nothing)
e.getPhone.PressButton(Phone.ButtonIDConstants.BUTTON_1 + (PushButtonVal - 1), Nothing)
'e.getPhone.SetHookswitchStatus(False, Nothing)
RecordingDevice.getPhone.SetHookswitchStatus(False, Nothing)
'make changes here for extension
For i As Integer = 0 To OwnerDeviceExt.Length - 1
Dim buttonNumber As Integer = setButtonIDConstants(OwnerDeviceExt.Substring(i, 1))
e.getPhone.PressButton(buttonNumber, Nothing)
Next
First make the softphone onhook , then press the service observe feature button (button number 8 configured), then i make softphone offhook , then i dial the number of the extension to be recorded.
if i comment the above code , registration is working fine. For the registration of softphone 12002 , i have pasted the errors i got in to the link http://pastebin.com/G96wLjE8
It was noticed from the above log that , once the service observe code is called, it is unregistering the softphone with the error "CM Connection lost - protocol timeout: MISC timer, tried 3 times.Possible problem(s) include:
1. Network connection is not working or is congested" , please refer the above link for the full error logs of softphone 12002.
Thanks and Regards
Abdul Rasheed
|
|
[+]
DMCC .NET API: Client Development (Archive - Oct 2013 and earlier)
» DMCC Registration issue, 22/05/2013 12:00:49
» Go to message
|
|
Hello,
we have a recording application which uses service observe mode. While testing i registered 40 DMCC stations and in the response we are using pressbutton to activate serice observe feature button and dial the phone to be recorded. The application is a windows service. It was noticed that ,in the response of registrations, all the registrations were succesful without any errors. But when we checked DMCC_DMC license consumption and registrered stations from CM ,only very few stations got registered. When we restart the service, again the registrations of another number of stations happened. When the session details is checked from AES, it is shown that 40 associated devices with that session. i am really confused what is happening. Is there any way to monitor the flow of registration through this applicaiton and what is happening during this registration process.
Regards
Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» DMCC stations, 13/05/2013 13:39:55
» Go to message
|
|
Hello,
How much is the maximum number of DMCC stations which can be registered from a single system. can i register up to 1000 DMCC stations which will be acting as service observers . Is there any limit in this regard?
Thanks and Regards
Abdul Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» Unable to read from socket. Socket to server has been closed, 08/03/2013 12:34:38
» Go to message
|
|
Dear Johnson,
If there is a private data version issue, will that cause to hang the connection between applicaion and AES server? If the version of TSAPI client is 4.2 and aes is 4.0 , will that cause an issue?
Regards
Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» Unable to read from socket. Socket to server has been closed, 05/03/2013 13:21:49
» Go to message
|
|
Dear Johnson,
TSAPI client application some times fails with error in the log "private message UNKNOWN(65535) was found.
02:50:42 ERROR:WARNING:TSAPI:g3pderr:E_WARNING:L 1074:C 38:[CAS.CPP]: For message [MONITOR_DEVICE:111] an inappropriate or unknown private message UNKNOWN(65535) was found.
02:50:42 "
We are using TSAPI client 4.2 and AES version 4.0 , will that be a reason for the above error. When the above error happens, our tsapi application will restart the DMCC application as a recovery measure , and as this tsapi error is occuring many times, DMCC application will get restarted many times and finally result in a socket close error. Following are the MVAP logs which i noticed during the DMCC failture of socket.
INFO: [1566:najmpbx:10.1.5.200:0] :session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3] Client API call
2013-02-23 02.51.40,104 com.avaya.mvcs.monitor.MonitoringServicesImpl stopMonitor
FINE: removing MediaControlListener: 92:[Holder]: [1566:najmpbx:10.1.5.200:0] ,com.avaya.mvcs.monitor.MediaControlListenerImpl@6f8860
2013-02-23 02.51.40,105 com.avaya.mvap.intsvc.CstaTerminalImpl tearDownDevice
FINE: [10.1.5.200:1566] station is now clear
2013-02-23 02.51.40,105 com.avaya.mvap.extsvc.DeviceServicesImpl releaseDeviceID
INFO: session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3] session released device [1566:najmpbx:10.1.5.200:0] via Client API call
2013-02-23 02.51.40,105 com.avaya.mvcs.proxy.CstaRouterNode processPacket
FINE: Received session[null] com.avaya.csta.binding.ReleaseDeviceIdResponse@1d3c40c in response to session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3] com.avaya.csta.binding.ReleaseDeviceId@32b816
2013-02-23 02.51.40,135 com.avaya.common.packet.TPacketizer readChannel
INFO: End of stream from DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Connected to SocketAddress: /172.16.0.146:1280
2013-02-23 02.51.40,135 com.avaya.mvcs.proxy.ExceptionEventHandlerNode handleEvent
FINE: Normal Operation: The far end closed the socket, event=ExceptionEvent[com.avaya.mvcs.proxy.TPacketReaderNode@134d246, com.avaya.common.packet.EndOfStreamException: End of stream from DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Connected to SocketAddress: /172.16.0.146:1280, session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3,DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Connected to SocketAddress: /172.16.0.146:1280]]
2013-02-23 02.51.40,145 com.avaya.mvcs.proxy.CstaRouterNode handlePipelineCommand
FINE: Socket is closed, so pausing event subscriptions for session=session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3,DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Not connected.]
2013-02-23 02.51.40,146 com.avaya.mvcs.proxy.TPacketReaderNode handlePipelineCommand
INFO: Closing channel=DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Not connected. and marking session=session 1D07E41E68BF78B83DCADB158FDDC9E8-3 as inactive
2013-02-23 02.51.40,147 com.avaya.sessionsvc.SessionObjectImpl markAsInactive
FINE: session 1D07E41E68BF78B83DCADB158FDDC9E8-3 is being marked as inactive.
2013-02-23 02.51.40,148 com.avaya.mvcs.proxy.CstaMarshallerNode$CstaMarshallerThread convertException
FINE: Returning negative ack to client session (1D07E41E68BF78B83DCADB158FDDC9E8-3) : com.avaya.csta.errors.InvalidSessionIDException: com.avaya.api.sessionsvc.exceptions.SessionInactiveException: Session = 1D07E41E68BF78B83DCADB158FDDC9E8-3 :: request = session[null] ch.ecma.csta.binding.stop.StopApplicationSession@1ebf1ca
2013-02-23 02.51.40,160 com.avaya.mvcs.proxy.ByteBufferToChannelNode processPacket
FINE: Unable to write to socket: packet=com.avaya.common.packet.TPacket@14f279c, session=session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3,DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Not connected.]
2013-02-23 02.51.40,160 com.avaya.mvcs.proxy.ExceptionEventHandlerNode handleEvent
FINE: Unknown Operation: The socket was already closed when a write was attempted... We're closing the near end of the socket, but session may not be affected, event=ExceptionEvent[com.avaya.mvcs.proxy.ByteBufferToChannelNode@14f79cb, java.nio.channels.ClosedChannelException, session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3,DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Not connected.]]
2013-02-23 02.51.40,161 com.avaya.mvcs.proxy.CstaRouterNode handlePipelineCommand
FINE: Socket is closed, so pausing event subscriptions for session=session[session 1D07E41E68BF78B83DCADB158FDDC9E8-3,DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Not connected.]
2013-02-23 02.51.40,161 com.avaya.mvcs.proxy.TPacketReaderNode handlePipelineCommand
INFO: Closing channel=DefaultTCPChannel Bound to SocketAddress: /10.1.5.194:4721 Not connected. and marking session=session 1D07E41E68BF78B83DCADB158FDDC9E8-3 as inactive
2013-02-23 02.51.45,148 com.avaya.sessionsvc.CleanupTimerTask run
FINE: CleanupTimerTask cleaning up: session 1D07E41E68BF78B83DCADB158FDDC9E8-3
2013-02-23 02.51.45,148 com.avaya.mvcs.proxy.CstaRouterNode$MySessionListener sessionCleanedup
FINE: Session is cleaned up, removing subscription for: session 1D07E41E68BF78B83DCADB158FDDC9E8-3
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 92
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 102
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 94
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 104
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 84
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 86
2013-02-23 02.51.45,149 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 96
2013-02-23 02.51.45,150 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 106
2013-02-23 02.51.45,172 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 108
2013-02-23 02.51.45,172 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 90
2013-02-23 02.51.45,172 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 110
2013-02-23 02.51.45,173 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 88
2013-02-23 02.51.45,173 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 100
2013-02-23 02.51.45,173 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
FINE: calling unsubscribe 98
2013-02-23 02.51.45,173 com.avaya.mvcs.proxy.SubscriptionManager unsubscribeAll
INFO: Clearing the executor
Thanks and Regards
Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» Unable to read from socket. Socket to server has been closed, 04/03/2013 10:22:53
» Go to message
|
|
Hello,
we are getting an error unexpectedly on a running system with AES version 4.0 , service provider dll version 4.1 . we noticed that after running the application for 2 days and every day early morning 3AM -4 AM our applicaiton will lose connection to AES server, if we try to reconnect it will give us error "Unable to read from socket. Socket to server has been closed" . To recover from this error , we need to restart the AES server. Is there any way to resolve this. Please get back to me at the earliest as this is bit critical for us.
Thanks and Regards
Abdul Rasheed
|
|
[+]
Device, Media and Call Control (Archive - Oct 2013 and earlier)
» Missing Media Events, 04/01/2013 12:29:12
» Go to message
|
|
Thanks Martin. I had a chat with Richard today, i got the configuration which cleared the issue.
Best Regards
Abdul
|
|
[+]
Device, Media and Call Control (Archive - Oct 2013 and earlier)
» Missing Media Events, 03/01/2013 11:03:23
» Go to message
|
|
Hello,
With service observe mode of recording, we noticed that Media events is missed out when a call is made from H.323 phone to another extension connected to an Avaya CM networked through H.323 trunk. if the call is between extensions of the same PBX or from extension to another phone through a normal trunk line , then the DMCC station registered for doing the service observe triggers the media events. Is there any specific reason due to which this happens. Is there any solution for getting the media events in all cases.
Best Regards
Abdul Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» IP_API license acquired instead of DMCC_DMC, 31/10/2012 13:19:01
» Go to message
|
|
Dear John,
The FAQ Q string is "When is a DMCC_DMC license allocated and when is it not?" it is mentioned under this question - "The DMCC protocol version of DMCC API referred in StartApplicationSession interface must be http://www-ecma-international.org/standards/ecma-323/csta/ed3/priv3 (AE Services R4.2.2) or later."
But i got it work with protocol version 3.0 and above.
Thanks and Regards
Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» IP_API license acquired instead of DMCC_DMC, 31/10/2012 05:39:18
» Go to message
|
|
Dear John,
I could resolve the issue . In fact we were providing the CM IP address in the Switch IP Address field of Dashboard and leaving the Switch Name as blank. It is able to register the terminal after i put Switchname in the dashboard and then invoked the GetDevice and then the RegisterTerminal. But i have a few queries.
1. Is it mandatory to enter Switch name in the GetDeviceID and register terminal . In the previous version of AE services this was not mandatory
2. It is supporting all protocols of DMCC , i tried 3.0, 4.1 , 4.2 etc which looks contradictory to the FAQ which says that 4.2 protocol should be negotiated.
I request you to kindly clarify the queries above.
Thanks a lot for your prompt response as you always do.
Best Regards
Abdul Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» IP_API license acquired instead of DMCC_DMC, 30/10/2012 13:25:46
» Go to message
|
|
Hello,
we were testing with DMCC dash board application on AES version 6.1 and CM 6.0 . 6 numbers of DMCC_DMC license is available in AES. But DMCC is returning an error "3014 Registration Reject reason: resourceUnavailable
Invalid product ID is specified. Check the version of switch or license file 111" . I checked the FAQ regarding this issue and verified the points mentioned in the FAQ .
1. I am trying to start application session with protocol version 5.2 (i tried with 4.2 and 6.1 also)
2. we are using the latest dashboard application
3. There is a switch connection available between AES and CM
Please let me know what can be the causes of this issue. If any logs are required , we can provide you the same.
Thanks and Regards
Abdul Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» Roaming profile, 10/04/2012 11:51:19
» Go to message
|
|
Hello,
We have supplied our voice logger to one of our customer recently. We use Service observe for recording. Customer is saying that they dont have a hunt group , but the extensions are using roaming profile. They have 50 IP phones , for which 150 users are using the phones in different shift. He said they are using roaming profile for extensions. My concern is that , if we use Service observe for recording this setup , how it can be done?
Thanks and Regards
Rasheed
|
|
[+]
AE Services General (Archive - Oct 2013 and earlier)
» IVR and Call information, 12/01/2012 00:37:31
» Go to message
|
|
Hello John,
I was also expecting the same scenario as you have explained below and it is clear. Regarding the IVR the structure is the following as explained by our customer.
"Current model is built over Suse Linux OS on Asterisk ver 1.4.2.62 - IVR is standard dialplan based - probably connected through SIP to main Avaya .Future system will be on VXI* , Asterisk again for platform but working with VoiceXML scripts "
Do you think that UUI information is passed through TSAPI even if the call is transfered through SIP?
Thanks and Regards
Rasheed
|
|