Cisco Unified Application Environment Mailing Lists                                                

Subscribing to the mailing-lists

To Subscribe one or more of our mailing-lists,
please use the mailing-list management page at this URL: http://developer.cisco.com/web/cuae/mailer.

  Web Archives

       To browse the mailing-list archives, select one of the categories below:

 

Cisco Unified Application Environment Developer Forums Cisco Unified Application Environment Developer Forums
Combination View Flat View Tree View
Threads [ Previous | Next ]
RE: Please Help: CiscoIPPhoneError number = "6"
toggle
Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 4/30/09 7:46 PM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 4/30/09 9:07 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/1/09 2:50 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/1/09 4:39 PM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 5/2/09 6:48 AM
RE: Please Help: CiscoIPPhoneError number = "6" Craig Thrall 5/4/09 3:14 PM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 5/4/09 6:28 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/8/09 4:36 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/8/09 8:25 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/11/09 4:05 PM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 5/11/09 4:59 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/11/09 9:02 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 5/19/09 3:00 PM
RE: Please Help: CiscoIPPhoneError number = "6" Neha Dar 5/22/09 6:09 AM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 5/30/09 7:27 AM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 6/2/09 3:58 PM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 6/16/09 11:14 PM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 6/17/09 12:43 AM
RE: Please Help: CiscoIPPhoneError number = "6" Aaron Ragheb 6/17/09 4:46 PM
RE: Please Help: CiscoIPPhoneError number = "6" Craig Thrall 6/17/09 8:29 PM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 6/18/09 9:05 PM
RE: Please Help: CiscoIPPhoneError number = "6" Craig Thrall 6/22/09 7:15 PM
RE: Please Help: CiscoIPPhoneError number = "6" UP Chaurasia 7/23/09 10:57 AM
RE: Please Help: CiscoIPPhoneError number = "6" David Staudt 7/23/09 3:28 PM
RE: Please Help: CiscoIPPhoneError number = "6" UP Chaurasia 10/15/09 3:39 AM
RE: Please Help: CiscoIPPhoneError number = "6" Rakesh Kumar 10/27/09 10:23 AM
RE: Please Help: CiscoIPPhoneError number = "6" UP Chaurasia 10/27/09 10:44 AM
RE: Please Help: CiscoIPPhoneError number = "6" UP Chaurasia 11/2/09 11:37 AM
RE: Please Help: CiscoIPPhoneError number = "6" Rakesh Kumar 11/3/09 8:29 AM
Hi folks,
   I have a trivial CUAE 2.5 SR2 program written in C# that works to send a CiscoIpPhoneText to a phone.
 
This program works on 7970s and 7921s.  It does not work on the 7960.  I get all kind of erratic behavior (the other day, I posted about this), I would get failure codes, yet the entire transaction would succeed...now I am consistently getting CiscoIPPhoneError number = "6" which has been failed to be documented in the xsi).
 
I enclose the DeviceInformationX page for the phone.
I enclose the app server log.
I enclose the code (username/passwords are blacked out).
 
