VoIP - Caller Display: Difference between revisions
(Document the caller's number and name fields) |
mNo edit summary |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
__NOTOC__<indicator name="Configuring">[[File:Menu-cog.svg|link=:Category:VoIP Features|30px|Back up to the VoIP Features Category]]</indicator> |
__NOTOC__<indicator name="Configuring">[[File:Menu-cog.svg|link=:Category:VoIP Features|30px|Back up to the VoIP Features Category]]</indicator> |
||
By default we send the incoming caller's phone number when you receive a call. This means that your phone (if it has a display) will show the number of the person calling you. It may show Unknown or Withheld if it is not known. |
By default we send the incoming caller's phone number when you receive a call. This means that your phone (if it has a display) will show the number of the person calling you. It may show Unknown or Withheld if it is not known. There is also a caller's name field which we send as well, although this usually won't show the name (except on calls from other AAISP VoIP customers). |
||
==Untrusted calls have CLI prefixed with ?== |
|||
Where an incoming call has been made using a [[VoIP_-_Calling_With_a_SIP_URI|SIP URI]] rather than the PSTN the 'number' of the person calling cannot be trusted (and may be not purely numeric) , and so we prefix that 'number' with a '?' to indicate the potential |
Where an incoming call has been made using a [[VoIP_-_Calling_With_a_SIP_URI|SIP URI]] rather than the PSTN the 'number' of the person calling cannot be trusted (and may be not purely numeric) , and so we prefix that 'number' with a '?' to indicate the potential untrustworthiness. |
||
==Caller's Number and Name== |
==Caller's Number and Name== |
||
The protocol used (SIP) to deliver phone calls to you has fields which provide the caller's number and the caller's "name" - although the name will probably not be received for calls from the PSTN. Where the name field received is the same as the number field, we will send to you the name field set to the "pretty format" of the caller's number - e.g. "020 |
The protocol used (SIP) to deliver phone calls to you has fields which provide the caller's number and the caller's "name" - although the name will probably not be received for calls from the PSTN. Where the name field received is the same as the number field, we will send to you the name field set to the "pretty format" of the caller's number - e.g. "020 xxxx xxxx", "07973 xxxxxx". If the name field is set to something different than the number then it will be passed on to you - in general this will only apply to calls from other AAISP VoIP customers, or from calls received using sip: URIs. |
||
Your local hardware will display either the number, the name, or both (or neither if it has no display..). If you have an Analogue Telephone Adaptor set to sending caller display to your analogue phone(s) using BT's SIN 227 standard, then this standard also has fields for caller's number and caller's name and those fields will be populated. |
Your local hardware will display either the number, the name, or both (or neither if it has no display...). If you have an Analogue Telephone Adaptor set to sending caller display to your analogue phone(s) using BT's SIN 227 standard, then this standard also has fields for caller's number and caller's name and those fields will be populated. Note that in the SIN 227 standard '+' is not a valid character in the number field, although space (' ') and dash ('-') are allowed. |
||
For some examples, a SIP From header could be: |
|||
"07973 xxxxxx" <sip:07973xxxxxx@voiceless.aa.net.uk>;tag=2018122611233000003 |
|||
becoming (through a Grandstream ATA) the SIN 227 message: |
|||
NMBR = 07973xxxxxx DATE = 1226 TIME = 1123 NAME = 07973 xxxxxx |
|||
An anonymous call would have a SIP From header like: |
|||
"Anonymous" <sip:Anonymous@voiceless.aa.net.uk>;tag=2018122611244000001 |
|||
becoming |
|||
NMBR = O DATE = 1226 TIME = 1124 NAME = Anonymous |
|||
and a SIP URI call could have a SIP From header of: |
|||
"30164xxx" <sip:%3f30164xxx@voiceless.aa.net.uk>;tag=2018122611314200003 |
|||
becoming |
|||
NMBR = O DATE = 1226 TIME = 1131 NAME = 30164xxx |
|||
(The '%3f' is the URL encoding of the '?' we added) |
|||
(In the SIN 227 messages, a NMBR of 'O' means 'Unavailable' and 'P' means 'Withheld'). |
|||
==Tag feature== |
==Tag feature== |
||
This is a feature found on the control pages for your phone number. |
This is a feature found on the control pages for your phone number. |
||
The Tag is 4 characters that will be prefixed to the |
The Tag is 4 characters that will be prefixed to the name and shown on your phone's display, this can be used to help identify the number the caller called. E.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']] |
[[File:Snom715-Tag-Screenshot.png|none|frame|The tag is set to 'aTag']] |
||
| Line 31: | Line 50: | ||
In the 'tag' box, set it to N= (e.g. 2=), then the CLI will be sent as +11N (in our example, +112) followed by the number calling. This way you will be able to tell that the incoming call is one being redirected from your VoIP number and you still get the CLI of the caller. |
In the 'tag' box, set it to N= (e.g. 2=), then the CLI will be sent as +11N (in our example, +112) followed by the number calling. This way you will be able to tell that the incoming call is one being redirected from your VoIP number and you still get the CLI of the caller. |
||
(This feature was added 2017-04-20, but may be removed or improved) |
(This feature was added 2017-04-20, but may be removed or improved - as of 2022-10-20 it seems to no longer work) |
||
==Setting your outgoing caller ID== |
==Setting your outgoing caller ID== |
||
Latest revision as of 07:45, 21 October 2022
By default we send the incoming caller's phone number when you receive a call. This means that your phone (if it has a display) will show the number of the person calling you. It may show Unknown or Withheld if it is not known. There is also a caller's name field which we send as well, although this usually won't show the name (except on calls from other AAISP VoIP customers).
Untrusted calls have CLI prefixed with ?
Where an incoming call has been made using a SIP URI rather than the PSTN the 'number' of the person calling cannot be trusted (and may be not purely numeric) , and so we prefix that 'number' with a '?' to indicate the potential untrustworthiness.
Caller's Number and Name
The protocol used (SIP) to deliver phone calls to you has fields which provide the caller's number and the caller's "name" - although the name will probably not be received for calls from the PSTN. Where the name field received is the same as the number field, we will send to you the name field set to the "pretty format" of the caller's number - e.g. "020 xxxx xxxx", "07973 xxxxxx". If the name field is set to something different than the number then it will be passed on to you - in general this will only apply to calls from other AAISP VoIP customers, or from calls received using sip: URIs.
Your local hardware will display either the number, the name, or both (or neither if it has no display...). If you have an Analogue Telephone Adaptor set to sending caller display to your analogue phone(s) using BT's SIN 227 standard, then this standard also has fields for caller's number and caller's name and those fields will be populated. Note that in the SIN 227 standard '+' is not a valid character in the number field, although space (' ') and dash ('-') are allowed.
For some examples, a SIP From header could be:
"07973 xxxxxx" <sip:07973xxxxxx@voiceless.aa.net.uk>;tag=2018122611233000003
becoming (through a Grandstream ATA) the SIN 227 message:
NMBR = 07973xxxxxx DATE = 1226 TIME = 1123 NAME = 07973 xxxxxx
An anonymous call would have a SIP From header like:
"Anonymous" <sip:Anonymous@voiceless.aa.net.uk>;tag=2018122611244000001
becoming
NMBR = O DATE = 1226 TIME = 1124 NAME = Anonymous
and a SIP URI call could have a SIP From header of:
"30164xxx" <sip:%3f30164xxx@voiceless.aa.net.uk>;tag=2018122611314200003
becoming
NMBR = O DATE = 1226 TIME = 1131 NAME = 30164xxx
(The '%3f' is the URL encoding of the '?' we added) (In the SIN 227 messages, a NMBR of 'O' means 'Unavailable' and 'P' means 'Withheld').
Tag feature
This is a feature found on the control pages for your phone number.
The Tag is 4 characters that will be prefixed to the name and shown on your phone's display, this can be used to help identify the number the caller called. E.g., the tag could be set to Sale or Tech, and then you'll know what type of call you are receiving.
The above screenshots are from a Snom 715 and a Snom 821 showing incoming calls with a tag of "aTag".
The SIP for a tag is shown in the From field:
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.
Special, "unsupported" tag feature: If you forward a VoIP number to another number such as your mobile (using the Also Rings), the CLI presented to your mobile will be the callers number. You won't know if this is a redirected call or not. There is a hidden feature where by we can add a prefix to the CLI. In the 'tag' box, set it to N= (e.g. 2=), then the CLI will be sent as +11N (in our example, +112) followed by the number calling. This way you will be able to tell that the incoming call is one being redirected from your VoIP number and you still get the CLI of the caller.
(This feature was added 2017-04-20, but may be removed or improved - as of 2022-10-20 it seems to no longer work)
Setting your outgoing caller ID
see: VoIP Caller ID