Incoming VoIP Features: Difference between revisions

Incoming VoIP Features (view source)

Revision as of 12:59, 4 September 2020

889 bytes added , 4 September 2020

m

Removing reverence to Special, "unsupported" tag feature:

Aa-shaun

autoreview, Bureaucrats, editor, emailconfirmed, Administrators

8

edits

Revision as of 20:00, 7 September 2015 (view source) AA-Andrew (talk \| contribs) m (→‎More about SRV Records) ← Older edit		Revision as of 12:59, 4 September 2020 (view source) Aa-shaun (talk \| contribs) m (Removing reverence to Special, "unsupported" tag feature:) Newer edit →
(12 intermediate revisions by 3 users not shown)
=Related Pages on the A&A Website:= [http://www.aa.net.uk/telecoms.html www.aa.net.uk/telecoms.html] [http://www.aa.net.uk/kb-telecoms-sip.html www.aa.net.uk/kb-telecoms-sip.html] ---- =Incoming Features Tab Overview:= These are the features on the Control Page, under the 'Incoming' Tab. ===ACR=== Anonymous Call Reject - callers who withheld their number will have a message played to them and call will be rejected. Call 114 to hear that message, and 113 to record your own message. An alternative way of handling Anonymous calls is to not reject them on the account's control panel and, if ''all'' configured targets reject Anonymous calls, and you have voicemail enabled, then Anonymous calls will go direct to voicemail. Anonymous Call Reject - callers who withheld their number will be rejected ===Voicemail=== ===SIP Phone=== *You can register multiple sip phones to our server., and calls will be sent to all registered sip phones. ===Tag=== The Tag is 4 characters that will be prefixed to the ~~number~~caller's name field and (perhaps) shown on your phone's display (depending on whether your phone's display shows caller's number, caller's name, or both), this can be used to help identify the number the caller called. EgE.g., the tag could be set to ''Sale'' or ''Tech'', and then you'll know what type of call you are receiving. [[File:Snom715-Tag-Screenshot.png\|none\|frame\|The tag is set to 'aTag']] From: "aTag07508xxxxxx" <sip:07508xxxxxx@voiceless.aa.net.uk>;tag=2015012110443100001 It's worthwhile checking that your local equipment can cope with your chosen tag. For example a phone with a seven segment display will have difficulty with some alphabetic characters, and some phones can only display 12 characters (and a typical UK phone number is 11 characters) so you'll lose some characters. ===Your Server=== The format of the 'host' part of a SRV record is: <code> _service._protocol.name</code>. The format of the 'value' of an srv record would be in the format of: <code>priority weight port host</code> Lowest-numbered priority wins, weight is used for records with the same priority. More info on [https://en.wikipedia.org/wiki/SRV_record#Provisioning_for_high_service_availability Wikipedia]▼ ▲~~Lowest~~Like with MX records, lowest-numbered priority ~~wins~~gets tried first, weight is used for records with the same priority. More info in RFC 2782 and on [https://en.wikipedia.org/wiki/SRV_record#Provisioning_for_high_service_availability Wikipedia] You can test your SRV record using 'dig', 'host' or 'nslookup' on the command line, eg:▼ ▲You can test your SRV record using 'dig', 'host' or 'nslookup' on the command line, ege.g.: $ dig +short srv _sip._udp.pbx.example.com $ host -t SRV _sip._udp.pbx.example.com