Problem with SIP Resolver Ecom Plugin

[ecio83]

Hi all,

i can't solve problem with sip resolver plugin and so my sip application can't receive incoming requests.

I developed my app and ecom plugin with carbide c++ express v1.1, and i had problem with plugin. Then i found in this forum some posts about problems of carbide in building plugins, with errors in target directories and in .mmp file.

This is link of a thread about this problems:

http://discussion.forum.nokia.com/fo...ad.php?t=92181

I tried to do changes that suggested this thread, but nothing, i continue to receive '415 unsupported media type": my plugin was never loaded by emulator!

So i decided to change code developer, and i now i'm trying to develop plugin with CodeWarrior for Symbian v3.1, Personal Edition (90 days of free trial).
I checked target directories and they are ok.

But also developing plugin with cw, plugin isn't loaded when emulator starts; i'm using Symbian 3rd edition, FP1.

I post my mmp file and rsc file, but i think that they are right.

/////////resolverplugin.mmp//////////

TARGET SIPResolverPlugin.dll
TARGETTYPE PLUGIN

UID 0x10009D8F 0xA00001EC

SOURCEPATH ..\Src
SOURCE SIPResolverPluginDll.cpp
SOURCE SIPResolverPlugin.cpp

USERINCLUDE ..\Inc

SYSTEMINCLUDE \epoc32\include \epoc32\include\ecom

START RESOURCE ..\Data\A00001EC.rss
TARGET SIPResolverPlugin.rsc
END

LIBRARY euser.lib
LIBRARY ecom.lib
LIBRARY apparc.lib
LIBRARY apgrfx.lib

VENDORID 0

CAPABILITY NetworkServices LocalServices Location ReadUserData \
WriteUserData WriteDeviceData SwEvent ProtServ

/////A00001EC.rss///////

#include <RegistryInfo.rh>

RESOURCE REGISTRY_INFO theInfo
{
// UID for the DLL
dll_uid = 0xA00001EC;
// Declare array of interface info
interfaces =
{
INTERFACE_INFO
{
// UID of interface that is implemented
interface_uid = 0x102010DD;
implementations =
{
IMPLEMENTATION_INFO
{
implementation_uid = 0xA00001EC;
version_no = 1;
// SIPApp UID: Must match to the one SIPApp passes to CSIP::NewL.
default_data = "E42E5457";
}
};
}
};
}

Please, help me! I've tried hundreds of solutions, but plugin has never been loaded!

Thanks in advance,

Alessio

[satya3050]

Hi

I developed one application on sip using carbide only but it worked fine for me.
i dont know why its not working for you.
are you using importing mmp or bld.inf for importing your project?
If you are not created already create a bld.inf containing both the mmp files of Resolver and also main application.
try to run from command prompt. may be it will work.


Thanks &Regards
Satya

[ecio83]

Thanks, for your reply.

I have tried what you suggested, but i can't see good results.

I post file epocwind.out, where we could see that plugin probably is loaded when emulator starts, but for some cause there are problems.

///////epocwind.out////////

18.350 SIP Client Resolver: Plug-in with 'default_data': E42E5457
18.350 SIP Client Resolver: Plug-in status: 0
18.350 SIP Client Resolver: Plug-in with 'default_data': 101F9515
18.350 SIP Client Resolver: Plug-in status: 0
18.350 SIP Client Resolver: ROM-based plug-ins count: 2
...
18.365 SIP Client Resolver: All plug-ins count: 2

E42E5457 is Uid of my Sip App. Reading these lines, i suppose that plugin is correctly loaded.

...
90.850 SIP: Connection Manager::ReceivedFromNetwork, MESSAGE sip:alessio83@192.168.1.196 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.198;branch=z9hG4bK00b4f7a6f
90.850 SIP: Received data via UDP:
90.865 SIP: Received data:
90.865 SIP: MESSAGE sip:alessio83@192.168.1.196 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.198;branch=z9hG4bK00b4f7a6f
90.870 SIP: Incoming message:
90.870 SIP: From address: 192.168.1.198Port: 5060
90.885 Thread siprsvsrv.EXE::SIPClientResolverWorker00895D375B created @ 0x1227554 - Win32 Thread ID 0xb08
90.890 Thread siprsvsrv.EXE::SIPClientResolverWorker00895D375B Killed -1
90.890 RAknUiServer::ConnectAknServer(), handle 1079377959, EikAppUiServerThread
90.890 RAknUiServer::ConnectAknServer() end
90.895 Thread siprsvsrv.EXE::SIPClientResolverWorker006AFE9FF7 created @ 0x1229e3c - Win32 Thread ID 0xa0
90.895 Starter:EnvChange 4
90.895 TeUtl: ECN.HandleCallBack.<
90.895 TeUtl: ECN.DoHandleCallBack.<
90.895 TeUtl: ECN.DoHandleCallBack.>
90.895 TeUtl: ECN.HandleCallBack.>
90.895 TeUtl: ECN.HandleCallBack.<
90.895 TeUtl: ECN.DoHandleCallBack.<
90.895 TeUtl: ECN.DoHandleCallBack.>
90.895 TeUtl: ECN.HandleCallBack.>
90.895 CDRMClock::TimeChanged
90.895 Thread siprsvsrv.EXE::SIPClientResolverWorker006AFE9FF7 Killed -5
90.900 RAknUiServer::ConnectAknServer(), handle 1079377959, EikAppUiServerThread
90.900 RAknUiServer::ConnectAknServer() end
90.900 Starter:EnvChange 4
90.900 TeUtl: ECN.HandleCallBack.<
90.900 TeUtl: ECN.DoHandleCallBack.<
90.900 TeUtl: ECN.DoHandleCallBack.>
90.900 TeUtl: ECN.HandleCallBack.>
90.900 TeUtl: ECN.HandleCallBack.<
90.900 TeUtl: ECN.DoHandleCallBack.<
90.900 TeUtl: ECN.DoHandleCallBack.>
90.900 TeUtl: ECN.HandleCallBack.>
90.905 CDRMClock::TimeChanged ok
90.905 CDRMClock::TimeChanged
90.905 CDRMClock::TimeChanged ok
90.925 SIP: Outgoing data:
90.925 SIP: To address: 192.168.1.198Port: 5060
90.925 SIP: SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 192.168.1.198;branch=z9hG4bK00b4f7a6fe39dc11a5

Previous text is about receiving the SIP packet MESSAGE and the answer Unsupported media type.
Why 2 threads "siprsvsrv.EXE" are killed? One with '-1' and the other with '-5'?

Thanks in advance,

Alessio

[tkot]

Hi ecio83!

Could you pls send your apps client resolver XML and MESSAGE request so we can give you better help!

The resolver plugins are executed in their own threads -> 2 plugins -> 2 terminated threads. This is normal. Why other returns with -1 and other -5 ... dunno, but lets assume for the moment that thats also normal

[ecio83]

Hi, thanks for reply.

For 'apps client resolver XML', do you mean capabilities?

My capabilities are:

<SIP_CLIENT ALLOW_STARTING="NO">
<SIP_HEADERS>
<ACCEPT value="application/sdp"/>
<ACCEPT value="text/plain"/>
<ACCEPT value=""/>
</SIP_HEADERS>
<SDP_LINES>
<LINE name="m" />
</SDP_LINES>
</SIP_CLIENT>

and MESSAGE is:

