1. Brekeke Product Name and version:
Brekeke SIP verser 2.4.8.6/286.3
2. Java version:
1.6.0_29
3. OS type and the version:
Windows7
4. UA (phone), gateway or other hardware/software involved:
Phone
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :
Pattern1
6. Your problem:
structure: User A - Brekeke SIP server - User B
Descriptions:
1. User A send INVITE with SIP body for Instant Messenger(Content-length is 728)
2. Brekeke server receive the SIP message from User A
3. Brekeke server send the received SIP message to User B without SIP body. (Content-length is only 10 )
4. User B get SIP header only without SIP body.
Question: How to keep the SIP body without loss during transaction between two users??
I'm attaching some parts of SIP message for clear.
[ SIP message User A ]
INVITE sip:+12345678@test.test.aa;user=phone SIP/2.0
.
.
.
Contact: <sip+87654321@111.222.333.444:5060;transport=TCP>;+g.oma.sip-im
Via: SIP............
content-Type: multipart/mixed;boundry="++"
content-Length: 728
--++
content-type: application/sdp
content-Length: 268
v=0
0=haha-IMS-UE........
.
.
.
--++
content-Type: message/cpim
content-Length: 333
From:....
.
.
.
content-Type: message/cpim
content-Length: 4
hihi
--++
[ Brekeke SIP server is sending the received SIP message to User B ]
INVITE sip:+12345678@test.test.aa;user=phone SIP/2.0
.
.
.
Contact: <sip+87654321@444.333.222.111:50498;transport=TCP>;+g.oma.sip-im
Via: SIP............
content-Type: multipart/mixed;boundry="++"
content-Length: 10 << there is no SIP body ;(
--"++"
SIP body is gone by Brekeke SIP server
Moderator: Brekeke Support Team
From the packet information you pasted, it seems your SIP client doesn't meet the RFC( 1341,2046) requirements.
This is the reason of the problem.
Follow the RFC correctly.
----------------------------
Each part starts with an encapsulation boundary, and then contains a body part
consisting of header area, a blank line, and a body area.
----------------------------
This is the reason of the problem.
Follow the RFC correctly.
----------------------------
Each part starts with an encapsulation boundary, and then contains a body part
consisting of header area, a blank line, and a body area.
----------------------------
Fixed but, issue is still ongoing.
[ SIP message User A ]
INVITE sip:+12345678@test.test.aa;user=phone SIP/2.0
.
.
.
Contact: <sip+87654321@111.222.333.444:5060;transport=TCP>;+g.oma.sip-im
Via: SIP............
content-Type: multipart/mixed;boundry="++"
content-Length: 728
--++
content-type: application/sdp
content-Length: 268
v=0
0=haha-IMS-UE........
.
.
.
--++
content-Type: message/cpim
content-Length: 333
From:....
.
.
.
imdn.Disposition-Notification: positive-delivery, negative-delivery, display
content-Type: message/cpim
content-Length: 4
hihi
--++
[ Brekeke SIP server is sending the received SIP message to User B ]
INVITE sip:+12345678@test.test.aa;user=phone SIP/2.0
.
.
.
Contact: <sip+87654321@444.333.222.111:50498;transport=TCP>;+g.oma.sip-im
Via: SIP............
content-Type: multipart/mixed;boundry="++"
content-Length: 10 << there is no SIP body ;(
--"++"
INVITE sip:+12345678@test.test.aa;user=phone SIP/2.0
.
.
.
Contact: <sip+87654321@111.222.333.444:5060;transport=TCP>;+g.oma.sip-im
Via: SIP............
content-Type: multipart/mixed;boundry="++"
content-Length: 728
--++
content-type: application/sdp
content-Length: 268
v=0
0=haha-IMS-UE........
.
.
.
--++
content-Type: message/cpim
content-Length: 333
From:....
.
.
.
imdn.Disposition-Notification: positive-delivery, negative-delivery, display
content-Type: message/cpim
content-Length: 4
hihi
--++
[ Brekeke SIP server is sending the received SIP message to User B ]
INVITE sip:+12345678@test.test.aa;user=phone SIP/2.0
.
.
.
Contact: <sip+87654321@444.333.222.111:50498;transport=TCP>;+g.oma.sip-im
Via: SIP............
content-Type: multipart/mixed;boundry="++"
content-Length: 10 << there is no SIP body ;(
--"++"