<DeviceInformation>
<MACAddress>000BBE1CF2FC</MACAddress>
<HostName>SEP000BBE1CF2FC</HostName>
4381
<appLoadID>P00308001000</appLoadID>
<bootLoadID>PC0303010001</bootLoadID>
<versionID>8.0(10.0)</versionID>
<DSPLoadID>4.0(5.0)[A0]</DSPLoadID>
<addonModule1/>
<addonModule2/>
<hardwareRevision>4.1</hardwareRevision>
<serialNumber>INM064905SX</serialNumber>
<modelNumber>CP-7960G</modelNumber>
<Codec>ADLCodec</Codec>
<Amps>5V Amp</Amps>
<C3PORevision>2</C3PORevision>
<MessageWaiting> NO</MessageWaiting>
</DeviceInformation>
 
 
2009:04:30::13:36:59(76): Verbose: JTP Got 20(IncomingCall) message from v7.0.
2009:04:30::13:36:59(76): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:04:30::13:36:59(76): Verbose: JTP Field: 6(DeviceType) = 3
2009:04:30::13:36:59(76): Verbose: JTP Field: 40(CallId) = Z3nN8z25pkwlfc66
2009:04:30::13:36:59(76): Verbose: JTP Field: 41(To) = 8009
2009:04:30::13:36:59(76): Verbose: JTP Field: 42(From) = 4381
2009:04:30::13:36:59(76): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:04:30::13:36:59(76): Verbose: JTP Field: 53(CallControlCause) = NORMAL
2009:04:30::13:36:59(76): Verbose: JTP Field: 66(JTapiCallId) = 39072/2
2009:04:30::13:36:59(76): Info: JTP Added JTapi call 1000033<->Z3nN8z25pkwlfc66
2009:04:30::13:36:59(76): Info: TM  Loading IncomingCall state map to handle Metreos.CallControl.IncomingCall event
2009:04:30::13:36:59(76): Info: TM  Processing new inbound call (1000033) from '4381' to '8009'
2009:04:30::13:36:59(76): Verbose: TM  Executing state: 617769025cac:1000033:1 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(76): Verbose: TM  Executing state: 617769025cac:1000033:5 (ForwardEventToApp) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(76): Verbose: LM  License check PASS: licensed: 100, running: 0.
2009:04:30::13:36:59(76): Verbose: EPM Event message: Metreos.CallControl.IncomingCall
2009:04:30::13:36:59(76): Verbose: EPM Test7960-Default-1: Running scripts added
2009:04:30::13:36:59(76): Verbose: EPM Legacy event: Metreos.CallControl.IncomingCall sent to etch app: Test7960
2009:04:30::13:36:59(89): Info: TM  Enqueuing action (1000033): Metreos.CallControl.AnswerCall
2009:04:30::13:36:59(89): Verbose: TM  Executing state: 617769025cac:1000033:10 (AssumePreferredTxCodec) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(89): Info: TM  Assuming preferred codec is Tx codec (1000033): G711u:20
2009:04:30::13:36:59(89): Verbose: TM  Executing state: 617769025cac:1000033:15 (ReserveConnection) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(89): Verbose: MCP connect message sent successfully
2009:04:30::13:36:59(89): Verbose: MEP Sending success response (1:431)
2009:04:30::13:36:59(90): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.MediaControl
2009:04:30::13:36:59(90): Verbose: TM  Executing state: 617769025cac:1000033:20 (AcceptCall) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(90): Verbose: JTP Sent AcceptCall. stackCallId:Z3nN8z25pkwlfc66
2009:04:30::13:36:59(90): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.CallControl.JTapi
2009:04:30::13:36:59(90): Verbose: TM  Executing state: 617769025cac:1000033:25 (SetMedia) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(90): Verbose: JTP Set media for call (ID: 1000033) RxIp: 192.168.102.20 RxPort: 20538
2009:04:30::13:36:59(92): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.CallControl.JTapi
2009:04:30::13:36:59(92): Verbose: JTP Got 99(Ringing) message from v7.0.
2009:04:30::13:36:59(92): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:04:30::13:36:59(92): Verbose: JTP Field: 6(DeviceType) = 3
2009:04:30::13:36:59(92): Verbose: JTP Field: 40(CallId) = Z3nN8z25pkwlfc66
2009:04:30::13:36:59(92): Verbose: JTP Field: 41(To) = 8009
2009:04:30::13:36:59(92): Verbose: JTP Field: 42(From) = 4381
2009:04:30::13:36:59(92): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:04:30::13:36:59(92): Verbose: JTP Field: 66(JTapiCallId) = 39072/2
2009:04:30::13:36:59(92): Verbose: TM  Executing state: 617769025cac:1000033:30 (ForwardActionToProvider) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(92): Verbose: TM  Forwarding Metreos.CallControl.JTapi.AnswerCall action to provider
2009:04:30::13:36:59(92): Verbose: JTP Sent AnswerCall. stackCallId:Z3nN8z25pkwlfc66, rxIP:192.168.102.20, rxPort:20538
2009:04:30::13:36:59(92): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.CallControl.JTapi
2009:04:30::13:36:59(93): Verbose: TM  Executing state: 617769025cac:1000033:35 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(93): Info: TM  Call '1000033' switching to state map: IncomingCall_WaitTxRx
2009:04:30::13:36:59(93): Verbose: TM  Executing state: 617769025cac:1000033:1 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:36:59(95): Verbose: JTP Got 31(CallEstablished) message from v7.0.
2009:04:30::13:36:59(95): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:04:30::13:36:59(95): Verbose: JTP Field: 6(DeviceType) = 3
2009:04:30::13:36:59(95): Verbose: JTP Field: 40(CallId) = Z3nN8z25pkwlfc66
2009:04:30::13:36:59(95): Verbose: JTP Field: 41(To) = 8009
2009:04:30::13:36:59(95): Verbose: JTP Field: 42(From) = 4381
2009:04:30::13:36:59(95): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:04:30::13:36:59(95): Verbose: JTP Field: 46(Cause) = normal
2009:04:30::13:36:59(95): Verbose: JTP Field: 53(CallControlCause) = NORMAL
2009:04:30::13:36:59(95): Verbose: JTP Field: 66(JTapiCallId) = 39072/2
2009:04:30::13:36:59(95): Info: TM  Enqueuing event (1000033): Metreos.CallControl.CallEstablished
2009:04:30::13:37:00(07): Verbose: JTP Got 98(MediaEstablished) message from v7.0.
2009:04:30::13:37:00(07): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:04:30::13:37:00(07): Verbose: JTP Field: 6(DeviceType) = 3
2009:04:30::13:37:00(07): Verbose: JTP Field: 21(TxIP) = 192.168.60.27
2009:04:30::13:37:00(07): Verbose: JTP Field: 22(TxPort) = 30986
2009:04:30::13:37:00(07): Verbose: JTP Field: 25(Codec) = 1
2009:04:30::13:37:00(07): Verbose: JTP Field: 26(Framesize) = 10
2009:04:30::13:37:00(07): Verbose: JTP Field: 40(CallId) = Z3nN8z25pkwlfc66
2009:04:30::13:37:00(07): Verbose: JTP Field: 41(To) = 8009
2009:04:30::13:37:00(07): Verbose: JTP Field: 42(From) = 4381
2009:04:30::13:37:00(07): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:04:30::13:37:00(07): Verbose: JTP Field: 66(JTapiCallId) = 39072/2
2009:04:30::13:37:00(09): Verbose: TM  MediaEstablished (1000033): Tx Addr=192.168.60.27:30986, RxAddr=192.168.102.20:20538, TxCodec=G711u:10, RxCodec=G711u:10.
2009:04:30::13:37:00(09): Info: TM  Enqueuing event (1000033): Metreos.CallControl.MediaEstablished
2009:04:30::13:37:00(09): Verbose: TM  MediaEstablished (1000033): Tx Addr=192.168.60.27:30986, RxAddr=192.168.102.20:20538, TxCodec=G711u:10, RxCodec=G711u:10.
2009:04:30::13:37:00(09): Verbose: TM  Executing state: 617769025cac:1000033:5 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(09): Verbose: TM  Executing state: 617769025cac:1000033:10 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(09): Verbose: TM  Executing state: 617769025cac:1000033:15 (CreateConnection) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(09): Verbose: MCP connect message sent successfully
2009:04:30::13:37:00(14): Verbose: MEP Sending success response (1:432)
2009:04:30::13:37:00(14): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.MediaControl
2009:04:30::13:37:00(14): Verbose: TM  Executing state: 617769025cac:1000033:20 (SendStartTxToApp) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(14): Verbose: EPM Event message: Metreos.CallControl.StartTx
2009:04:30::13:37:00(14): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:00(14): Verbose: EPM Legacy event: Metreos.CallControl.StartTx sent to etch app: Test7960
2009:04:30::13:37:00(14): Verbose: TM  Executing state: 617769025cac:1000033:25 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(15): Verbose: TM  Executing state: 617769025cac:1000033:30 (SendStartRxToApp) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(15): Verbose: EPM Event message: Metreos.CallControl.StartRx
2009:04:30::13:37:00(15): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:00(15): Verbose: EPM Legacy event: Metreos.CallControl.StartRx sent to etch app: Test7960
2009:04:30::13:37:00(15): Verbose: TM  Executing state: 617769025cac:1000033:35 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(15): Verbose: TM  Executing state: 617769025cac:1000033:40 (ForwardResponseToApp) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(15): Verbose: EPM Response message: success
2009:04:30::13:37:00(15): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:00(15): Verbose: EPM Provider action response sent, method: Metreos.CallControl.answerCall, message id: success
2009:04:30::13:37:00(15): Verbose: TM  Executing state: 617769025cac:1000033:1000 (EndScript) - Metreos.CallControl.JTapi
2009:04:30::13:37:00(15): Verbose: TM  Script ended for call '1000033'. Waiting for call service request...
2009:04:30::13:37:00(25): Verbose: EPM Test7960-Default-1: native action: Metreos.Native.CiscoIpPhone.CreateExecute completed
2009:04:30::13:37:00(25): Verbose: EPM Native action response message sent for: createExecute
2009:04:30::13:37:00(32): Verbose: EPM Test7960-Default-1: native action: Metreos.Native.CiscoIpPhone.SendExecute completed
2009:04:30::13:37:00(85): Verbose: EPM Event message: Metreos.Providers.Http.GotRequest
2009:04:30::13:37:00(85): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:00(85): Verbose: EPM Legacy event: Metreos.Providers.Http.GotRequest sent to etch app: Test7960
2009:04:30::13:37:00(95): Verbose: EPM Test7960-Default-1: native action: Metreos.Native.CiscoIpPhone.CreateText completed
2009:04:30::13:37:30(37): Warning: EPM Msg from etch csharp runtime: System.TimeoutException: timeout waiting for cisco.uc.cuae.legacy.CiscoIpPhone._result_sendExecute(1119480957)
   at Etch.Transport.DefaultDeliveryService.EndCall(Mailbox mb, XType responseType) in c:\BambooAgent\xml-data\build-dir\ETCH-RELEASE\binding-csharp\runtime\src\main\csharp\Etch\Transport\DefaultDeliveryService.cs:line 182
   at Etch.Support.RemoteBase._EndCall(Mailbox mb, XType responseType) in c:\BambooAgent\xml-data\build-dir\ETCH-RELEASE\binding-csharp\runtime\src\main\csharp\Etch\Support\RemoteBase.cs:line 81
   at cisco.uc.cuae.legacy.RemoteCiscoIpPhoneServer._Async._end_sendExecute(Mailbox _mb) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\RemoteCiscoIpPhoneServer.cs:line 2675
   at cisco.uc.cuae.legacy.RemoteCiscoIpPhoneServer.sendExecute(String sessionId, String message, String uRL, SendExecuteOptions options) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\RemoteCiscoIpPhoneServer.cs:line 1519
   at test7960.RemoteTest7960Server.sendExecute(String sessionId, String message, String uRL, SendExecuteOptions options) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\test7960\RemoteTest7960Server.cs:line 1336
   at test7960.ImplTest7960Client.incomingCall(String sessionId, IncomingCallOptions options) in C:\aragheb\hacking\Test7960\src\test7960\ImplTest7960Client.cs:line 72
   at cisco.uc.cuae.legacy.StubCallControlClient.<.cctor>b__1(DeliveryService _src, Object _obj, Who _sender, Message _msg) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\StubCallControlClient.cs:line 78
2009:04:30::13:37:30(79): Error: EAE Phone was able to process request, but replied with an error: <CiscoIPPhoneError Number="6" />
2009:04:30::13:37:30(79): Verbose: EPM Native action response message sent for: sendExecute
2009:04:30::13:37:30(79): Verbose: EPM Native action response message sent for: createText
2009:04:30::13:37:30(89): Verbose: EPM Response message: success
2009:04:30::13:37:30(89): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:30(89): Verbose: EPM Provider action response sent, method: Metreos.Providers.Http.SendResponse, message id: success
2009:04:30::13:37:30(98): Warning: EPM Msg from etch csharp runtime: System.NullReferenceException: Object reference not set to an instance of an object.
   at test7960.ImplTest7960Client.gotRequest(String sessionId, GotRequestOptions options) in C:\aragheb\hacking\Test7960\src\test7960\ImplTest7960Client.cs:line 111
   at cisco.uc.cuae.legacy.StubHttpClient.<.cctor>b__0(DeliveryService _src, Object _obj, Who _sender, Message _msg) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\StubHttpClient.cs:line 49
2009:04:30::13:37:52(46): Verbose: JTP Got 98(MediaEstablished) message from v7.0.
2009:04:30::13:37:52(46): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:04:30::13:37:52(46): Verbose: JTP Field: 6(DeviceType) = 3
2009:04:30::13:37:52(46): Verbose: JTP Field: 21(TxIP) =
2009:04:30::13:37:52(46): Verbose: JTP Field: 22(TxPort) = 0
2009:04:30::13:37:52(46): Verbose: JTP Field: 25(Codec) = 0
2009:04:30::13:37:52(46): Verbose: JTP Field: 26(Framesize) = 0
2009:04:30::13:37:52(46): Verbose: JTP Field: 40(CallId) = Z3nN8z25pkwlfc66
2009:04:30::13:37:52(46): Verbose: JTP Field: 41(To) = 8009
2009:04:30::13:37:52(46): Verbose: JTP Field: 42(From) = 4381
2009:04:30::13:37:52(46): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:04:30::13:37:52(46): Verbose: JTP Field: 66(JTapiCallId) = 39072/2
2009:04:30::13:37:52(48): Verbose: TM  MediaChanged (1000033): Tx Addr=<null>, RxAddr=192.168.102.20:20538, TxCodec=G711u:10, RxCodec=G711u:10.
2009:04:30::13:37:52(48): Info: TM  Call '1000033' switching to state map: MediaChanged
2009:04:30::13:37:52(48): Info: TM  Handling event (1000033): Metreos.CallControl.MediaChanged
2009:04:30::13:37:52(48): Verbose: TM  Executing state: 617769025cac:1000033:1 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(48): Verbose: TM  Executing state: 617769025cac:1000033:3 (SendStopTxToApp) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(48): Verbose: EPM Event message: Metreos.CallControl.StopTx
2009:04:30::13:37:52(48): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:52(48): Verbose: EPM Legacy event: Metreos.CallControl.StopTx sent to etch app: Test7960
2009:04:30::13:37:52(48): Verbose: TM  Executing state: 617769025cac:1000033:5 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(50): Verbose: TM  Executing state: 617769025cac:1000033:10 (UseMohMedia) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(50): Verbose: JTP Sent UseMohMedia. stackCallId:Z3nN8z25pkwlfc66
2009:04:30::13:37:52(50): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.CallControl.JTapi
2009:04:30::13:37:52(50): Verbose: TM  Executing state: 617769025cac:1000033:1000 (EndScript) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(50): Verbose: TM  Script ended for call '1000033'. Waiting for call service request...
2009:04:30::13:37:52(51): Verbose: JTP Got 25(Hangup) message from v7.0.
2009:04:30::13:37:52(51): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:04:30::13:37:52(51): Verbose: JTP Field: 6(DeviceType) = 3
2009:04:30::13:37:52(51): Verbose: JTP Field: 40(CallId) = Z3nN8z25pkwlfc66
2009:04:30::13:37:52(51): Verbose: JTP Field: 41(To) = 8009
2009:04:30::13:37:52(51): Verbose: JTP Field: 42(From) = 4381
2009:04:30::13:37:52(51): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:04:30::13:37:52(51): Verbose: JTP Field: 46(Cause) = NORMAL
2009:04:30::13:37:52(51): Verbose: JTP Field: 53(CallControlCause) = NORMAL
2009:04:30::13:37:52(51): Verbose: JTP Field: 66(JTapiCallId) = 39072/2
2009:04:30::13:37:52(51): Verbose: JTP About to remove call: 1000033
2009:04:30::13:37:52(51): Info: TM  Call '1000033' switching to state map: RemoteHangup
2009:04:30::13:37:52(51): Info: TM  Handling event (1000033): Metreos.CallControl.RemoteHangup
2009:04:30::13:37:52(51): Verbose: TM  Executing state: 617769025cac:1000033:1 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(53): Verbose: TM  Executing state: 617769025cac:1000033:5 (Wait) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(53): Verbose: TM  Executing state: 617769025cac:1000033:10 (DeleteConnection) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(53): Info: TM  Deleting connection: 1000033:16777502
2009:04:30::13:37:52(53): Verbose: MCP disconnect message sent successfully
2009:04:30::13:37:52(54): Verbose: MEP Sending success response (1:438)
2009:04:30::13:37:52(54): Verbose: TM  Enqueuing 'success' (1000033) response from Metreos.MediaControl
2009:04:30::13:37:52(54): Verbose: TM  Executing state: 617769025cac:1000033:15 (ForwardEventToApp) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(54): Verbose: EPM Event message: Metreos.CallControl.RemoteHangup
2009:04:30::13:37:52(54): Verbose: EPM Test7960-Default-1:  found in running scripts
2009:04:30::13:37:52(54): Verbose: EPM Legacy event: Metreos.CallControl.RemoteHangup sent to etch app: Test7960
2009:04:30::13:37:52(54): Verbose: TM  Executing state: 617769025cac:1000033:1000 (EndCall) - Metreos.CallControl.JTapi
2009:04:30::13:37:52(54): Info: TM  Call 20c5f24b-a3b7-42dc-b8d1-617769025cac:1000033 has ended due to normal call termination
2009:04:30::13:37:52(54): Verbose: TM  Call '1000033' ended. State path = 1, 5, 10, 15, 20, 25, 30, 35, 0, 1, 5, 10, 15, 20, 25, 30, 35, 40, 1000, 0, 1, 3, 5, 10, 1000, 0, 1, 5, 10, 15, 1000
2009:04:30::13:37:52(64): Warning: EPM Msg from etch csharp runtime: System.NotSupportedException: remoteHangup
   at test7960.BaseTest7960Client.remoteHangup(String sessionId, RemoteHangupOptions options) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\test7960\BaseTest7960Client.cs:line 400
   at cisco.uc.cuae.legacy.StubCallControlClient.<.cctor>b__2(DeliveryService _src, Object _obj, Who _sender, Message _msg) in C:\aragheb\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\StubCallControlClient.cs:line 103
