incorrect error when programming set supervision key

[ssteiner]

Just ran into this - I tried programming a set supervision key for the same station on two keys. Apparently that's not supported as mgr tells me the following when I try to do it.

Processing Failure x
x OBJECT -1: Key No.: There is redundancy on the key type

With O2G, I send

Code: Select all

{
	"attributes": [{
		"name": "Type",
		"value": ["Station_Supervision"]
	},
	{
		"name": "Key_NOE_Mnemonic1",
		"value": ["labtest3"]
	},
	{
		"name": "Ringing_Mode",
		"value": ["Long_Ring"]
	},
	{
		"name": "Directory_Number",
		"value": ["1034"]
	}]
}

And the error I get back is this

Code: Select all

{
	"httpStatus": "BAD_REQUEST",
	"code": 1006,
	"helpMessage": "Request parameters are not correct. Please fix the problem and resend the request.",
	"type": "BAD_PARAMETER",
	"innerMessage": "McdoException: problem=ProcessingFailure message=Processing Failure for Attribute id=Subscriber_Key error=819",
	"canRetry": true
}

Technically, that is correct, what I sent was not allowed, but practically, I think O2G should always return a useful error - in this case what mgr returns as this tells you something and you don't have to troubleshoot by attempting to do the same operation manually and see why it fails.

[ssteiner]

Here's another example... this time the set where I wanted to program set supervision wasn't a multiline set.
In Mgr, this scenario gives you the following error

Code: Select all

 x Processing Failure                             x
          x OBJECT -1: ATTRIBUTE 0: Set must be multi-line 

The same on O2G gives you

Code: Select all

{
	"httpStatus": "BAD_REQUEST",
	"code": 1006,
	"helpMessage": "Request parameters are not correct. Please fix the problem and resend the request.",
	"type": "BAD_PARAMETER",
	"innerMessage": "McdoException: problem=ProcessingFailure message=Processing Failure for Attribute id=null error=902",
	"canRetry": true
}

the corresponding request

Code: Select all

{
	"attributes": [{
		"name": "Type",
		"value": ["Station_Supervision"]
	},
	{
		"name": "Key_NOE_Mnemonic1",
		"value": ["labteam2"]
	},
	{
		"name": "Ringing_Mode",
		"value": ["Long_Ring"]
	},
	{
		"name": "Directory_Number",
		"value": ["1029"]
	}]
}

[yblanchard]

ok: whenever the pbx error message will contain an error code, O2G will add the error label (corresponding to the GEA one) if it is found in the error dictionary.
For example:
message=Processing Failure for Attribute id=Subscriber_Key error=819:there is redundancy on the key type"

[ssteiner]

is that new way or returning errors already part of the new build that was posted recently (14.0.000.027)?

[yblanchard]

not in 14.0.000.027: still need to wait for 0.28