To some extent this depends on how you define a UA.
In the case you describe, I would model what you have as a box
containing two different UAs.
Paul
Divya Sachdeva wrote:
> Thanks But i am little confused as from RFC 3261 Section 10 page 58
> it says
>
> Call-ID: All registrations from a UAC SHOULD use the same Call-ID
>
> header field value for registrations sent to a particular
>
> registrar.
>
> If the same client were to use different Call-ID values, a
>
> registrar could not detect whether a delayed REGISTER request
> might have arrived out of order.
>
> which means for
>
> registering userA for port 5060 and userY for port 5051 in different
> REGISTER request In
> that case both registrations will have the same call-id
>
>
>
>
> On 11/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
>>
>>
>>
>> *"Divya Sachdeva" <[EMAIL PROTECTED]>*
>> Sent by: [EMAIL PROTECTED]
>>
>> 11/01/2006 01:01 PM
>> To
>> [email protected] cc
>>
>> Subject
>> [Sip-implementors] Register Request
>>
>>
>>
>>
>>
>>
>> I hve a question regarding REGISTER request Can one UA register to the
>> same registrar with two names in order to
>> redirect different users to different ports?
>>
>> [Balaji Says]
>> Yes... U can do it with a single register request. Check the CONTACT
>> header in the Register request. You can place the different name in that.
>> [Balaji End]
>>
>> For example register as userA for port 5060 and as userY for port 5051? In
>> that case should both registrations have the same call-id?
>>
>> [Balaji Says]
>> I think it is not possible. Since for each register (for any new request)
>> new Call-ID is generated. If the same Call-ID repeated then it will consider
>> as Retransmission of that Request (As per RFC 3261 Brach-ID should be
>> validated to detect the Retransmission ,But as per old RFC 2543 the Call-ID
>> is used to detect the retramsmission.
>> [Balaji End]
>>
>>
>> Thanks and Regards
>> Divya
>> _______________________________________________
>> Sip-implementors mailing list
>> [email protected]
>> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>>
>>
>>
>> *********************** Aricent-Private ***********************
>>
>> *********************** Aricent-Private ***********************
>>
>> "DISCLAIMER: This message is proprietary to Aricent 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. Aricent accepts no responsibility for
>> loss or damage arising from the use of the information transmitted by this
>> email including damage from virus."
>>
>>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
