On 3/10/17 2:49 PM, Dale R. Worley wrote:
Puneet Kumar writes:
If a UA uses different dialog-ID(say new Call-ID & No To header tag)
for REGISTER refresh with same contact address then it is allowed?
If not then please point out RFC section which blocks a UA from doing
Puneet Kumar writes:
> If a UA uses different dialog-ID(say new Call-ID & No To header tag)
> for REGISTER refresh with same contact address then it is allowed?
> If not then please point out RFC section which blocks a UA from doing it.
>
> In general does REGISTER refresh
Hi,
Sorry about the resend; however I wanted to mention that you also might
want to look at RFC 5626 (and RFC 5627) since it updates RFC 3261.
> -Original Message-
> From: Brett Tate [mailto:br...@broadsoft.com]
> Sent: Friday, March 10, 2017 6:35 AM
> To: 'Puneet Kumar';
> If a UA uses different dialog-ID (say new Call-ID & No To
> header tag) for REGISTER refresh with same contact
> address then it is allowed?
Yes; however you should read RFC 3261 section 10. For instance, section
10.2.4 indicates "UA SHOULD use the same Call-ID for all registrations
during a
Hi All,
I have a generic doubt on SIP registration request.
If a UA uses different dialog-ID(say new Call-ID & No To header tag) for
REGISTER refresh with same contact address then it is allowed?
If not then please point out RFC section which blocks a UA from doing it.
In general does REGISTER