02-05-2020 05:32 AM - edited 02-05-2020 05:36 AM
I've set up a subscription to a user's "Basic Call" events using HTTP contact and am receiving some event notifications at the endpoint I have specified, but not all.
Most of the time I will only receive a CallSubscriptionEvent/OnHook or a CallReceivedEvent, with no corresponding events such as call ending (or vice versa!).
ngrok/fiddler don't register any requests to my endpoint that my event handling code isn't registering, so I'm at a bit of a loss.
Does anyone have any ideas or suggestions?
Subscription Command (censored)
POST {{host}}/xsi-events/v2.0/user/{{username}}
<?xml version="1.0" encoding="UTF-8"?> <Subscription xmlns="http://schema.broadsoft.com/xsi"> <subscriberId>{{username}}</subscriberId> <targetIdType>User</targetIdType> <targetId>{{username}}</targetId> <event>Basic Call</event> <expires>3600</expires> <httpContact> <uri>{{url}}/new-phone</uri> </httpContact> <applicationId>{{appId}}</applicationId> </Subscription>
Versions
<?xml version="1.0" encoding="UTF-8"?> <Versions xmlns="http://schema.broadsoft.com/xsi"> <commands> <baseline>21.0</baseline> <patchedCommand> <uri>/v2.0/user/[userid]</uri> <version> <value>22.1</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/user/[userid]/subid/[targetsubid]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/enterprise/[enterpriseid]/group/[groupid]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/serviceprovider/[serviceproviderid]/group/[groupid]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/enterprise/[enterpriseid]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/serviceprovider/[serviceproviderid]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/subscription/[subscriptionId]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/subscription</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/systemChannel</uri> <version> <value>23.0</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/systemChannelSet</uri> <version> <value>23.0</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/systemSubscription</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> <patchedCommand> <uri>/v2.0/systemSubscription/[subscriptionid]</uri> <version> <value>22.2</value> <feature>13709</feature> </version> </patchedCommand> </commands> <eventPackages> <baseline>21.0</baseline> <patchedEventPackage> <name>Standard Call</name> <version> <value>21.3</value> </version> </patchedEventPackage> <patchedEventPackage> <name>Advanced Call</name> <version> <value>21.3</value> </version> </patchedEventPackage> <patchedEventPackage> <name>Push Notification Registration</name> <version> <value>21.6</value> </version> </patchedEventPackage> </eventPackages> </Versions>
02-07-2020 08:26 AM
Analyzing the reported issue.
02-19-2020 02:51 AM
We tried to simulate the scenario. Did not encounter this problem. The issue might be that you are not handling the event post request with a success response and it might be getting timed out.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: