AudioControl VERSION 6.2 manual Message Publish Subscribe Notify

CPE SIP Products

3.The ICMP protocol is not supported. The device is unable to generate ICMP PING packets. The SIP Gateway Alternative Routing feature using PING packets is not supported.

	Product
MP-11x		MP-124
Mediant 600		Mediant 1000
Mediant 800 MSBG		Mediant 1000 MSBG
Mediant 2000
Mediant 3000/TP-6310		Mediant 3000 HA/TP-6310
Mediant 3000/TP-8410		Mediant 3000 HA/TP-8410

4.T.38 fax relay using the same port as RTP (T38UseRTPport = 1) is not supported.

	Product
MP-11x		MP-124
Mediant 600		Mediant 1000
Mediant 800 MSBG		Mediant 1000 MSBG
Mediant 2000
Mediant 3000/TP-6310		Mediant 3000 HA/TP-6310
Mediant 3000/TP-8410		Mediant 3000 HA/TP-8410

5.For the IP-to-IP application, since the back-to-back user agent (B2BUA) mode is based on full termination at each leg, some requests, headers and URI parameters and message bodies are omitted or changed while traversing the device. Responses to requests within a SIP dialog are always sent independently at each leg regardless of the other leg’s response.

•The following SIP Methods are omitted by the IP-to-IP application:

♦MESSAGE

♦PUBLISH

♦SUBSCRIBE

♦NOTIFY

♦Out-of-dialog REFER

♦Any other proprietary Method

•The following SIP message components are omitted by the IP-to-IP application:

♦Message body (other than SDP)

♦Specific parameters in the SIP headers handled by the device (such as To, From, P-Asserted, Diversion, Remote Party ID, and Contact)

♦Specific parameters in the SDP – these parameters may affect the RTP flow at each leg independently

			Product
	MP-11x			MP-124
	Mediant 600			Mediant 1000
	Mediant 800 MSBG			Mediant 1000 MSBG
	Mediant 2000
	Mediant 3000/TP-6310			Mediant 3000 HA/TP-6310
	Mediant 3000/TP-8410			Mediant 3000 HA/TP-8410
SIP Release Notes		148		Document #: LTRT-26901