[reSIProcate] Call disconnect due to re-invite timeout
Byron Campen
bcampen at estacado.net
Tue Sep 25 13:36:34 CDT 2007
This is interesting... By the time (1) is sent, it is too late for
DUM to redirect it. Sending a CANCEL and retrying the INVITE could
work, but this would not help if we were using an UPDATE instead.
Maybe we could treat 408 as a 503 with Retry-After==0 if our remote
contact has changed since the request was sent?
Do people think this is a corner-case that we want to solve for this
release?
Best regards,
Byron Campen
> Hi,
>
> I have a B2B based on resiprocate-1.1 sip stack. I am facing a
> problem of call disconnect because of re-invite timeout. The call
> flow is given below.
>
> DUM updates the remote party contact on getting a re-invite
> (message 4). But DUM does not cancel/redirect any previous request
> (message 1) sent by it. I believe DUM should atleast ignore any
> response of re-INVITE in such case.
>
> Can someone provide inputs to how this can be resolved?
>
>
>
> B2BUA client-A
>
> | |
>
> | |
>
> | |
>
> |(1) re-INVITE |
>
> |---------------->|
>
> |(2) REGISTER(new IP address)
>
> |<----------------|
>
> |(3) 200 OK |
>
> |---------------->|
>
> |(4) re-INVITE (from new IP)
>
> |<----------------|
>
> |(5) 491 Request Pending
>
> |---------------->|
>
> |(6) ACK |
>
> |<----------------|
>
> |(7) re-INVITE (retransmission to old IP of client-A)
>
> |---------------->|
>
> |Call disconnect due to timeout of
>
> | |
>
> |re-INVITE to client-A
>
> | |
>
>
>
> Regards,
>
> Mayur Ninama,
>
> Sr Software Engg.
>
> Varaha Systems
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.resiprocate.org
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070925/2bece137/attachment.htm>
More information about the resiprocate-devel
mailing list