ESock_client error 14

[raj_rr7]

Hi,

I am developing VoIP client for S60 3rd Edition FP1 devices. I found a strange problem of application crash with ESock_client panic 14. Application open RSocketSrv, open & start RConnection, initialize SIP stack and then send SIP Register. When transport failure callback is received, application shutdown SIP Stack and then restart RSocketSrv & RConnection. Sometimes before the completions of callback application crashes with ESock_client error 14. Here application just opens RSocketSrv & RConnection but does not send or receive data. What can be the reason in this scenario for ESock panic???

Thanks
Rajat

[kishore84]

Hi,

I am developing VoIP client for S60 3rd Edition FP1 devices. I found a strange problem of application crash with ESock_client panic 14. Application open RSocketSrv, open & start RConnection, initialize SIP stack and then send SIP Register. When transport failure callback is received, application shutdown SIP Stack and then restart RSocketSrv & RConnection. Sometimes before the completions of callback application crashes with ESock_client error 14. Here application just opens RSocketSrv & RConnection but does not send or receive data. What can be the reason in this scenario for ESock panic???

Thanks
Rajat

EBadDescriptor = 14, This panic numbers associated with Bad Descriptor. One common reason could be u r passing any temp variable (stack based) to asychrnous func(write() of RSocket) In such cases use heapbased meber or class variable instead.

[mayankkedia]

Hi,

SIP stack and then send SIP Register.Thanks
Rajat

How about the SIP register you would be sending the SIP register request, how are you doing that, what all data are you pasing and in what formats?

[raj_rr7]

Well, i am not sending any data using socket until application register with call manager and call established.

Regarding sending data in Register request, for NewL()
/**
* Two-phased constructor.
* @pre aAor != 0 &&
* aContact != 0
* @pre "Expires" parameter in aContact must be >= KSIPMinExpirationValue
* @param aConnection a SIP connection to be used
* @param aAor contains user's address-of-record to register;
* the ownership is transfered
* @param aContact contact(s) to be registered. The "expires" parameter
* indicates how long the client would like the binding to be
* valid.
* "expires" parameter value must be >= KSIPMinExpirationValue;
* the ownership is transfered
* @param aRefresh if set, created binding will be refreshed;
* the ownership is transfered
* @param aOutboundProxy an outbound proxy address;
* the ownership is transfered
* @param aRemoteUri if set, will be used in request-uri construction;
* the ownership is transfered
* @param aFrom From header, the ownership is transferred
* @return New object, ownership is transferred.
* @leave KErrArgument if aAor == 0, aContact == 0 or if "Expires"
* parameter in aContact is less than KSIPMinExpirationValue
*/
IMPORT_C static CSIPRegistrationBinding*
NewL(CSIPConnection& aConnection,
CSIPToHeader* aAor,
CSIPContactHeader* aContact,
CSIPRefresh* aRefresh=0,
CSIPRouteHeader* aOutboundProxy=0,
CUri8* aRemoteUri=0,
CSIPFromHeader* aFrom=0); // All the parameters provided properly

and put extension headers like user agent etc. before calling

/**
* Creates SIP REGISTER request, sends it to the given destination.
* Received 2xx response will create at least one registration
* binding.
* @pre Connection().State()==EActive
* @param aElements contains user SIP headers and content; the ownership
* is taken
* @return SIP REGISTER transaction; the ownership is transfered
* @leave KErrSIPMalformedMessage if aElements contains contact or
* expires headers
* @leave KErrSIPInvalidRegistrationState if already registered or
* registering is in progress or deregistering is in progress.
* @capability NetworkServices
*/
IMPORT_C CSIPClientTransaction*
RegisterL(CSIPMessageElements* aElements=0); // CSIPMessageElements is not NULL

The problem encounters when callback with error is received. Can it be some issue occurred in SIP stack as i shutdown and clean all the resources before the callback completes???

[kishore84]

The problem encounters when callback with error is received. Can it be some issue occurred in SIP stack as i shutdown and clean all the resources before the callback completes???

u have post ur header file which is not very much helpfull for detecting the pb.Also always put ur codes by using code tags and put minimal comments (only those are necessary).
abt the pb i think that could be a pb if u r cleaning ur resources before call back completes.