SIP:Alert-Info header: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Alert-Info is handled when received in INVITE | == 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 for handling of Alert-Info is as follows: | The heuristic method for handling of Alert-Info is as follows: | ||
| Line 15: | Line 15: | ||
Otherwise an incoming call is tagged as "external". | Otherwise an incoming call is tagged as "external". | ||
''' | == Alert-Info is handled when received in INVITE == | ||
== Alert-Info when sending INVITE == | |||
The innovaphone PBX '''does not''' send Alert-Info in INVITE, since there is no specification of Alert-Info beyond its basic syntax and interpretation is manufacturer specific. | |||
Revision as of 08:53, 18 January 2011
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 for handling of 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 "file://Bellcore-dr1/"
- uri contains "internal"
An incoming call is tagged as "re-call" (return from failed blind transfer) if either:
- parameter "call-type" is "callback"
- parameter "info" is "alert-community1"
Otherwise an incoming call is tagged as "external".
Alert-Info is handled when received in INVITE
Alert-Info when sending INVITE
The innovaphone PBX does not send Alert-Info in INVITE, since there is no specification of Alert-Info beyond its basic syntax and interpretation is manufacturer specific.