2009:04:30::13:37:55(82): Warning: EPM Msg from etch csharp runtime: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2009:04:30::13:37:55(82): Info: EPM Etch app unregistered, name: Test7960, partition: Default
2009:04:30::13:37:55(82): Verbose: EPM Test7960-Default-1:  Remove script instance: 20c5f24b-a3b7-42dc-b8d1-617769025cac, Test7960, Default
2009:04:30::13:37:55(82): Verbose: EPM Session ended:
  sid: 20c5f24b-a3b7-42dc-b8d1-617769025cac
  plugin-0: Metreos.CallControl
  plugin-1: Metreos.MediaControl
  plugin-2: Metreos.CallControl.JTapi
  plugin-3: Metreos.Providers.Http

Main.cs
 
public static void Main(String[] args)
        {
            // TODO: Change to correct URI
            string uri = "tls://192.168.102.20:9000?TlsConnection.authReqd=false&filter=KeepAlive&KeepAlive.Count=5&Packetizer.maxPktSize=102400&TcpTransport.reconnectDelay=4000";
           
            RemoteTest7960Server server = Test7960Helper.NewServer( uri, null, new MainTest7960Client());
       
            // Connect to the service
            server._StartAndWaitUp( 4000 );

            // TODO: Insert Your Code Here

            String key = server.registerApplication("Test7960", "Default", "USERNAME", "PASSWORD");
            System.Console.WriteLine("registered and running");
            System.Console.Read();

            // Disconnect from the service
            server._StopAndWaitDown( 4000 );           
        }
 
Impl.cs
 
 EventWaitHandle ewh;

        public override void incomingCall(string sessionId, IncomingCallOptions options)
        {
            System.Net.ServicePointManager.Expect100Continue = false;

            // base.incomingCall(sessionId, options);

            AnswerCallResult acr;

            acr = server.answerCall(sessionId, options.callId, "", null);

            CreateExecuteOptions ceo;
            CreateExecuteResult cer;

            ceo = new CreateExecuteOptions();

            ceo.url1 = "http://192.168.102.20:8000/Test7960?metreosSessionId=" + sessionId;
           
            cer = server.createExecute(sessionId, ceo);

            Console.WriteLine("cer: " + cer.returnValue);

            SendExecuteOptions seo;
            SendExecuteResult ser;

            seo = new SendExecuteOptions();

            seo.password = "PASSWORD";
            seo.username = "USER";

            ser = server.sendExecute(sessionId, cer.xmlObject, acr.mediaTxIP, seo);

            Console.WriteLine("ser: " + ser.returnValue);

            ewh = new EventWaitHandle(false, EventResetMode.AutoReset);

            ewh.WaitOne();

            server.hangup(sessionId, acr.callId, null);
            server.removeCuaeSession(sessionId);

            Console.WriteLine("ended call");
        
        }

        public override void gotRequest(string sessionId, GotRequestOptions options)
        {
            // base.gotRequest(sessionId, options);

            CreateTextOptions cto;
            CreateTextResult ctr;

            cto = new CreateTextOptions();

            cto.prompt = "prompt";
            cto.text = "text";
            cto.title = "title";

            ctr = server.createText(sessionId, cto);

            Console.WriteLine("ctr: " + ctr.returnValue);

            SendResponseOptions sro;
            SendResponseResult srr;

            srr = server.sendResponse(sessionId, options.remoteHost, 200, "text/xml", ctr.xmlObject, "OK", null);

            Console.WriteLine("srr: " + srr.returnValue);

            ewh.Set();
        }

        public override void startRx(string sessionId, StartRxOptions options)
        {
            // base.startRx(sessionId, options);
        }

        public override void startTx(string sessionId, StartTxOptions options)
        {
            // base.startTx(sessionId, options);
        }

        public override void stopTx(string sessionId, StopTxOptions options)
        {
            // base.stopTx(sessionId, options);
        }
 
 
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
4/30/09 9:07 PM as a reply to Aaron Ragheb.
Error 6 is typically seen when the phone attempts to authorize a CiscoIPPhoneExecute request and cannot reach its configured authorization URL.  I would check that the services URL for the phone is valid (this can be modified both in Enterprise Parameters and on the individual phone config screen), and that the URL is reachable (no DNS issues) and active.
 
It may be useful to get a network packet capture from the phone's extra switch port (using something like Wireshark) to see exactly what is getting sent/received at the phone.  You can attach here if something looks amiss.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/1/09 2:50 PM as a reply to David Staudt.
David,
   Thanks for the reply.
 
The 7960 (and two other 7960s I tested with) have valid authorization urls.  The 7960s all fail.  Other phones on the network work fine.
 
The 7960s that I have only have a single switch port.
 
 


Error 6 is typically seen when the phone attempts to authorize a CiscoIPPhoneExecute request and cannot reach its configured authorization URL.  I would check that the services URL for the phone is valid (this can be modified both in Enterprise Parameters and on the individual phone config screen), and that the URL is reachable (no DNS issues) and active.
 
It may be useful to get a network packet capture from the phone's extra switch port (using something like Wireshark) to see exactly what is getting sent/received at the phone.  You can attach here if something looks amiss.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/1/09 4:39 PM as a reply to Aaron Ragheb.
David here is a capture off the phone's pc port.
 
phone is 192.168.60.28
 
packet 173 seems to indicate that authorization occured.
 
 
Attachments:
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/2/09 6:48 AM as a reply to Aaron Ragheb.
My read of the CUAE log is that the sendExecute request actually times out, and I guess CUAE reports that back to the app as an Error=6..?
 
This is borne out by the pcap, which shows that the Execute is sent to the phone, the phone requests/receives authorization, but never appears to make the HTTP request.
 
Not sure why the phone wouldn't make the request...helpful info might be:
 
- Phone model/firmware version and pcap of a working test
- Phone firmware version of the 7960 that fails
 
 
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/4/09 3:14 PM as a reply to David Staudt.
My read of the CUAE log is that the sendExecute request actually times out, and I guess CUAE reports that back to the app as an Error=6..?
 
This is borne out by the pcap, which shows that the Execute is sent to the phone, the phone requests/receives authorization, but never appears to make the HTTP request.
 
