Here's a solution for numeric dialing and alpha dialing.
An example with 2 phones calling each other. This can be adapted to point to a gateway instead of another phone:
mac address = 003094C283B9
IP address = 10.10.1.1
SIP address for Line1 = 45731
SIP address for Line2 = user1
mac address = 003094C283A7
IP address = 10.10.1.2
SIP address for Line1 = 45732
SIP address for Line2 = user2
In the SIP.cnf file for both phones make sure to set the proxy_register field to 0 and the following for the line appearance config (everything else should be standard SIP phone config):
# Phone Number
# Phone Number
Basically, we configure the line appearances to point directly to the IP address of the other phone. In this case, we configured 2 line appearances to point to the same destination IP, one for numeric dialing and one for alpha dialing. You could configure each line appearance to point to a different endpoint, if that's what you want.
The same premise applies when configuring an IP phone to point to a gateway.
With IP phone to GW config, the GW would need a dial-peer for each phone. You can't configure a bunch of VoIP dial-peers and point the phone to the GW and make phone to phone calls as IOS does not support tandeming of VoIP calls, but you could place calls to/from the PSTN.
Expanding on the above example, on SIP7960_1 I could configure line3 to point to a SIP gateway and make calls to the PSTN using that line appearance, but to call to SIP7960_2, I would need to use either line1 or line2.
We can see that the DNS queries are indeed SRV records, but even without SRV records in my database, the hostname eventually resolves. I don't know how many times the phone will retry for the SRV records, but it will eventually fall back to A records, and it will resolve very quickly (no noticeable delay).
You can run into some delay problems if you're running multiple DNS servers and the first server is unresponsive. The reason it resolves so quickly in the above case is that the phone is getting a reply from the DNS server, but it's getting an NXDOMAIN reply for the SRV records, not a NOERROR reply (success), so it knows to retry. In the event of a downed DNS server, the device has a nontrivial timeout before retrying, so it will introduce delay.
Using IP addresses is easiest in our lab, only because DNS management is an additional step and usually not necessary for our purposes, but DNS is a realistic expectation in deployments. With a single DNS server, everything works great, even without the SRV records.
For redundancy, the recommendation, instead of using multiple DNS servers configured in the phone to provide redundancy, is to use some kind of load balancing device in front of your DNS cluster (i.e. Cisco CSS-11xxx) so you would provide a single DNS IP to the phone and the SLB device would handle the load balancing.
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...
This document describe how DST changes and how time changes are
implemented in DST. Daylight Saving Time (DST) is the practice of
setting the clocks forward 1 hour from standard time during the summer
months, and back again in the fall, in order to make b...