Avaya 4600 Series Anwendungshinweis PDF herunterladen (Seite 68)

Troubleshooting the Push Interface

68 4600 Series IP Telephones Application Programmer Interface (API) Guide

205 “Not In Push State:

Push Aborted”

The Push Message was rejected because the phone

is in a non-pushable state. Try sending a “barge”

priority message instead. See Chapter 3: Creating

Push Messages for more information.

208 “Not in Audio Push

State: Push Aborted”

The audio stream was rejected because the user is

currently on the call or busy. Try sending a “barge”

priority message instead. See The Audio Push

Type on page 46for more information.

301 “XML document not

valid”

Check the proper XML schema as described in this

API. See Chapter 3: Creating Push Messages

for

more information.

302 “XML document not

well-formed”

Make sure that all the XML tags are properly formed.

See Chapter 3: Creating Push Messages

for more

information.

303 “No element found” Make sure that all the XML tags are properly formed.

See Chapter 3: Creating Push Messages

for more

information.

304 “Unknown encoding” Make sure that all the XML tags are properly formed.

See Chapter 3: Creating Push Messages

for more

information.

305 “Invalid root element” Make sure that all the XML tags are properly formed.

See Chapter 3: Creating Push Messages

for more

information.

306 “Empty Post Content” If you are using the HTTP POST method in the Push

Message, include postfield tags with the message.

307 “Push Content too large” The XML file is larger than 5Kb. Send an XML file

less than 5K bytes.

402 “Push security failure” The security service failed to validate the Trusted

Push Server.

501 “Invalid Push URI” Recheck the URI included in the <go href…/>

request for fully qualified URL string. Also, make

sure the length of the URI is no longer than 1024

characters.

503 “Subscription Service

Unavailable”

Ask your system administrator to administer the

SUBSCRIBELIST value on the TFTP Server. See

Chapter 4: Push Administration

for more information.

Table 6: x-Avaya-Push-Code Responses (continued)

x-Push-

Status code

Reason Phrase

(Description)

Resolution (“N/A”: Avaya IP Telephones

never send the status code)

2 of 2

1 2 ... 63 64 65 66 67 68 69 70 71 72 73 ... 205 206

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya 4600 Series Anwendungshinweis Seite 68

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Software Avaya 4600 Series