Hi!

I'm problems with invite using Nokia SIP plugin 4.0 with SIP server emulator. When I send invite from my own application it causes the SipServer in the other emulator to crash with Kern-Exec 3. This naturally causes system error -15 for the application.

I have checked that the .rss file for my Ecom plugin matches the SDP part of my invite message and the default_data UID is correct. Here is the log before the SipServer crash:

[0x0f20 13:39:24] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
REGISTER sip:193.17.231.201 SIP/2.0
Route: <sip:193.17.231.201;lr>
Via: SIP/2.0/UDP 193.17.231.206:5060;branch=z9hG4bKYp4QqRyM1g418
From: sip:player1@realm;tag=k9YQqUgHCw
To: sip:player1@realm
Contact: sip:player1@193.17.231.206;expires=3600
Supported: sec-agree
CSeq: 3054 REGISTER
Call-ID: MtEQq-P6s085sEu8Hz-qt8Cka5HOVV
Max-Forwards: 70
Content-Length: 0

[0x0f20 13:39:25] SipUdpHandle: 5021240 SendMessage: sending datagram:
SIP/2.0 200 OK
Contact: <sip:player1@193.17.231.206>;expires=3600
Call-ID: MtEQq-P6s085sEu8Hz-qt8Cka5HOVV
CSeq: 3054 REGISTER
From: <sip:player1@realm>;tag=k9YQqUgHCw
To: <sip:player1@realm>;tag=17409488
Via: SIP/2.0/UDP 193.17.231.206:5060;branch=z9hG4bKYp4QqRyM1g418
Content-Length: 0

[0x0f20 13:39:31] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
REGISTER sip:193.17.231.201 SIP/2.0
Route: <sip:193.17.231.201;lr>
Via: SIP/2.0/UDP 193.17.231.205:5060;branch=z9hG4bKr4MYwnzyciIAO
From: sip:player2@realm;tag=umIYwsOkh2
To: sip:player2@realm
Contact: sip:player2@193.17.231.205;expires=3600
Supported: sec-agree
CSeq: 3851 REGISTER
Call-ID: DNwYwj4Jww-N3BsIaNTMts9xs3Tfyu
Max-Forwards: 70
Content-Length: 0

[0x0f20 13:39:31] SipUdpHandle: 5021240 SendMessage: sending datagram:
SIP/2.0 200 OK
Contact: <sip:player2@193.17.231.205>;expires=3600
Call-ID: DNwYwj4Jww-N3BsIaNTMts9xs3Tfyu
CSeq: 3851 REGISTER
From: <sip:player2@realm>;tag=umIYwsOkh2
To: <sip:player2@realm>;tag=24551711
Via: SIP/2.0/UDP 193.17.231.205:5060;branch=z9hG4bKr4MYwnzyciIAO
Content-Length: 0

[0x0f20 13:39:38] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
INVITE sip:player2@realm SIP/2.0
Route: <sip:193.17.231.201;lr>
Via: SIP/2.0/UDP 193.17.231.206:5060;branch=z9hG4bKLjcQqTCin2fpj
From: sip:player1@realm;tag=lTQQqYTAai
To: sip:player2@realm
Supported: 100rel,sec-agree
Contact: sip:player1@193.17.231.206
CSeq: 3055 INVITE
Call-ID: M6IQqP1tXMvzLOAN7ZRW2xf6GxEKQJ
s: subj;255.255.255.255;999999999;9999
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 154
v=0
o=Name 1337002864 1337002865 IN IP4 193.17.231.206
s=SipSession
c=IN IP4 193.17.231.206
t=0 0
m=application 49152 TCP application
a=direction:both

[0x0f20 13:39:38] SipUdpHandle: 5047448 SendMessage: sending datagram:
INVITE sip:player2@193.17.231.205 SIP/2.0
Via: SIP/2.0/UDP 193.17.231.201;branch=z9hG4bK7df0c8592626758599bf195ed57e31b6
Route: <sip:193.17.231.201;lr>
Via: SIP/2.0/UDP 193.17.231.206:5060;branch=z9hG4bKLjcQqTCin2fpj
From: <sip:player1@realm>;tag=lTQQqYTAai
To: <sip:player2@realm>
Supported: 100rel
Supported: sec-agree
Contact: <sip:player1@193.17.231.206>
CSeq: 3055 INVITE
Call-ID: M6IQqP1tXMvzLOAN7ZRW2xf6GxEKQJ
Subject: subj;255.255.255.255;999999999;9999
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 154
v=0
o=Name 1337002864 1337002865 IN IP4 193.17.231.206
s=SipSession
c=IN IP4 193.17.231.206
t=0 0
m=application 49152 TCP application
a=direction:both

[0x0f20 13:39:39] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 193.17.231.201;branch=z9hG4bK7df0c8592626758599bf195ed57e31b6,SIP/2.0/UDP 193.17.231.206:5060;branch=z9hG4bKLjcQqTCin2fpj
To: sip:player2@realm
From: sip:player1@realm;tag=lTQQqYTAai
Call-ID: M6IQqP1tXMvzLOAN7ZRW2xf6GxEKQJ
CSeq: 3055 INVITE
Content-Length: 0

[0x0f20 13:39:39] SipUdpHandle: 5047448 SendMessage: sending datagram:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 193.17.231.206:5060;branch=z9hG4bKLjcQqTCin2fpj
To: <sip:player2@realm>
From: <sip:player1@realm>;tag=lTQQqYTAai
Call-ID: M6IQqP1tXMvzLOAN7ZRW2xf6GxEKQJ
CSeq: 3055 INVITE
Content-Length: 0

Could you tell me why the Kern-Exec 3 occurs before my application is informed about the invitation? Thanks!