Makes sense Loren. Thanks for clarifying. And by ping group, do you mean
using voice class sip-options-keepalive
On Mon, Mar 5, 2018 at 1:51 PM Loren Hillukka
wrote:
> Local dns srv allowed priority and weight, whereas server-group only
> allowed priority, that I recall. Granted, you don't u
Nice tips Adam. The failovers to active endpoints was a pain. That retry
invites 2 was a must - the default was 6.
Loren
> On Mar 5, 2018, at 1:14 PM, Pawlowski, Adam wrote:
>
> Ed,
>
> Caveat on all this that I set this up a year or two ago so I could be wrong
> on some parts:
>
> This
Local dns srv allowed priority and weight, whereas server-group only allowed
priority, that I recall. Granted, you don't usually need weight, but some
customers desired that option.
Either can be used, and server-groups do add some benefits (can see better
up/down status, etc). Lately I have mov
Thank you Anthony very much. I really appreciated your guidance. I was able to
make work with the sip setup and incoming calls are now working fine but it
doesn't have caller ID. I have attached the logs.
below is the config.
control-plane
!
!
voice-port 0/2/0
trunk-group FXO_EM
no battery-
Loren,
Just out of curiosity, why didn't you just use session server groups?
Based on the config you shared, it looks like it would achieve the same
thing, but with less config, and not adding in the DNS stack within IOS.
Ed,
*Note, you cannot use DNS in server groups, so it's one or the other.
Ed,
Caveat on all this that I set this up a year or two ago so I could be wrong on
some parts:
This does DNS SRV lookup I believe first, then A. As long as you're in an IOS
version that supports SRV as that appeared somewhere in 15 I believe. We are
running 15.(4)3 M2.
I set up a number of SR
You can have your gw query your DNS server, and you have to add SRV records to
your central DNS server (like with the jabber entries required to get jabber
sign-in to work).
Here’s the example of doing local DNS to static entries on the gateway itself,
from the CVP 10 config guide. CVP is where
Hi everyone,
Hopefully a quick question - in a dial-peer on CUBE (16.3.5) how does
session target dns: resolve to an IP? I've never used DNS as target before
for this.
Does CUBE just do a query for the A record by default, or does it do a SRV
query by default? I have a SIP provider that wants to