incoming request failed

[ukelady]

hello there

i tried to use the CSIPExample contained in the "Series 60 SIP Programmer's guide" document

with the example, i can register to the server succesfully, and receive the response from server (with incoming incomingresponse function)

but when i try to use some functions further...it failed.
i use two emulators and try to send invite message from one to another(ie. use player1 to invite player2)

player2 should receive the invite message from player1 by the incomingrequest function....but nomatter how i try , the incomingrequest function doesn't work /_\

is there anyone send requests from one emulator to another one successfully? PLEASE HELP ME!!

[ukelady]

there are some transfer infos of the emulators from server


[0x0fec 11:29:21] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
REGISTER sip:140.115.228.32 SIP/2.0
Route: <sip:140.115.228.32;lr>
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKeWNtWFfUdthIe
From: sip:player1@realm;tag=HwptWHWFvJ
To: sip:player1@realm
Contact: <sip:player1@140.115.228.31;comp=sigcomp>;expires=3600
Supported: sec-agree
CSeq: 403 REGISTER
Call-ID: WfhtWyuegduTX0rXwyWIn1qw8z9v1R
Max-Forwards: 70
Content-Length: 0

[0x0fec 11:29:21] SipUdpHandle: 5018200 SendMessage: sending datagram:
SIP/2.0 200 OK
Contact: <sip:player1@140.115.228.31;comp=sigcomp>;expires=3600
Call-ID: WfhtWyuegduTX0rXwyWIn1qw8z9v1R
CSeq: 403 REGISTER
From: <sip:player1@realm>;tag=HwptWHWFvJ
To: <sip:player1@realm>;tag=22168576
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKeWNtWFfUdthIe
Content-Length: 0

[0x0fec 11:29:21] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
INVITE sip:player2@realm SIP/2.0
Route: <sip:140.115.228.32;lr>
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
From: sip:player1@realm;tag=xrltWC8OUt
To: sip:player2@realm
Contact: <sip:player1@140.115.228.31;comp=sigcomp>
Supported: sec-agree
CSeq: 404 INVITE
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
Max-Forwards: 70
Content-Length: 0

[0x0fec 11:29:21] SipUdpHandle: 5047640 SendMessage: sending datagram:
INVITE sip:player2@140.115.228.30;comp=sigcomp SIP/2.0
Via: SIP/2.0/UDP 140.115.228.32;branch=z9hG4bKaf36e2938bb6e47f1e835a2bda7873cf
Route: <sip:140.115.228.32;lr>
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
From: <sip:player1@realm>;tag=xrltWC8OUt
To: <sip:player2@realm>
Contact: <sip:player1@140.115.228.31;comp=sigcomp>
Supported: sec-agree
CSeq: 404 INVITE
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
Max-Forwards: 69
Content-Length: 0

[0x0fec 11:29:21] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 140.115.228.32;branch=z9hG4bKaf36e2938bb6e47f1e835a2bda7873cf,SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
To: sip:player2@realm
From: sip:player1@realm;tag=xrltWC8OUt
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
CSeq: 404 INVITE
Content-Length: 0

[0x0fec 11:29:21] SipUdpHandle: 5047640 SendMessage: sending datagram:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
To: <sip:player2@realm>
From: <sip:player1@realm>;tag=xrltWC8OUt
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
CSeq: 404 INVITE
Content-Length: 0

[0x0fec 11:29:21] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 140.115.228.32;branch=z9hG4bKaf36e2938bb6e47f1e835a2bda7873cf,SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
To: sip:player2@realm;tag=Du8osETT10
From: sip:player1@realm;tag=xrltWC8OUt
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
CSeq: 404 INVITE
Content-Length: 0

[0x0fec 11:29:21] SipUdpHandle: 5047640 SendMessage: sending datagram:
SIP/2.0 415 Unsupported Media Type
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
To: <sip:player2@realm>;tag=Du8osETT10
From: <sip:player1@realm>;tag=xrltWC8OUt
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
CSeq: 404 INVITE
Content-Length: 0

[0x0fec 11:29:22] SipHandleManagerImpl: 4980808 ProcessUdpEvent: received datagram:
ACK sip:player2@realm SIP/2.0
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
Route: <sip:140.115.228.32;lr>
From: sip:player1@realm;tag=xrltWC8OUt
To: sip:player2@realm;tag=Du8osETT10
Supported: sec-agree
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
CSeq: 404 ACK
Max-Forwards: 70
Content-Length: 0

[0x0fec 11:29:22] SipUdpHandle: 5018200 SendMessage: sending datagram:
ACK sip:player2@140.115.228.30;comp=sigcomp SIP/2.0
Via: SIP/2.0/UDP 140.115.228.32;branch=z9hG4bKaf36e2938bb6e47f1e835a2bda7873cf
Via: SIP/2.0/UDP 140.115.228.31:5060;branch=z9hG4bKY_9tWJp4BdEBg
Route: <sip:140.115.228.32;lr>
From: <sip:player1@realm>;tag=xrltWC8OUt
To: <sip:player2@realm>;tag=Du8osETT10
Supported: sec-agree
Call-ID: q0htWwHv2Z_bS0rye4G7KA4bA9Vsn6
CSeq: 404 ACK
Max-Forwards: 69
Content-Length: 0