Request-Line: MESSAGE sip:alessio83@192.168.1.196 SIP/2.0
Method: MESSAGE
[Resent packet : false]
Message Header
Via: SIP/2.0/UDP 192.168.1.198; branch=z9hG..................
From: KAKI <sip:kaki83@192.168.1.198>;tag=12137
To: <sip:alessio83@192.168.1.196>
Call-ID: 809ACACC-..............
CSeq: 108 MESSAGE
Contact: <sip:kaki83@192.168.1.198>
Max-Forwards: 70
Date: Fri, 27 Jul 2007 08:41:13 GMT
User-Agent: SIPPER for 3CX Phone
Content-Type: text/plain
Content-Length: 17
Message Body
Line-based text data: text/plain
example of text

C++ code of my resolver plugin is the same of SIP Example and my app UID is E42E5457.

Thanks in advance,

Alessio

[tkot]

Hi ecio83!

I believe your xml's syntax is wrong -> -5 from SIP.
This '<LINE name="m" /> is propably not right so either complete
that line or remove it all togeather.

So use:
<SIP_CLIENT ALLOW_STARTING="NO">
<SIP_HEADERS>
<ACCEPT value="application/sdp"/>
<ACCEPT value="text/plain"/>
<ACCEPT value=""/>
</SIP_HEADERS>
</SIP_CLIENT>

OR

<SIP_CLIENT ALLOW_STARTING="NO">
<SIP_HEADERS>
<ACCEPT value="application/sdp"/>
<ACCEPT value="text/plain"/>
<ACCEPT value=""/>
</SIP_HEADERS>
<SDP_LINES>
<LINE name="m" value="audio 0 RTP/AVP 0" />
</SDP_LINES>
</SIP_CLIENT>

Also, I see you have SIP_CLIENT ALLOW_STARTING = NO, so remember
to keep you appl running when receiving that MESSAGE.

Hope this helps!

[ecio83]

Hi tkot,

i try to implement what you suggest...but nothing changes!!

How could i debug my plugin (with carbide or codewarrior) to see what method (ConstructL, ChannelL, ConnectL...) has problems and crashes?

Thanks

Alessio

[tkot]

Hi!

OK ... first ... make sure that you are really using you new version of your plugin. These ECOMs are bit tricky (dlls clean OK, but old resource files may haunt you)!

Search files under /epoc32. Assume your plugin name is myappplugin (that you have in your mmp-file). You should now see many entries of myappplugin.* (dll, rsc, etc). These entries are for example under /epoc32/release, /epoc32/data/ and /epoc32/build.

Next try to clean everything using official tools. Havent use eclipse, but with CW you do this in you open project from 'Project'->'Remove object code'. Again, I recommend you to use for a while command line building (Its more reliable I feel , with that 'abld clean' and 'abld reallyclean' will do the job.

Now, do the search again for your myappplugin.* files. You still propably see some entries even you tried to clean them. So, next manually delete those files, so that there are no entries for myappplugin.*. Also get out of CW (or eclipse) and delete also those project files found under your plugins group directory (again, at least CW). So something like, myplugin/group/myplugin_Data. Delete this *_Data directory, it may also contain some old binaries.

OK. Now your enviroment should be clean from your old version of plugin. Its time to build & test the new one

I strongly recommend that you use command line tools to build you ecom in the beginning. In the group directory ... just 'bldmake bldfiles' and the 'abld build winscw udeb' -> new binaries are build. Testing ...

Its bit too difficult to teach debugging here, so I will not even try . Just simple flood you plugin code with debug prints so see where the execution goes. Use RDebug, it will print into that epocwind.out file. So, put in every (I mean every) function entry/exit logs and run & see logs. Something like this:

void CMyPlugin::WhatEverL()
{
RDebug::Print(_L("CMyPlugin::WhatEverL, entry"));
//do_whatever_here
RDebug::Print(_L("CMyPlugin::WhatEverL, exit"));
}

See what happens with these. If and when it still does not work, pls come back

[ecio83]

Hi tkot!

Thank you very much for your help!

I followed your steps, and when i did command line building i understood that uid2 of my plugin wasn't correct: it was 10009D8F but it must be 10009D8D.

Now it works!

Alessio