Mailing List Archive: SIP phone registration

Here is a pretty basic question: Should we be using the address of our Publisher, or one of the subscribers as the registration point for our SIP phones?

Confidentiality Statement:
This email/fax, including attachments, may include confidential
and/or proprietary information and may be used only by the
person or entity to which it is addressed. If the reader of
this email/fax is not the intended recipient or his or her
agent, the reader is hereby notified that any dissemination,
distribution or copying of this email/fax is prohibited. If you
have received this email/fax in error, please notify the sender
by replying to this message and deleting this email or
destroying this facsimile immediately.

If you only have a pub and a sub, then either one. If you wanted to micro
manage device registrations, you could register some to one, and some to
the other. The benefit here is that if you have a fault on one of them,
only 50% of the devices are impacted....in theory. Otherwise, just
register all devices to one of them, and none to the other, to make things
easier from an administrative standpoint. Be sure to go through your Route
Lists and SIP Trunks and make sure Run on All Active Nodes is checked, so
that you can take advantage of the Route Local rule, which strives to keep
call processing on a single server, when dealing with RL and Trunk based
calls.

On Wed, Mar 11, 2020 at 11:40 AM Wesley Schochet via cisco-voip <
cisco-voip@puck.nether.net> wrote:

> Here is a pretty basic question: Should we be using the address of our
> Publisher, or one of the subscribers as the registration point for our SIP
> phones?
>
>
>
> Confidentiality Statement:
> This email/fax, including attachments, may include confidential
> and/or proprietary information and may be used only by the
> person or entity to which it is addressed. If the reader of
> this email/fax is not the intended recipient or his or her
> agent, the reader is hereby notified that any dissemination,
> distribution or copying of this email/fax is prohibited. If you
> have received this email/fax in error, please notify the sender
> by replying to this message and deleting this email or
> destroying this facsimile immediately.
> _______________________________________________
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>