[reSIProcate] Answer REFER failed, it's DUM bug ?
Scott Godin
slgodin at icescape.com
Tue Dec 18 08:27:02 CST 2007
If you don't pass a userProfile to dum to use for the new Invite then it
will use the user profile from the dialog set that the refer was
received on. It then uses the default from address of this profile in
the new invite. Do you have the default from address set on the
userprofile used for the original invite session?
Scott
From: resiprocate-devel-bounces at resiprocate.org
[mailto:resiprocate-devel-bounces at resiprocate.org] On Behalf Of Karlsson
Sent: Tuesday, December 18, 2007 6:01 AM
To: resiprocate-devel at list.resiprocate.org
Subject: [reSIProcate] Answer REFER failed, it's DUM bug ?
Hi, when I recevied a REFER, I using these source code to answer it,
the new INVITE has sent out, but with this new INVITE, the "From" header
is wrong likes this: From: <sip:>;tag=5a4a6f15
Did I missed something or it's DUM bug(I using the 1.2.2 reSIProcate)?
Thanks
void UserAgent::acceptRefer(long callID, const SipMessage & msg, const
SdpContents * sdpContent)
{
Lock lock(mDumMutex);
ReferTempHandleMap::iterator iter = mReferTempHandleMap.find(callID);
if (iter == mReferTempHandleMap.end())
{
return;
}
ServerSubscriptionHandle & h = iter->second.second;
h->send(h->accept(202));
mDum.send(mDum.makeInviteSessionFromRefer(msg, h, sdpContent));
mReferTempHandleMap.erase(iter);
}
REFER sip:testuser1 at 111.22.3.89:1758;rinstance=b153394fad217042 SIP/2.0
Record-Route: <sip:6.16.21.45:8000;lr=on;ftag=d53e2542>
Via: SIP/2.0/UDP 6.16.21.45:8000;branch=z9hG4bK158e.bb7f7395.0
Via: SIP/2.0/UDP
192.168.1.100:20308;received=111.22.3.89;branch=z9hG4bK-d87543-4913da7ac
768324e-1--d87543-;rport=1756
Max-Forwards: 69
Contact: <sip:testuser2 at 111.22.3.89:1756>
To: "testuser1"<sip:testuser1 at sip.exserver.com:8000>;tag=8e411f1b
From: "testuser2"< sip:testuser2 at sip.exserver.com:8000>;tag=d53e2542
Call-ID: YjYxNjkyZjM1YTkyZGNhNjkxYzQxNGEyNzU4MDE5OWY.
CSeq: 4 REFER
Proxy-Authorization: Digest username="testuser2",realm="
sip.exserver.com",nonce="4767a41bb33b44206b7f2939f6a04dbaf2278a26",uri="
sip:testuser1 at 111.22.3.89:1758;rinstance=b153394fad217042",response="ba5
51c4fe4d88090c09297ae1e241e09",cnonce="739ccfc024e894e8",nc=00000003,qop
=auth,algorithm=MD5
User-Agent: eyeBeam release 1004p stamp 31962
Refer-To: <sip:testuser3 at sip.exserver.com:8000>
Referred-By: <sip:testuser2 at 111.22.3.89:1756>
Content-Length: 0
Server-hint: NAThelper
Server-hint: loose_route
Server-hint: route4
Server-hint: route4-donat
NOTIFY sip:testuser2 at 111.22.3.89:1756 SIP/2.0
Via: SIP/2.0/UDP
192.168.1.100:5090;branch=z9hG4bK-d8754z-0a6a2d7e6831735b-1---d8754z-;rp
ort
Max-Forwards: 70
Route: <sip: 6.16.21.45:8000;lr;ftag=d53e2542>
Contact: <sip:testuser1 at 192.168.1.100:5090;rinstance=b153394fad217042>
To: "testuser2"< sip:testuser2 at sip.exserver.com:8000
<http://sip:testuser2@sip.exserver.com:8000> >;tag=d53e2542
From: "testuser1"<sip:testuser1 at sip.exserver.com:8000>;tag=8e411f1b
Call-ID: YjYxNjkyZjM1YTkyZGNhNjkxYzQxNGEyNzU4MDE5OWY.
CSeq: 2 NOTIFY
Content-Type: message/sipfrag
Subscription-State: active;expires=60
Event: refer
Content-Length: 22
SIP/2.0 100 Trying
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 6.16.21.45:8000;branch=z9hG4bK158e.bb7f7395.0
Via: SIP/2.0/UDP 192.168.1.100:20308;received= 111.22.3.89
<http://111.22.3.89>
;branch=z9hG4bK-d87543-4913da7ac768324e-1--d87543-;rport=1756
Record-Route: <sip:6.16.21.45:8000;lr;ftag=d53e2542>
Contact: <sip:testuser1 at 192.168.1.100:5090;rinstance=b153394fad217042>
To: "testuser1"<sip:testuser1 at sip.exserver.com:8000>;tag=8e411f1b
From: "testuser2"< sip:testuser2 at sip.exserver.com:8000
<http://sip:testuser2@sip.exserver.com:8000> >;tag=d53e2542
Call-ID: YjYxNjkyZjM1YTkyZGNhNjkxYzQxNGEyNzU4MDE5OWY.
CSeq: 4 REFER
Expires: 60
Content-Length: 0
INVITE sip:testuser3 at sip.exserver.com:8000 SIP/2.0
Via: SIP/2.0/UDP
192.168.1.100:5090;branch=z9hG4bK-d8754z-263a6a009d194575-1---d8754z-;rp
ort
Max-Forwards: 70
Contact: <sip:192.168.1.100:5090>
To: <sip:testuser3 at sip.exserver.com:8000>
From: <sip:>;tag=5a4a6f15
Call-ID: ODUwY2VjMTgzODM2ODUyNDNjZTk5OGFiNDQzZjEwNDQ.
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, NOTIFY, REFER,
REGISTER, SUBSCRIBE, MESSAGE, INFO
Content-Type: application/sdp
Referred-By: < sip:testuser2 at 111.22.3.89:1756>
Content-Length: 289
v=0
o=- 4730935 4730935 IN IP4 192.168.1.100
s=CALL
c=IN IP4 192.168.1.100
t=0 0
m=audio 20704 RTP/AVP 18 3 0 101
a=fmtp:18 annexb=no
a=fmtp:101 0-15
a=ptime:20
a=rtpmap:18 G729/8000
a=rtpmap:3 GSM/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20071218/a3ec82c9/attachment.htm>
More information about the resiprocate-devel
mailing list