> > consider the case where Alice has 2 phones registering > > sip:[EMAIL PROTECTED] on different ports of the gateway. > > > > Currently phone 1 may send out a REGISTER with, for example, > > > > From: <sip:[EMAIL PROTECTED]> > > Contact: <sip:[EMAIL PROTECTED]> > > > > And phone 2 may send out a REGISTER with > > > > From: <sip:[EMAIL PROTECTED]> > > Contact: <sip:[EMAIL PROTECTED]> > > > > This is good - the registrar has 2 registrations for Alice, with > > distinct contact addresses. All is good. > > > > With your proposed scheme phone 1 would send out a REGISTER with > > > > From: <sip:[EMAIL PROTECTED]> > > Contact: <sip:[EMAIL PROTECTED]> > > > > and phone 2 would send out a REGISTER with > > > > From: <sip:[EMAIL PROTECTED]> > > Contact: <sip:[EMAIL PROTECTED]> > > > > I don't think that the registrar would be aware that Alice has > > registered from 2 devices. > > Ok, I understand. > > Making it a little complex it could be: > > AoR = [EMAIL PROTECTED] => > Contact = user(_anything)[EMAIL PROTECTED] > > This is: the "Contact" URI should be: > > AoRusernamepart + "_" + anything + "*" + AoRdomain + "@" + device_IP > (where "_anything" is optional). > > > So in the case you tell: > > AoR = [EMAIL PROTECTED] => > Contact 1 = [EMAIL PROTECTED] > Contact 2 = [EMAIL PROTECTED] > > > Yes, there could be some issues if the AoR contains "*" or > "_", but nothing difficuly to solve with a convenient specification.
Good luck with that. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
