reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] INVITE-Replaces being sent with to-tag set

Hi Julio,

I assume you are using the redirectParticipant API.  I've just committed a fix for this.

Thanks,
Scott

On Thu, Apr 28, 2011 at 2:36 PM, Julio Cesar Esteves Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

Hi Kennard,

 

    You are right. Your advice worked OK!

         

    How I did it:

    In my implementation of InviteSessionHandler::onReadyToSend(InviteSessionHandle, SipMessage& msg) I added:

               

    if (msg.method() == REFER) 

    {

      if(msg.exists(h_ReferTo)  &&  msg.header(h_ReferTo).exists(p_tag))

        msg.header(h_ReferTo).remove(p_tag);

    }

               

Thank you!

Julio.

 

From: Kennard White [mailto:kennard_white@xxxxxxxxxxxx]
Sent: quarta-feira, 20 de abril de 2011 17:14
To: jcabezas@xxxxxxxxxxxxx
Cc: resiprocate-users@xxxxxxxxxxxxxxx
Subject: Re: [reSIProcate-users] INVITE-Replaces being sent with to-tag set

 

Hi Julio,

We had similar problem. Solution from Aron Rosenberg is:

You need to remove the tag param from the "ReferTo" paramater by calling <NameAddr>.uri().remove(p_tag)

; before passing it as the "referTo" paramater to dum->makeRefer(), or dum->makeOutOfDialogRequest() or InviteSession::refer()


Regards,
Kennard

On Wed, Apr 20, 2011 at 12:24 PM, Julio Cesar Esteves Cabezas <jcabezas@xxxxxxxxxxxxx> wrote:

Hi,

 

                I am using recon/resiprocate in my application to implement attended transfer, but I am having problem as the UA that receives REFER and sends INVITE-Replaces (the transferee) is inserting a to-tag in the To header;  that tag is a copy of the to-tag of the dialog to be replaced. Because of that the transfer target rejects that INVITE-Replaces with  481 Call/Transaction Does Not Exist.

                As I understand the UAC is not allowed to set any to-tag in the first INVITE.

                Casually I am testing my app together with eyebeam and X-Lite and as those also use reciprocate they exhibit the same wrong behavior. For example, SJPhone exhibits a correct behavior (not inserting that to-tag)

 

See below the SIP messages.

 

Best Regards,

Julio Cabezas.

 

 

INVITE sip:5903@xxxxxxxxx:18906;rinstance=53b7b2c736696a25;transport=udp SIP/2.0

Via: SIP/2.0/UDP 10.0.1.21:5060;branch=z9hG4bK-d8754z-126bf71a5e481b6a-1---d8754z-;rport

Via: SIP/2.0/UDP 10.0.1.11:7000;branch=z9hG4bK-d8754z-684cef569855f45e-1---d8754z-;rport=7000

Max-Forwards: 69

Contact: <sip:5902@xxxxxxxxx:7000>

To: <sip:5903@xxxxxxxxxxxxxx>;tag=a355263d

From: "5902"<sip:5902@xxxxxxxxxxxxxx>;tag=0955157e

Call-ID: ZDA3MDY4ZmViN2I4NzZiZTM0ODdkNGNmZTBkNTg4YjY.

CSeq: 2 INVITE

Session-Expires: 360

Min-SE: 90

Accept-Language: en

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

Content-Type: application/sdp

Proxy-Authorization: Digest username="5902",realm="neopath.com.br",nonce="12943758675:5c05150d28751395f731274c43839595",uri="sip:5903@xxxxxxxxxxxxxx",response="76d07f0600f59b7e824d25f26db2ba29",cnonce="7dd281983180bfb09b384a3312acc323",nc=00000001,qop=auth-int,algorithm=MD5

Supported: replaces, timer, norefersub, answermode, tdialog

User-Agent: Inovax SessionManager

Referred-By: "5901"<sip:5901@xxxxxxxxxxxxxx>

Replaces: ZjA3ZjcyNjIwMTQ5MGY3YTRjNmE4ZGUwZjc4ZmVjZTA.;to-tag=a355263d;from-tag=1d160069

Content-Length: 583

 

v=0

o=- 12943758701087479 12943758701087479 IN IP4 10.0.1.11

s=-

c=IN IP4 10.0.1.11

t=0 0

m=audio 40004 RTP/AVP 97 103 104 119 100 101 0 8 102 18 117 106 13 105 126

a=rtpmap:97 IPCMWB/16000

a=rtpmap:103 ISAC/16000

a=rtpmap:104 ISAC/32000

a=rtpmap:119 ISACLC/16000

a=rtpmap:100 EG711U/8000

a=rtpmap:101 EG711A/8000

a=rtpmap:0 PCMU/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:102 iLBC/8000

a=rtpmap:18 G729/8000

a=rtpmap:117 red/8000

a=rtpmap:106 telephone-event/8000

a=fmtp:106 0-15

a=rtpmap:13 CN/8000

a=rtpmap:105 CN/16000

a=rtpmap:126 CN/32000

a=ptime:20

a=sendrecv

 

 

SIP/2.0 481 Call/Transaction Does Not Exist

Via: SIP/2.0/UDP 10.0.1.21:5060;branch=z9hG4bK-d8754z-126bf71a5e481b6a-1---d8754z-;rport=5060

Via: SIP/2.0/UDP 10.0.1.11:7000;branch=z9hG4bK-d8754z-684cef569855f45e-1---d8754z-;rport=7000

To: <sip:5903@xxxxxxxxxxxxxx>;tag=a355263d

From: "5902"<sip:5902@xxxxxxxxxxxxxx>;tag=0955157e

Call-ID: ZDA3MDY4ZmViN2I4NzZiZTM0ODdkNGNmZTBkNTg4YjY.

CSeq: 2 INVITE

Accept-Language: en

Content-Length: 0

 


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

 


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/