Patton electronic SmartNode 4110 Series ユーザーズマニュアル

Location Service configuration task list

SmartWare Software Configuration Guide 

Message Waiting Indication is programmed in two sections of SmartWare, 
the FXS interface, and the SIP Location service. The information below 
refers to information for configuring the Message Waiting Indication feature 
for SIP. For information on configuring the Message Waiting Indication fea-
ture for FXS, see 

The SIP part of SmartWare is now able to receive message waiting information. This is done according to the 
subscribe notify mechanism described in RFC 3265 and RFC 3842. To be compatible with current installa-
tions, it is possible to choose between explicit and implicit subscription. In explicit subscription, SmartWare 
establishes the subscription by sending SUBSCRIBE messages to a configured message server. In implicit sub-
scription, the message server gets the subscriber information due to configuration or another mechanism like 
registration. In any case, SmartWare accepts and processes NOTIFY messages with message waiting informa-
tion, which is then forwarded to the according destination. 

Subscription 
If an identity is added to a location-service which is bound to a context sip-gateway, the following procedure 
takes place:

1. Determine if identity should be subscribed.

a. The location-service containing the identity must have at least one domain configured.

b. The identity must have a message inbound face configured or inherited.

c. The subscription command must be set to “explicit”.

2. Build the address to subscribe. The name of the identity builds the user-part. The first domain configured 

in the location-service builds the host-part.

3. Build the address of the message server. The message server configured in the message inbound face is 

taken as request-uri. If no message server is configured the first domain configured in the location-service 
builds the request-uri.

4. Build expire header. If a lifetime is configured in the message inbound face the expire header is set to 

desired lifetime else the lifetime is set to 3600 seconds.

5. Build contact address. The spoofed-contact parameter of the sip-interface in the context sip gateway, 

through which the SUBSCRIBE request is sent, is set as contact address. If no spoofed-contact is config-
ured the ip-address and port of the sip-interface in the context sip-gateway through which the SUB-
SCRIBE request is sent builds the contact address.

6. Send the SUBSCRIBE request.

If one of these steps has no result and fails, the subscription fails. After a certain timeout (which is configurable 
in the registration outbound face), the request is re-issued.

Outgoing SUBSCRIBE requests can provide authentication credentials. See 

“Outbound Authentication”

 on 

page 561 for more information.