SIP INVITE Routing Problem

[bifihi]

Hi everybody!

I know this topic has been discussed in numerous threads already, but I am still having problems with my application not being able to receive SIP INVITEs.

My XML Capabilities description for the client looks like this:

_LIT8(KCapabilities,
"<SIP_CLIENT ALLOW_STARTING=\"YES\">\
<SIP_HEADERS>\
<ACCEPT_CONTACT value=\"*;+media=audio\"/>\
<ALLOW_EVENTS value=\"telephone-event\"/>\
<ACCEPT value=\"audio/basic\"/>\
<ACCEPT value=\"application/sdp\"/>\
</SIP_HEADERS>\
<SDP_LINES>\
<LINE name=\"m\" value=\"application 0 TCP SIP\"/>\
<LINE name=\"m\" value=\"audio 10001 RTP/AVP 98\">\
<MEDIA_ATTRIBUTE value=\"rtpmap:98 telephone-event/8000/1\"/>\
</LINE>\
</SDP_LINES>\
</SIP_CLIENT>");

The INVITE Message is this:

INVITE sip:974260@x.x.x.x SIP/2.0
To: <sip:974260@technikum.at>
From: "myname"<sip:974261@technikum.at>;tag=1d673777
Via: SIP/2.0/UDP x.x.x.x:5082;branch=z9hG4bK-d87543-aa3c120d6796121bc293-1-cHBjMzNkMmU3ODk2YjVkMzUwODIwOQ..-d87543-
Call-ID: 87a9ff286aeed0316a696d1fac39042d
CSeq: 427364045 INVITE
Contact: <sip:0rOeGDwXvsr25sSrSNbIT-das6jVdBX4921VJaXOTmzuewztDSGZB_PkNWuao729v6zFw..@x.x.x.x:5082>
Max-Forwards: 67
Content-Type: application/sdp
Supported: sec-agree
Content-Length: 206
Accept-Contact: *;+media=audio

v=0
o=- 1581227023 2115422058 IN IP4 193.154.103.162
s=Basic Call
c=IN IP4 193.154.103.162
t=0 0
m=audio 10844 RTP/AVP 0 3 98 101
a=fmtp:101 0-15
a=rtpmap:98 telephone-event/8000/1
a=sendrecv

As a result I get 480 Temporarily Unavailable. According to the INVITE routing figure published by Nokia (http://discussion.forum.nokia.com/fo...d.php?t=112633) this should happen if there is no matching Accept-Contact header.
But no matter what I write there, a unique parameter like "myapplication", whith or without "+", the result remains the same.

Why doesn't my application start?

Please help me out!

[tkot]

Hi bifihi!

First, before worrying if your XML is correct or not, make sure
that your plugin is REALLY loaded by SIP.

See this:
http://discussion.forum.nokia.com/fo...d.php?t=112694

In short:
-clean old implementation by manually deleting all files.
-check and double check you plugin UID's (typically, these are wrong!!)
-add lots of logs (or debug) to see that plugin is instantiated by SIP
-build from command line (for the first time!)

Once you are sure that plugin is loaded, then start to figure your XML!

[bifihi]

Thanks for the reply, you're right. The plug-in isn't even loaded, in "Epocwind.out" I find only the following lines:

-------------------------------------------------------------------------
90.460 SIP Client Resolver: Plug-in with 'default_data': 101F9515
90.460 SIP Client Resolver: Plug-in status: 0
90.460 SIP Client Resolver: ROM-based plug-ins count: 1
90.460 SIP Client Resolver: All plug-ins count: 1
-------------------------------------------------------------------------

I guess 101F9515 is the native client, my application is not there. I'm now trying to figure out why.
All the UIDs look OK, in fact I took the SIPExample and only tried to change the XML description in the plug-in, so I wonder why it doesn't load.......

[tkot]

Hi bihifi!

Guessed so

Read that link I gave above about manually cleaning your plugin binaries. Even your UID's are correct now, it does not mean that simply by re-compiling your code things start to work. That is, if you managed earlier screw up your environment by building the component with mixed UID's, you have to (with my experience) manually delete all old binaries before re-compiling.

Good luck!

Edit: Re-read your comments. If you really did not change anything (but XML) in sip examples plugin, then only reason I can figure out why plugin is not found, that you did not build that component from command line (abld build etc). Did you?

[bifihi]

Hi tkot!

Again you're right, I didn't build it from the command line. But now that I try it results in this:


-----------------------------------------------------------------------
C:\current\SIPExampleDebug\resolverplugin\Group>abld build winscw udeb
make -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\
resolverplugin\Group\EXPORT.make" EXPORT VERBOSE=-s
Nothing to do
make -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\
resolverplugin\Group\WINSCW.make" MAKEFILE VERBOSE=-s
perl -S makmake.pl -D \current\SIPExampleDebug\resolverplugin\Group\RESOLVERPLU
GIN WINSCW
ERROR: Unable to identify a valid CodeWarrior for Symbian OS installation
make: *** [MAKEFILERESOLVERPLUGIN] Error 255
make -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\
resolverplugin\Group\WINSCW.make" LIBRARY VERBOSE=-s
make -s -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug
\resolverplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.WINSCW" LIBRARY
make[1]: \Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\resolv
erplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.WINSCW: No such file or dire
ctory
make[1]: *** No rule to make target `\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\cu
rrent\SIPExampleDebug\resolverplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.
WINSCW'. Stop.
make: *** [LIBRARYRESOLVERPLUGIN] Error 2
make -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\
resolverplugin\Group\WINSCW.make" RESOURCE CFG=UDEB VERBOSE=-s
make -s -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug
\resolverplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.WINSCW" RESOURCEUDEB
make[1]: \Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\resolv
erplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.WINSCW: No such file or dire
ctory
make[1]: *** No rule to make target `\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\cu
rrent\SIPExampleDebug\resolverplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.
WINSCW'. Stop.
make: *** [RESOURCERESOLVERPLUGIN] Error 2
make -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\
resolverplugin\Group\WINSCW.make" TARGET CFG=UDEB VERBOSE=-s
make -s -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug
\resolverplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.WINSCW" UDEB
make[1]: \Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\resolv
erplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.WINSCW: No such file or dire
ctory
make[1]: *** No rule to make target `\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\cu
rrent\SIPExampleDebug\resolverplugin\Group\RESOLVERPLUGIN\WINSCW\RESOLVERPLUGIN.
WINSCW'. Stop.
make: *** [TARGETRESOLVERPLUGIN] Error 2
make -r -f "\Symbian\9.2\S60_3rd_FP1_10\EPOC32\BUILD\current\SIPExampleDebug\
resolverplugin\Group\WINSCW.make" FINAL CFG=UDEB VERBOSE=-s
-------------------------------------------------------------------------


I guess the problem is the following line:
ERROR: Unable to identify a valid CodeWarrior for Symbian OS installation

I found some threads on this error, still I'm not really sure what to do.

I'm using Carbide.C++ Professional with an academic license and s60 sdk 3rd fp1.

[bifihi]

OK, I resolved this by simply installing CodeWarrior. Lucky it's still available for download.....

The Plug-In is loaded now. Let's see if it works.

Thanks so far, tkot!!!!!

[tkot]

Good that you got it working

I have not done anything with carbide, so I have no clue how this problem should be solved on that environment. Anyway, I was supposed to check this tool anyhow in near future, so maybe I install that environment and try to figure this out.

Btw, one more hint for your XML. Since you use accept-contact header to match your invite to your appl, you do not need to specify those SDP lines in your XML. So, you can remove those from your XML and simplify it a bit. Then, when you for example add support for more codecs, you do not need to update this plugin!