Not sure why the phone wouldn't make the request...helpful info might be:
 
- Phone model/firmware version and pcap of a working test
- Phone firmware version of the 7960 that fails
 

 
Hi David,
 
My 7960 exhibited this behavior and is running the same firmware version as Aaron (see his original post):
 
App Load ID: P00308001000
Boot Load ID: PC0303010200
Version: 8.0(10.0)
 
My 7975 is working successfully and is displaying this firmware version:
 
Load File: SCCP75.8-4-3S
App Load ID: jar75sccp.8-4-2-38.sbn
OS Load ID: cnu75.8-4-2-38.sbn
Boot Load ID: tnp75.8-3-1-21.bin
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/4/09 6:28 PM as a reply to Craig Thrall.
Looking again at the pcap, you can see at packet 209 that the phone makes an HTTP request to:
 
GET /Test7960?metreosSessionId=cfd39644-ca4d-4459-b833-9423bca99e79 HTTP/1.1
Host: 192.168.102.20:8000
User-Agent: Allegro-Software-WebClient/3.12
Connection: close
Accept: x-CiscoIPPhone/Text, x-CiscoIPPhone/Menu, x-CiscoIPPhone/IconMenu, x-CiscoIPPhone/Directory, x-CiscoIPPhone/Input, x-CiscoIPPhone/Image, x-CiscoIPPhone/GraphicMenu, x-CiscoIPPhone/Execute, x-CiscoIPPhone/Status, text/*
Accept-Language: en_US
Accept-Charset: iso-8859-1,utf-8;q=0.8
x-CiscoIPPhoneModelName: CP-7960G
x-CiscoIPPhoneSDKVersion: 4.0.1
x-CiscoIPPhoneDisplay: 133,65,2,G

But the host never responds.  So it looks like the phone is working ok, but the app never responds to the request...
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/8/09 4:36 PM as a reply to David Staudt.
David,
 
 I attach the mininal source files that exarcebate the number 6 problem.
 
Also, I attach a complete wireshark (allowing for the time out of the SendExecute, and the return of the error number 6).
 
Please note: the apache server never indicates an access for the /Test7960 url!
 
Also:
 
Packet # 527:  CUAE Server sends CiscoIpPhoneExecute to 7960
Packet # 558:  7960 authenticates user with CUCM
Packet # 578:  CUCM authorizes user
Packet # 619:  7960 Sends GET to CUAE Server
Packet #6743:  7960 Sends Error Number = "6" but I don't know in response to what.
 
And the App server log for this:
 
2009:05:08::10:25:34(93): Info: JTP Added JTapi call 1000061<->xxVq59rZpN8ghvwx
2009:05:08::10:25:34(95): Info: TM Loading IncomingCall state map to handle Metreos.CallControl.IncomingCall event
2009:05:08::10:25:34(95): Info: TM Processing new inbound call (1000061) from '4381' to '8009'
2009:05:08::10:25:34(95): Verbose: TM Executing state: b06fd5221b0e:1000061:1 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:34(95): Verbose: TM Executing state: b06fd5221b0e:1000061:5 (ForwardEventToApp) - Metreos.CallControl.JTapi
2009:05:08::10:25:34(95): Verbose: LM License check PASS: licensed: 100, running: 0.
2009:05:08::10:25:34(95): Verbose: EPM Event message: Metreos.CallControl.IncomingCall
2009:05:08::10:25:34(95): Verbose: EPM Test7960-Default-1: Running scripts added
2009:05:08::10:25:34(95): Verbose: EPM Legacy event: Metreos.CallControl.IncomingCall sent to etch app: Test7960
2009:05:08::10:25:35(06): Info: TM Enqueuing action (1000061): Metreos.CallControl.AnswerCall
2009:05:08::10:25:35(06): Verbose: TM Executing state: b06fd5221b0e:1000061:10 (AssumePreferredTxCodec) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(06): Info: TM Assuming preferred codec is Tx codec (1000061): G711u:20
2009:05:08::10:25:35(06): Verbose: TM Executing state: b06fd5221b0e:1000061:15 (ReserveConnection) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(06): Verbose: MCP connect message sent successfully
2009:05:08::10:25:35(06): Verbose: MEP Sending success response (1:9488)
2009:05:08::10:25:35(07): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.MediaControl
2009:05:08::10:25:35(07): Verbose: TM Executing state: b06fd5221b0e:1000061:20 (AcceptCall) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(07): Verbose: JTP Sent AcceptCall. stackCallId:xxVq59rZpN8ghvwx
2009:05:08::10:25:35(07): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.CallControl.JTapi
2009:05:08::10:25:35(07): Verbose: TM Executing state: b06fd5221b0e:1000061:25 (SetMedia) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(07): Verbose: JTP Got 99(Ringing) message from v7.0.
2009:05:08::10:25:35(07): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:05:08::10:25:35(07): Verbose: JTP Field: 6(DeviceType) = 3
2009:05:08::10:25:35(09): Verbose: JTP Field: 40(CallId) = xxVq59rZpN8ghvwx
2009:05:08::10:25:35(09): Verbose: JTP Field: 41(To) = 8009
2009:05:08::10:25:35(09): Verbose: JTP Field: 42(From) = 4381
2009:05:08::10:25:35(09): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:05:08::10:25:35(09): Verbose: JTP Field: 66(JTapiCallId) = 42559/2
2009:05:08::10:25:35(09): Verbose: JTP Set media for call (ID: 1000061) RxIp: 192.168.102.20 RxPort: 20494
2009:05:08::10:25:35(09): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.CallControl.JTapi
2009:05:08::10:25:35(10): Verbose: TM Executing state: b06fd5221b0e:1000061:30 (ForwardActionToProvider) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(10): Verbose: TM Forwarding Metreos.CallControl.JTapi.AnswerCall action to provider
2009:05:08::10:25:35(10): Verbose: JTP Sent AnswerCall. stackCallId:xxVq59rZpN8ghvwx, rxIP:192.168.102.20, rxPort:20494
2009:05:08::10:25:35(10): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.CallControl.JTapi
2009:05:08::10:25:35(10): Verbose: TM Executing state: b06fd5221b0e:1000061:35 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(10): Info: TM Call '1000061' switching to state map: IncomingCall_WaitTxRx
2009:05:08::10:25:35(10): Verbose: TM Executing state: b06fd5221b0e:1000061:1 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(12): Verbose: JTP Got 31(CallEstablished) message from v7.0.
2009:05:08::10:25:35(12): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:05:08::10:25:35(12): Verbose: JTP Field: 6(DeviceType) = 3
2009:05:08::10:25:35(12): Verbose: JTP Field: 40(CallId) = xxVq59rZpN8ghvwx
2009:05:08::10:25:35(12): Verbose: JTP Field: 41(To) = 8009
2009:05:08::10:25:35(12): Verbose: JTP Field: 42(From) = 4381
2009:05:08::10:25:35(12): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:05:08::10:25:35(12): Verbose: JTP Field: 46(Cause) = normal
2009:05:08::10:25:35(12): Verbose: JTP Field: 53(CallControlCause) = NORMAL
2009:05:08::10:25:35(12): Verbose: JTP Field: 66(JTapiCallId) = 42559/2
2009:05:08::10:25:35(12): Info: TM Enqueuing event (1000061): Metreos.CallControl.CallEstablished
2009:05:08::10:25:35(34): Verbose: JTP Got 98(MediaEstablished) message from v7.0.
2009:05:08::10:25:35(34): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:05:08::10:25:35(34): Verbose: JTP Field: 6(DeviceType) = 3
2009:05:08::10:25:35(34): Verbose: JTP Field: 21(TxIP) = 192.168.60.24
2009:05:08::10:25:35(34): Verbose: JTP Field: 22(TxPort) = 24688
2009:05:08::10:25:35(34): Verbose: JTP Field: 25(Codec) = 1
2009:05:08::10:25:35(34): Verbose: JTP Field: 26(Framesize) = 10
2009:05:08::10:25:35(34): Verbose: JTP Field: 40(CallId) = xxVq59rZpN8ghvwx
2009:05:08::10:25:35(34): Verbose: JTP Field: 41(To) = 8009
2009:05:08::10:25:35(34): Verbose: JTP Field: 42(From) = 4381
2009:05:08::10:25:35(35): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:05:08::10:25:35(35): Verbose: JTP Field: 66(JTapiCallId) = 42559/2
2009:05:08::10:25:35(35): Verbose: TM MediaEstablished (1000061): Tx Addr=192.168.60.24:24688, RxAddr=192.168.102.20:20494, TxCodec=G711u:10, RxCodec=G711u:10.
2009:05:08::10:25:35(35): Info: TM Enqueuing event (1000061): Metreos.CallControl.MediaEstablished
2009:05:08::10:25:35(35): Verbose: TM MediaEstablished (1000061): Tx Addr=192.168.60.24:24688, RxAddr=192.168.102.20:20494, TxCodec=G711u:10, RxCodec=G711u:10.
2009:05:08::10:25:35(35): Verbose: TM Executing state: b06fd5221b0e:1000061:5 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(37): Verbose: TM Executing state: b06fd5221b0e:1000061:10 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(37): Verbose: TM Executing state: b06fd5221b0e:1000061:15 (CreateConnection) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(39): Verbose: MCP connect message sent successfully
2009:05:08::10:25:35(42): Verbose: MEP Sending success response (1:9489)
2009:05:08::10:25:35(42): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.MediaControl
2009:05:08::10:25:35(43): Verbose: TM Executing state: b06fd5221b0e:1000061:20 (SendStartTxToApp) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(43): Verbose: EPM Event message: Metreos.CallControl.StartTx
2009:05:08::10:25:35(43): Verbose: EPM Test7960-Default-1: found in running scripts
2009:05:08::10:25:35(43): Verbose: EPM Legacy event: Metreos.CallControl.StartTx sent to etch app: Test7960
2009:05:08::10:25:35(43): Verbose: TM Executing state: b06fd5221b0e:1000061:25 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(45): Verbose: TM Executing state: b06fd5221b0e:1000061:30 (SendStartRxToApp) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(45): Verbose: EPM Event message: Metreos.CallControl.StartRx
2009:05:08::10:25:35(45): Verbose: EPM Test7960-Default-1: found in running scripts
2009:05:08::10:25:35(45): Verbose: EPM Legacy event: Metreos.CallControl.StartRx sent to etch app: Test7960
2009:05:08::10:25:35(45): Verbose: TM Executing state: b06fd5221b0e:1000061:35 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(46): Verbose: TM Executing state: b06fd5221b0e:1000061:40 (ForwardResponseToApp) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(46): Verbose: EPM Response message: success
2009:05:08::10:25:35(46): Verbose: EPM Test7960-Default-1: found in running scripts
2009:05:08::10:25:35(46): Verbose: EPM Provider action response sent, method: Metreos.CallControl.answerCall, message id: success
2009:05:08::10:25:35(48): Verbose: TM Executing state: b06fd5221b0e:1000061:1000 (EndScript) - Metreos.CallControl.JTapi
2009:05:08::10:25:35(48): Verbose: TM Script ended for call '1000061'. Waiting for call service request...
2009:05:08::10:25:35(56): Verbose: EPM Test7960-Default-1: native action: Metreos.Native.CiscoIpPhone.CreateExecute completed
2009:05:08::10:25:35(56): Verbose: EPM Native action response message sent for: createExecute
2009:05:08::10:25:35(67): Verbose: EPM starting send execute
2009:05:08::10:25:35(67): Verbose: EPM Test7960-Default-1: native action: Metreos.Native.CiscoIpPhone.SendExecute completed
2009:05:08::10:25:36(23): Verbose: EPM Event message: Metreos.Providers.Http.GotRequest
2009:05:08::10:25:36(23): Verbose: EPM Test7960-Default-1: found in running scripts
2009:05:08::10:25:36(23): Verbose: EPM Legacy event: Metreos.Providers.Http.GotRequest sent to etch app: Test7960
2009:05:08::10:25:36(31): Verbose: EPM Test7960-Default-1: native action: Metreos.Native.CiscoIpPhone.CreateText completed
2009:05:08::10:26:05(68): Info: TM Call '1000061' switching to state map: User_Hangup_Media
2009:05:08::10:26:05(68): Info: TM Handling action (1000061): Metreos.CallControl.Hangup
2009:05:08::10:26:05(68): Verbose: TM Executing state: b06fd5221b0e:1000061:1 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:26:05(70): Verbose: TM Executing state: b06fd5221b0e:1000061:3 (Wait) - Metreos.CallControl.JTapi
2009:05:08::10:26:05(70): Verbose: TM Executing state: b06fd5221b0e:1000061:5 (ForwardActionToProvider) - Metreos.CallControl.JTapi
2009:05:08::10:26:05(70): Verbose: TM Forwarding Metreos.CallControl.JTapi.Hangup action to provider
2009:05:08::10:26:05(70): Verbose: JTP Sent Hangup. stackCallId:xxVq59rZpN8ghvwx
2009:05:08::10:26:05(70): Verbose: JTP HandleTerminateCall-Wait for the hangup for call 1000061
2009:05:08::10:26:05(70): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.CallControl.JTapi
2009:05:08::10:26:05(70): Verbose: TM Executing state: b06fd5221b0e:1000061:15 (DeleteConnection) - Metreos.CallControl.JTapi
2009:05:08::10:26:05(70): Info: TM Deleting connection: 1000061:16777832
2009:05:08::10:26:05(70): Verbose: MCP disconnect message sent successfully
2009:05:08::10:26:05(71): Verbose: JTP Got 25(Hangup) message from v7.0.
2009:05:08::10:26:05(71): Verbose: JTP Field: 5(DeviceName) = Aaron10220test
2009:05:08::10:26:05(71): Verbose: JTP Field: 6(DeviceType) = 3
2009:05:08::10:26:05(71): Verbose: JTP Field: 40(CallId) = xxVq59rZpN8ghvwx
2009:05:08::10:26:05(71): Verbose: JTP Field: 41(To) = 8009
2009:05:08::10:26:05(71): Verbose: JTP Field: 42(From) = 4381
2009:05:08::10:26:05(71): Verbose: JTP Field: 43(OriginalTo) = 8009
2009:05:08::10:26:05(71): Verbose: JTP Field: 46(Cause) = NORMAL
2009:05:08::10:26:05(71): Verbose: JTP Field: 53(CallControlCause) = NORMAL
2009:05:08::10:26:05(71): Verbose: JTP Field: 66(JTapiCallId) = 42559/2
2009:05:08::10:26:05(71): Verbose: JTP About to remove call: 1000061
2009:05:08::10:26:05(73): Verbose: MEP Sending success response (1:9493)
2009:05:08::10:26:05(73): Verbose: TM Enqueuing 'success' (1000061) response from Metreos.MediaControl
2009:05:08::10:26:05(73): Verbose: TM Executing state: b06fd5221b0e:1000061:20 (ForwardResponseToApp) - Metreos.CallControl.JTapi
2009:05:08::10:26:05(73): Verbose: EPM Response message: success
2009:05:08::10:26:05(73): Verbose: EPM Test7960-Default-1: found in running scripts
2009:05:08::10:26:05(73): Verbose: EPM Provider action response sent, method: Metreos.CallControl.hangup, message id: success
2009:05:08::10:26:05(73): Verbose: TM Executing state: b06fd5221b0e:1000061:1000 (EndCall) - Metreos.CallControl.JTapi
2009:05:08::10:26:05(73): Info: TM Call 6f7bedac-5989-439d-a878-b06fd5221b0e:1000061 has ended due to normal call termination
2009:05:08::10:26:05(73): Verbose: TM Call '1000061' ended. State path = 1, 5, 10, 15, 20, 25, 30, 35, 0, 1, 5, 10, 15, 20, 25, 30, 35, 40, 1000, 0, 1, 3, 5, 15, 20, 1000
2009:05:08::10:26:06(14): Error: EAE Phone was able to process request, but replied with an error: <CiscoIPPhoneError Number="6" />
2009:05:08::10:26:06(14): Verbose: EPM Native action response message sent for: sendExecute
2009:05:08::10:26:06(14): Verbose: EPM Native action response message sent for: createText
2009:05:08::10:26:06(37): Warning: EPM Msg from etch csharp runtime: System.TimeoutException: timeout waiting for cisco.uc.cuae.legacy.CiscoIpPhone._result_createText(-2047208103)
at Etch.Transport.DefaultDeliveryService.EndCall(Mailbox mb, XType responseType) in c:\BambooAgent\xml-data\build-dir\ETCH-RELEASE\binding-csharp\runtime\src\main\csharp\Etch\Transport\DefaultDeliveryService.cs:line 182
at Etch.Support.RemoteBase._EndCall(Mailbox mb, XType responseType) in c:\BambooAgent\xml-data\build-dir\ETCH-RELEASE\binding-csharp\runtime\src\main\csharp\Etch\Support\RemoteBase.cs:line 81
at cisco.uc.cuae.legacy.RemoteCiscoIpPhoneServer._Async._end_createText(Mailbox _mb) in C:\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\RemoteCiscoIpPhoneServer.cs:line 2585
at cisco.uc.cuae.legacy.RemoteCiscoIpPhoneServer.createText(String sessionId, CreateTextOptions options) in C:\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\RemoteCiscoIpPhoneServer.cs:line 1384
at test7960.RemoteTest7960Server.createText(String sessionId, CreateTextOptions options) in C:\hacking\Test7960\etch-generated\etch-src\test7960\RemoteTest7960Server.cs:line 1321
at test7960.ImplTest7960Client.gotRequest(String sessionId, GotRequestOptions options) in C:\hacking\Test7960\src\test7960\ImplTest7960Client.cs:line 102
at cisco.uc.cuae.legacy.StubHttpClient.<.cctor>b__0(DeliveryService _src, Object _obj, Who _sender, Message _msg) in C:\hacking\Test7960\etch-generated\etch-src\cisco.uc.cuae.legacy\StubHttpClient.cs:line 49
2009:05:08::10:26:49(89): Info: R No handler registered for nontriggering event: Metreos.Providers.Http.SessionExpired
2009:05:08::10:28:49(90): Info: R No handler registered for nontriggering event: Metreos.Providers.Http.SessionExpired
2009:05:08::10:29:21(15): Warning: EPM Msg from etch csharp runtime: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
2009:05:08::10:29:21(15): Info: EPM Etch app unregistered, name: Test7960, partition: Default
2009:05:08::10:29:21(17): Verbose: EPM Test7960-Default-1: Remove script instance: 6f7bedac-5989-439d-a878-b06fd5221b0e, Test7960, Default
2009:05:08::10:29:21(17): Verbose: EPM Session ended:
sid: 6f7bedac-5989-439d-a878-b06fd5221b0e
plugin-0: Metreos.CallControl
plugin-1: Metreos.MediaControl
plugin-2: Metreos.CallControl.JTapi

2009:05:08::10:30:49(90): Info: R No handler registered for nontriggering event: Metreos.Providers.Http.SessionExpired
Attachments:
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/8/09 8:25 PM as a reply to David Staudt.
David,
   I modified the program slightly:
 
if you change the boolean condition in the if statement in incomingCall, I either use server.sendExecute(), or I "manually" create the CiscoIpPhoneExecute and send it.  I allow etch/cuae to trigger gotRequest().
 
Using the server object does not allow any of our 7960s to work!
 
Using the manual method, all phones work.
 
Something is wrong with what server.sendExecute() is creating for 7960s????
Attachments:
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/11/09 4:05 PM as a reply to Aaron Ragheb.
It might help if I attached the code!
Attachments: test7960.zip (3.2k)
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/11/09 4:59 PM as a reply to Aaron Ragheb.
Can you attach working and non-working pcaps?
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/11/09 9:02 PM as a reply to David Staudt.
Please find attached the binary used to do the test and 4 test runs.
 
Raw mode works (this is where I send the CiscoIpPhoneExecute not using etch).  It works for both 7960 and 7970.
Cuae mode does not work with the 7960 (where IU send the CiscoIpPhoneExecute using server.sendExecute()).
 
The 7960 is on 192.168.60.25
The 7970 is on 192.168.60.24
The CUAE server is on 192.168.102.20
 
I enclose pcaps and app server logs for each run plus the screen shot of the app.
Attachments: Test7960.zip (610.1k), Test7960src.zip (3.2k)
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/19/09 3:00 PM as a reply to Aaron Ragheb.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
5/22/09 6:09 AM as a reply to Aaron Ragheb.
Perhaps. We are following the issue on the other thread, we'll investigate it further and get back to you.
Flag Flag
Looking at the pcap for the CUAE/7960 test:
 
1) CUAE POSTs an Execute object to the phone
2) Phone makes the corresponding GET to CUAE
 
... 30 seconds ... no response from CUAE
 
3) Phone appears to time out waiting on the GET
4) Phone sends HTTP OK to the original POST, with Error=6
 
In both the CUAE/7970 test and the Raw/7960 test, CUAE seems to respond right away, and everything works fine.  I did notice that the 7970 did seem to go ahead and respond to the original POST with Success _before_ it even tried the corresponding GET.  So, it looks there are two items:
 
- 7960s appear to wait until their Execute command has completed, before they return CiscoIPPhoneResponse.  If the Execute command is a GET which is never responded to, the phone times out and returns Error=6.  In this case, the CUAE/app needs to return a timely response.
- 7970 and 7960 differ in their behaviour, where the 7970 responds immediately with Success before it tries the GET, where as above the 7960 waits and can potentially fail.
 
 
 
 
 
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/2/09 3:58 PM as a reply to David Staudt.
David,
 
Ok....let's look at your first two points:


Looking at the pcap for the CUAE/7960 test:
 
1) CUAE POSTs an Execute object to the phone
2) Phone makes the corresponding GET to CUAE
 
... 30 seconds ... no response from CUAE
 
 


 
point 1 occurs whether or not I use cuae to generate (and send)  xml, or if I do it by hand.
 
point 2's "no response" ONLY occurs when cuae generates (and sends) the xml.
 
I am unable to draw any conclusions from that.
 
Aaron
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/16/09 11:14 PM as a reply to David Staudt.
The need for a correct way to handle this is becoming critical.
 
Are there portions of the API that we shouldn't use?  Should xml creation and communication to the phone be done "raw" (as in test program attached above?).
 
 
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/17/09 12:43 AM as a reply to Aaron Ragheb.
It appears the CUAE engineering team is investigating the issue, with the indications pointing to a deadlock within CUAE for the SendExecute step when using 7940/60 phones.  Depending on the nature of the fix, it could require significant changes to the internals, so a quick fix is not currently anticipated (not definitive yet, though.)
 
If you are able to proceed using 'manual' HTTP POST as a workaround just for SendExecute, then that may be the best path for the short term.  Another proposed workaround (not confirmed to work yet) is to move the GotHTTPRequest handler (target of the Execute URL) to a different trigger or script which may allow threading to better occur.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/17/09 4:46 PM as a reply to David Staudt.
David,
   That's good news: you are seeing what I am talking about.
 
I would mention that with the CUAE 2.5 sr2 /etch/C# environment, that when I "stress" an application by hanging up in the middle of pending server.*() methods, I can see things as simple as server.createText() and server.createExecute() timeout!  These timeout can occur minutes AFTER the hangup has been processed.
 
It sounds suspiciously potentially connected.
 
Aaron
 
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/17/09 8:29 PM as a reply to David Staudt.
It appears the CUAE engineering team is investigating the issue, with the indications pointing to a deadlock within CUAE for the SendExecute step when using 7940/60 phones.  Depending on the nature of the fix, it could require significant changes to the internals, so a quick fix is not currently anticipated (not definitive yet, though.)
 
If you are able to proceed using 'manual' HTTP POST as a workaround just for SendExecute, then that may be the best path for the short term.  Another proposed workaround (not confirmed to work yet) is to move the GotHTTPRequest handler (target of the Execute URL) to a different trigger or script which may allow threading to better occur.


Hi David,
 
Is there a TAC incident or developer case we could look at to get some more info on the issue? Is it more widespread than just in the SendExecute API call?
 
Thanks,
 
Craig
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/18/09 9:05 PM as a reply to Craig Thrall.
The nature of the problem is due to the single serial message queue per app at the core of the CUAE, and the 7940/60 behaviour.  It is certainly possible that message queue blockages or deadlocks could cause problems in other areas unless the developer takes care.  I think what was surprising/tricky in this scenario is that the phone behaviour differed by model, and that SendExecute is a blocking/synchronous action.
 
One workaround being explored involves writing the CiscoIPPhoneExecute XML to a file, which is then served by the generic CUAE web server on port 80.  Hopefully this can be made available as a sample app.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
6/22/09 7:15 PM as a reply to David Staudt.
The nature of the problem is due to the single serial message queue per app at the core of the CUAE, and the 7940/60 behaviour.  It is certainly possible that message queue blockages or deadlocks could cause problems in other areas unless the developer takes care.  I think what was surprising/tricky in this scenario is that the phone behaviour differed by model, and that SendExecute is a blocking/synchronous action.
 
One workaround being explored involves writing the CiscoIPPhoneExecute XML to a file, which is then served by the generic CUAE web server on port 80.  Hopefully this can be made available as a sample app.

 
Hi David,
 
Can you give us more insight about this issue? We are working on developing multiple applications on CUAE 2.5. Could you give us some pointers on how we could avoid this?
 
Thanks,
 
Craig
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
7/23/09 10:57 AM as a reply to Craig Thrall.
Hi,
 
We are facing same issue. When we are tyring to push Text with some menu on 7940/7960 phones we are getting CIscoIPPhoneError =6.  I have seen answers available in the forum. Can you please tell me if any patch available from CIsco regarding this issue? Or we need to proceed with suggested workaround.
 
Thanks,
Umesh
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
7/23/09 3:28 PM as a reply to UP Chaurasia.
The problem summary and proposed solution (still under discussion
-----------
 Problem Definition :
SendExecute blocks the execution when used with 7940/7960,
 
Reason:
Each CUAE scripts runs in a single thread. 7940/7960 block "SendExecute" which posts a HTTP request to the app server and at the same time CUAE script that handles HTTP request is waiting for "SendExecute" to complete.
 
Symptoms:
This issue was observed on Cisco Ip Phone model 7940/7960. App-server threw a runtime error stating that the IP Phone responded with Cisco IP Phone Error 6.
 
Solution:
New API "SendExecuteAsync" which is a unblocking operation is created that will asynchronously execute "SendExecute" operation.
 
Target Version:
2.5.1(SR2)-Hotfix2
 -----------
Tentative time frame for HF2 appears to be August. Note the proposed solution is to add an asynchronous API, which will require some application changes to handle the result paths.
 
Some developers have been able to workaround the issue by first writing the contents of the Push request (for example a CiscoIPPhoneText object) to a file in the CUAE's static web pages, then using SendExecute to direct the phone to request the file from the CUAE web server.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
10/15/09 3:39 AM as a reply to David Staudt.
Hi,
 
Is there any HotFixes released by Cisco for CUAE 2.5.1 SR2?
When next release will come and what will be new features supported in next release?
 
Thanks,
Umesh
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
10/27/09 10:23 AM as a reply to UP Chaurasia.
Hi Umesh,
 
Yes a Hotfix has been created for this issue for CUAE 2.5.1-SR2. Kindly send us your mailing details if you need this hotfix.
 
Regards,
Rakesh.
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
10/27/09 10:44 AM as a reply to Rakesh Kumar.
Hi Rakesh,
 
Thanks for the hotfix for long pending issue.
 
My mail id is mailto:umesh.c@parsec-tech.com]
 
 
Regards,
Umesh
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
11/2/09 11:37 AM as a reply to UP Chaurasia.
Hi Rakesh,
 
I didn't receive the hotfix. Can you please send me that hotfix?
 
Regards,
Umesh
Flag Flag
RE: Please Help: CiscoIPPhoneError number = "6"
11/3/09 8:29 AM as a reply to UP Chaurasia.
Hi Umesh,
 
I am sorry to say that I was not aware of the process we follow for the Hotfixes.
 
There are two ways you can get the hotfix.
1. With the next CUAE release.
2. You need to contact Cisco TAC. They will guide you through the entire process.
 
Regards,
Rakesh.
Flag Flag