Wael-Fathallah / imsdroid

Automatically exported from code.google.com/p/imsdroid
0 stars 0 forks source link

Trying to use Action Config class with Reject api ,unable to add config.addheader #323

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response

What steps will reproduce the problem?
1. send a invite from the sipp
2.IMS droid recives invite and transcation layer sends 100 trying 
3.then 180 ringing is sent 
4.i want to sent 302 temprory unavailable so i am preparing the response and 
sending using msession.reject(config )
5.but i am unable to add contact header in it 
response line is being set to 302 but config.addheader function is not adding 
the required header 

INVITE sip:johndoe@10.76.205.182 SIP/2.0
Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-0-26785
From: rahul <sip:rahul@10.76.205.240>;tag=a57ddeb8bdd6ff12
To: <sip:johndoe@10.76.205.182>
Contact: <sip:rahul@10.76.205.240:5060;transport=UDP;user=phone>
Supported: replaces
Call-ID: 1-26785@10.76.205.240
CSeq: 55257 INVITE
User-Agent: Grandstream BT100 1.0.6.7
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE
Content-Type: application/sdp
Session-Expires: 3600
Content-Length: 197

v=0
o=doubango 1983 678901 IN IP4 10.0.2.15
s=-
c=IN IP4 10.0.5.16
t=0 0
m=audio 27946 RTP/AVP 8 101
a=ptime:20
a=rtpmap:8 PCMA/8000/1
a=rtpmap:101 telephone-event/8000/1
a=fmtp:101 0-15SIP/2.0 

100 Trying (sent from the Transaction Layer)
Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-0-26785
From: "rahul "<sip:rahul@10.76.205.240>;tag=a57ddeb8bdd6ff12
To: <sip:johndoe@10.76.205.182>
Call-ID: 1-26785@10.76.205.240
CSeq: 55257 INVITE
Content-Length: 0

SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-0-26785
From: "rahul "<sip:rahul@10.76.205.240>;tag=a57ddeb8bdd6ff12
To: <sip:johndoe@10.76.205.182>;tag=609025508
Contact: <sip:johndoe@10.0.2.15:50844;transport=udp>

Call-ID: 1-26785@10.76.205.240

CSeq: 55257 INVITE

Content-Length: 0

Allow: ACK, BYE, CANCEL, INVITE, MESSAGE, NOTIFY, OPTIONS, PRACK, REFER, UPDATE

SIP/2.0 302 Moved Temporarily!!

Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-0-26785

From: "rahul "<sip:rahul@10.76.205.240>;tag=a57ddeb8bdd6ff12

To: <sip:johndoe@10.76.205.182>;tag=609025508

Call-ID: 1-26785@10.76.205.240

CSeq: 55257 INVITE

Content-Length: 0

Reason: SIP; cause=302; text="Moved Temporarily!!"

ACK (null) SIP/2.0

Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-4-26785

From: rahul <sip:rahul@10.76.205.240;user=phone>;tag=a57ddeb8bdd6ff12

To: <sip:johndoe@10.76.205.182>;tag=609025508

Contact: <sip:rahul@10.76.205.240:5060;transport=UDP;user=phone>

Call-ID: 1-26785@10.76.205.240

CSeq: 55257 ACK

User-Agent: Grandstream BT100 1.0.6.7

Max-Forwards: 70

Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE

Content-Length: 0
2.
3.

What is the expected output? What do you see instead?
got this response
SIP/2.0 302 Moved Temporarily!!

Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-0-26785

From: "rahul "<sip:rahul@10.76.205.240>;tag=a57ddeb8bdd6ff12

To: <sip:johndoe@10.76.205.182>;tag=609025508

Call-ID: 1-26785@10.76.205.240

CSeq: 55257 INVITE

Content-Length: 0

Reason: SIP; cause=302; text="Moved Temporarily!!"

expected :
SIP/2.0 302 Moved Temporarily!!

Via: SIP/2.0/UDP 10.76.205.240:5060;branch=z9hG4bK-26785-1-0-26785

From: "rahul "<sip:rahul@10.76.205.240>;tag=a57ddeb8bdd6ff12

To: <sip:johndoe@10.76.205.182>;tag=609025508

Call-ID: 1-26785@10.76.205.240

CSeq: 55257 INVITE

Content-Length: 0
contact : <the uri which i have given >
Reason: SIP; cause=302; text="Moved Temporarily!!"

What version of the product are you using? On what operating system?
android 4.0.3  windows 64 bit machine 

Please provide any additional information below.

Original issue reported on code.google.com by ajithks...@gmail.com on 23 Jan 2012 at 8:36