Subscribe not hitting webhook

Notification API
1

I have setup a subscription:

“applicationId”: “AppID”,
“deviceId”: “https://webhook.site/1d44754b-5d66-4bc6-9d7f-c3070412e810”,
“transport”: “webhook”,
“topic”: “platform-api-media”,
“subjectFilter”: “/2017-09-01/endpoints/2240”,
“recordNotifications”: true,
“publicationFilter”: “$.publications[?(@.content.state == ‘ringing’)]”,
“expiryDateTime”: “2024-04-28T00:00:00Z”
}

But I don’t get anything when I place a call to that extension. Are there types of phone systems that this just won’t work with?

2

You shouldn’t need ‘recordNotifications’, I’m actually not sure what scenario that’s used for. That said, the rest looks good to me. Do you have the subscriptionId so I can look it up server side?

Officially we only support 6xxx series of IP phones because that’s what we test with, however that primarily pertains to call control. When it comes to notifications, most device types should work.

3

Here are the five that are currently unexpired.

102f758a69d84c91c879bddbbab0bbcf
0fdcc30bcdb1ca6f60f736b5a7ba8256
229f6a105728b973a04f7316d8e51dbf
bf41156897e8e1d10795c9391da109ff
2f1f5a338a6312c318f13d4faaf1818d

4

I’m not from Mitel but have been doing a lot of work with CloudLink and MiVB recently.

Try removing recordNotifications, expiryTime and the publicationFilter. If that works, work forward from there by adding the other parameters until it fails.

Also, I don’t include /2017-09-01 in my subject filter. /endpoints/[number] works.

I would include what PBX and software load you’re running for when someone from Mitel comes along to help.

5

Hi Budd, did you have a chance to look up the subscription ids I sent you?

6

Hi Lruss

Unfortunately, Budd no longer works for Mitel. Can you give us some more background? What type of PBX (type, release, …) are you using, and how is endpoint 2240 configured on your system? Are you subscriptionID still valid ?

regards,
Luc