If you are on the registrar side of things, then by being sufficiently
liberal in what you accept you can make this work. If you examine the
specified procedures that a registrar is to follow, then the only real
dependence on callid and cseq is at the level of the binding of
individual contacts
Thanks Paul,
I'm actually on the other end of the deal. A customer is using a PBX that
registers multiple AORs.
It uses the same Call-ID for all the registrations which doesn't work
out-of-the-box with our PBX.
I'm just trying to get a grasp on what, if anything, their PBX is not doing
incorrectly
Vadim Berezniker wrote:
> Paul,
>
> Sorry, I still haven't got my hands around the proper terminology for SIP.
> It's sending out registrations for distinct AORs. Each registration has a
> distinct user in the To URI.
>
> Hope that clears it up.
Section 8.1.1.4 of 3261 says:
The Call-ID h
Paul,
Sorry, I still haven't got my hands around the proper terminology for SIP.
It's sending out registrations for distinct AORs. Each registration has a
distinct user in the To URI.
Hope that clears it up.
On Mon, Oct 20, 2008 at 9:29 AM, Paul Kyzivat <[EMAIL PROTECTED]> wrote:
>
>
> Vadim Be
Vadim Berezniker wrote:
> Hi,
>
> We have a client that sends multiple registrations.
> All of the registrations have the same Call-ID and and incremented CSeq.
> So far, I believe the behavior is correct. (Although in practice, every
> other device I've seen uses a unique Call-ID for each uniqu
Hi,
We have a client that sends multiple registrations.
All of the registrations have the same Call-ID and and incremented CSeq.
So far, I believe the behavior is correct. (Although in practice, every
other device I've seen uses a unique Call-ID for each unique registration).
It does not however w
