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

Re: [reSIProcate-users] Problem with what I think is unattended transfer on a UA using resiprocate


Hi,

Appreciate that.

Unfortunately I'm not sure they understood the question as posed to them.

Thanks anyway.


On 2015-03-20 18:35, Scott Godin wrote:
Hi Simon,

This sounds like more a question for the softphone developer.  

Perhaps they are looking for errors
in DialogUsageManager::findInviteSession API call incorrectly.  This
API returns a std::pair with the 2nd arg as the ErrorStatusCode - but
the ErrorStatusCode should only be inspected if the first element
is InviteSessionHandle::NotValid() - sample code in
BasicClientCall::onNewSession shows this.

Scott

On Thu, Mar 12, 2015 at 6:02 PM, Simon Gregory <simon@xxxxxxxxxxxx
[7]> wrote:

HI,

SIMPLE (I HOPE) QUESTION ON TRANSFER TO A TARGET THAT HAS NOT YET
ANSWERED THE ORIGINAL CALL:

 

IF I SEND AN INVITE TO A USER AGENT THAT USES RECIPROCATE (AND
RHYMES WITH “MIA”), IT SENDS ME BACK A 180 RINGING...THEN
*BEFORE* THE OWNER ANSWERS I SEND AN INVITE-REPLACES WITH A
REPLACES
HEADER THAT REFERENCES THE CALL ID, FROM-TAG AND TO-TAG OF THE
ORIGINAL DIALOG (WHERE THE TO-TAG IS ACTUALLY THE ONE CREATED BY
“MIA” WHEN SENDING ME BACK THE 180).

I GET A 481 BACK FROM “MIA” TO THIS INVITE-REPLACES.

 

IF I ALLOW “MIA” TO ANSWER THE PHONE I.E. GENERATE A 200 OK
BEFORE I ATTEMPT THE INVITE-REPLACES ALL WORKS FINE AND THE SESSION
IS REPLACED.

 

 

CAN ANYONE TELL ME WHY RESIP IS TRYING - AND FAILING - TO MATCH
BASED ON THIS EXAMPLE - THE SEQUENCE IS:

1) INVITE TO “MIA” WITH CALLID A, FROM TAG B

2) “MIA” SENDS BACK 180 RINGING WITH CALLID A, FROM TAG B, TO
TAG C

3) ... WAIT A FEW SECONDS

4) INVITE TO “MIA” WITH CALLID D AND REPLACES HEADER INCLUDING

A;FROM-TAG=B;TO-TAG=C

 

MY QUESTION REALLY IS - WHAT SHOULD MY REPLACES HEADER CONTAIN IN
ORDER TO GET THE RESIP / “MIA” DIALOG MATCHING TO WORK ON THIS
"RINGING BUT NOT YET ANSWERED CALL" ?

MANY THANKS FOR ANY HELP.

 

P.S> THIS SEEMS TO FAIL ON ALL DESKTOP VERSION OF “MIA”

 

P.P.S> I HAVE CONSIDERED TRYING ALL THESE:

 



Replaces: 94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag=318de128
[1]



Replaces: 94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag
[2]=



Replaces: 94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag=0
[3]



Replaces: 94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag=318de128;early-only
[4]

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



Links:
------
[1]

mailto:94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag=318de128
[2] mailto:94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag [3] mailto:94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag=0
[4]

mailto:94ab8a63-81657ac1@10.0.0.97;from-tag=8b7615fb4286a409o0;to-tag=318de128;early-only
[5] mailto:resiprocate-users@xxxxxxxxxxxxxxx
[6] http://list.resiprocate.org/archive/resiprocate-users/
[7] mailto:simon@xxxxxxxxxxxx