SIP:Alert-Info header: Difference between revisions
Jump to navigation
Jump to search
(New page: Alert-Info is handled when received in INVITE.<br> It's for endpoints connected to a non-innovaphone PBX that sends Alert-Info in INVITE.<br> The heuristic method for handling of Alert-Inf...) |
mNo edit summary |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Alert-Info is handled when received in INVITE | =Inbound Calls= | ||
== Alert-Info is handled when received in INVITE == | |||
It's for endpoints connected to a non-innovaphone PBX that sends Alert-Info in INVITE.<br> | It's for endpoints connected to a non-innovaphone PBX that sends Alert-Info in INVITE.<br> | ||
The heuristic method | The heuristic method or processing Alert-Info is as follows: | ||
An incoming call is tagged as "internal" if either: | An incoming call is tagged as "internal" if either: | ||
* parameter "call-type" is "internal" | * parameter "call-type" is "internal" | ||
* parameter "info" is "alert-internal" | * parameter "info" is "alert-internal" | ||
* uri contains " | * uri contains "Bellcore-dr1" | ||
* uri contains "internal" | * uri contains "internal" (e.g. urn:alert:source:internal (RFC 7462)) | ||
An incoming call is tagged as "re-call" (return from failed blind transfer) if either: | An incoming call is tagged as "re-call" (return from failed blind transfer) if either: | ||
* parameter "call-type" is "callback" | * parameter "call-type" is "callback" | ||
* parameter "info" is "alert-community1" | * parameter "info" is "alert-recall" or "alert-community1" | ||
* uri contains "Bellcore-dr3/" | |||
* uri contains "service:recall" (e.g. urn:alert:service:recall:transfer (RFC 7462)) | |||
An incoming call is tagged as "emergency" if either: | |||
* parameter "info" is "alert-emergency" | |||
Otherwise an incoming call is tagged as "external". | Otherwise an incoming call is tagged as "external". | ||
=Outbound Calls= | |||
== Alert-Info when sending INVITE == | |||
Alert-Info header is sent in INVITE and the header content is selected according to RFC 7462: | |||
* <urn:alert:source:internal> if this call is tagged as "Internal" | |||
* <urn:alert:source:external> if this call is tagged as "Normal" | |||
* <urn:alert:service:recall:transfer> if this call is tagged as "Recall" (failed blind transfer) | |||
== Alert-Info is handled when received in provisional response == | |||
An outgoing call is tagged as "queued" (call-waiting) if "urn:alert:service:call-waiting" is present in Alert-Info header. | |||
[[Category:Faq|{{PAGENAME}}]] | |||
Latest revision as of 11:10, 22 June 2016
Inbound Calls
Alert-Info is handled when received in INVITE
It's for endpoints connected to a non-innovaphone PBX that sends Alert-Info in INVITE.
The heuristic method or processing Alert-Info is as follows:
An incoming call is tagged as "internal" if either:
- parameter "call-type" is "internal"
- parameter "info" is "alert-internal"
- uri contains "Bellcore-dr1"
- uri contains "internal" (e.g. urn:alert:source:internal (RFC 7462))
An incoming call is tagged as "re-call" (return from failed blind transfer) if either:
- parameter "call-type" is "callback"
- parameter "info" is "alert-recall" or "alert-community1"
- uri contains "Bellcore-dr3/"
- uri contains "service:recall" (e.g. urn:alert:service:recall:transfer (RFC 7462))
An incoming call is tagged as "emergency" if either:
- parameter "info" is "alert-emergency"
Otherwise an incoming call is tagged as "external".
Outbound Calls
Alert-Info when sending INVITE
Alert-Info header is sent in INVITE and the header content is selected according to RFC 7462:
- <urn:alert:source:internal> if this call is tagged as "Internal"
- <urn:alert:source:external> if this call is tagged as "Normal"
- <urn:alert:service:recall:transfer> if this call is tagged as "Recall" (failed blind transfer)
Alert-Info is handled when received in provisional response
An outgoing call is tagged as "queued" (call-waiting) if "urn:alert:service:call-waiting" is present in Alert-Info header.