Patton electronic SmartNode 4110 Series ユーザーズマニュアル
Location Service configuration task list
622
SmartWare Software Configuration Guide
51 • Location Service
Message Waiting Indication through Call-Control
The message waiting indication received on the SIP side is transported through the call control to the destina-
tion FXS interface. Currently, the SIP interface is the only source of message waiting indication information
and the FXS interface is the only possible destination of this information. The information is routed like a call
through the call-control. Therefore, it must exist a valid routing path for a call from the SIP interface handling
the NOTIFY to the destination fxs interface. This must be the case, because the phone connected to the FXS
interface must be able to get calls from SIP before it makes any sense to get message waiting information for
missed calls from SIP.
tion FXS interface. Currently, the SIP interface is the only source of message waiting indication information
and the FXS interface is the only possible destination of this information. The information is routed like a call
through the call-control. Therefore, it must exist a valid routing path for a call from the SIP interface handling
the NOTIFY to the destination fxs interface. This must be the case, because the phone connected to the FXS
interface must be able to get calls from SIP before it makes any sense to get message waiting information for
missed calls from SIP.
The message waiting information can be transported through routing-tables, service aaa, service limiter, service
priority, service distribution-group and service hunt-group.
priority, service distribution-group and service hunt-group.
•
In case of routing through routing tables, the message waiting information will reach the right destination
only if the parameter according which the routing occurs is set to exactly the same value in an incoming
INVITE request for that FXS interface as in the incoming NOTIFY request for that FXS interface.
only if the parameter according which the routing occurs is set to exactly the same value in an incoming
INVITE request for that FXS interface as in the incoming NOTIFY request for that FXS interface.
•
In the case of “called-e164”, this is surely the same, but pay attention to the manipulation of parameters.
•
In case of service distribution-group, the message waiting information is transported to any valid destina-
tion of the distribution-group.
tion of the distribution-group.
•
In case of service hunt-group, the message waiting information is transported only to the first destination of
the hunt group.
the hunt group.
•
In any other of the named services, the message waiting information is routed transparently through.
If the message waiting information is routed to a destination service or interface which is not explicitly listed
here, the information will be dropped.
here, the information will be dropped.