[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sip-implementors
Subject:    [Sip-implementors] Clarification about REGISTER call-flow
From:       vganapathy () hss ! hns ! com
Date:       2003-02-25 6:19:40
Message-ID: 65256CD8.0021A989.00 () sampark ! hss ! hns ! com
[Download RAW message or body]


Hi,

In the draft-ietf-sipping-basic-call-flows-01.txt
the section "2.1 Successful New Registration"
shows the call-flow for a successful registration
after a challenge cycle between the registrar and
the UA. In the re-tried REGISTER message the CSeq
has been incremented and the same call-id is used.
But the From-Tag has been changed. Should the From
tag be different in all the resubmitted requests.
If so section "3.2 Session Establishment Through
Two Proxies"  shows the resubmitting of INVITE
request after a 407. There the from tag has been
retained. Is the behaviour for REGISTER request
a special case or its a typo.

In short, in a resubmitted request after a challenge
should the From Tag be the same as the original
request. SIP Rfc is clear on incrementing CSeq but
not about re-using the From tag. It will be of help
if somebody can clarify or provide any poniters.


Thnx & Regards,
- Vijay






This message is proprietary to Hughes Software Systems Limited (HSS) and is
intended solely for the use of the individual to whom it is addressed.  It
may contain privileged or confidential information and should not be
circulated or used for any purpose other than for what it is intended.  If
you have received this message in error, please notify the originator
immediately.  If you are not the intended recipient, you are notified that
you are strictly prohibited from using, copying, altering, or disclosing
the contents of this message.  HSS accepts no responsibility for loss or
damage arising from the use of the information transmitted by this email
including damage from virus.



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic