setting Busy overflow results in no answer overflow being set

[ssteiner]

I'm starting out with this state

GET /api/rest/1.0/routing/state?loginName=oxe7800 HTTP/1.1

Code: Select all

{
	"presentationRoutes": [
		{
			"destinations": [
				{
					"type": "OFFICE",
					"selected": true
				},
				{
					"type": "MOBILE",
					"selected": true
				}
			]
		}
	],
	"forwardRoutes": [
		{
			"forwardType": "NO_ANSWER",
			"destinations": [
				{
					"type": "VOICEMAIL"
				}
			]
		}
	],
	"overflowRoutes": [],
	"dndState": {
		"activate": false
	}
}

Then I'm setting a BUSY overflow to a number

POST /api/rest/1.0/routing/overflowroute?loginName=oxe7800 HTTP/1.1

Code: Select all

{
	"overflowRoutes": [
		{
			"overflowType": "BUSY",
			"destinations": [
				{
					"type": "NUMBER",
					"number": "99980001"
				}
			]
		}
	],
	"requestId": "PMGR_ecf6d56c-85ae-4c24-8602-112595f78121"
}

And when I extract the status again, I see this

Code: Select all

{
	"presentationRoutes": [
		{
			"destinations": [
				{
					"type": "OFFICE",
					"selected": true
				},
				{
					"type": "MOBILE",
					"selected": true
				}
			]
		}
	],
	"forwardRoutes": [
		{
			"forwardType": "NO_ANSWER",
			"destinations": [
				{
					"type": "VOICEMAIL"
				}
			]
		}
	],
	"overflowRoutes": [
		{
			"overflowType": "NO_ANSWER",
			"destinations": [
				{
					"type": "NUMBER",
					"number": "99980001"
				}
			]
		}
	],
	"dndState": {
		"activate": false
	}
}

As you can see, there's an overflow to the number 99980001, but it's a NO_ANSWER overflow, not a BUSY overflow. Checking the Dynamic State User confirms this.. the associate is set to 99980001, but "Overflow on associate" is checked, not "Overfl.busy to assoc set".

I also tried BUSY_NO_ANSWER, same result.. only the NO_ANSWER overflow is set.

It also doesn't matter wheter I remove the NO_ANSWER forward route or not. I believe the fix for showing the proper overflow state doesn't go both ways (you recall that prior to release 29 routing state extraction didn't show the busy overflow route properly), it only shows the config properly but doesn't allow you to set this config properly.

[ssteiner]

is this fixed in 032?

[ssteiner]

seems I can answer that myself.. just tested it and this very scenario works in v33