[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
XML push client/phone intiated?
Author Message
KNERD Offline
Junior Member
**

Posts: 39
Joined: Mar 2014
Reputation: 0
Post: #11
RE: XML push client/phone intiated?
Of course all phones are connected to "A" PBX, but I cannot send the message to 100 different PBXs.

Thus the source of the message needs to come from another server, such as a provisioning server, or a PUSH/PULL XML server.

Reasoning, I need to put the status of our system so we are not inundated with the same calls over, and over about PBX problems.

EDIT: After studying that page 99 more, it may work after all. I will research it more. Thanks!
(This post was last modified: 12-06-2016 03:18 PM by KNERD.)
12-06-2016 01:55 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
KNERD Offline
Junior Member
**

Posts: 39
Joined: Mar 2014
Reputation: 0
Post: #12
RE: XML push client/phone intiated?
That guide turns out if not very useful. It tells you everything you need to know except for how to construct XML NOTIFY SIP message, and lacking discussion on how the phone is suppose to receive it!
(This post was last modified: 12-06-2016 10:43 PM by KNERD.)
12-06-2016 10:42 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
jolouis Offline
Moderator
*****

Posts: 339
Joined: Oct 2013
Reputation: 6
Post: #13
RE: XML push client/phone intiated?
Honestly it really sounds like you are going about this in a strange way. If the idea is to let customers know there is a problem and avoid support hours wasted when you have something going on, rather than using an XML message (which people might miss, dismiss, not read, etc) the typical way is to have an automated message inserted into the support queue. Advantages:
1) Only people who experience a problem will call in. Your outage/issue/whatever may not affect everyone, or not everyone in the same way. If you send out generic "Sorry we are down right now please wait" kind of messages, it highlights the problems with your system to all users, even those who might not have noticed (i.e. they weren't using their phone during the 5 minutes you were down, so would not have cared, but now see a message telling them about the error and your lack of reliability). The more that happens, the less confidence customers will have with your setup.
2) When people who experience a problem call in, they should hear the automated message immediately (i.e. "As of ZZZ time we are experiencing an outage that affects customers in YYY area. The problem is expected to be resolved by QQQ time. If you are in this area and experiencing difficulties please check back/check our website/whatever for updates. Our customer service staff does not have any additional information on this issue as of yet"). Just hearing that message will get rid of the majority of your complaining customers as they will simply hang up and wait. Most people just want to know that you are aware of the issue.

Anyway enough about how to properly run your organization...

At this point you have all the information you need from a Yealink perspective. If you don't know how to generate SIP Notify messages check with your PBX vendor/supplier/support as it should be a built in method. From there you would just need a way for all PBXes to check status from a central server and send out notifys as required... but if the PBX crashes or something that wouldn't work, and hence you're back to realizing your approach is not the best option...
12-07-2016 01:54 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
KNERD Offline
Junior Member
**

Posts: 39
Joined: Mar 2014
Reputation: 0
Post: #14
RE: XML push client/phone intiated?
The message would not be going across hundreds of extensions, but to those who we would expecting to call and complain. It will offer other advantages such as those who always pay late, and other lovely messages.

Thanks for the other advice. I am looking into that also.
12-08-2016 04:41 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
KNERD Offline
Junior Member
**

Posts: 39
Joined: Mar 2014
Reputation: 0
Post: #15
RE: XML push client/phone intiated?
The phones belong to customers. Sometimes we will want to send message to client concerning their service,
04-20-2018 08:54 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Yealink VOIP phone losing connection every few minutes robertpowell 1 77 Yesterday 04:34 PM
Last Post: SRIIVF
  Yealink phone with hearing aids Jamie22RR 1 492 03-18-2024 01:49 AM
Last Post: complex1
  Yealink IP phone lesliefrench 0 432 01-25-2024 12:37 PM
Last Post: lesliefrench
  Remote Phonebook - Numbers Display Format On Phone Medryn 19 67,839 11-24-2023 02:28 AM
Last Post: shulem@theteklink.com
  IP Phone Login Error "ERR_INVALID_HTTP_RESPONSE" nolto 2 1,827 10-06-2023 04:34 PM
Last Post: nolto
  Multicast Stops Working until Phone Rebooted Blake1 10 11,154 09-21-2023 05:47 PM
Last Post: axiompm
  Is there a way to get the incoming caller phone number with an Action URI? troy44 1 1,187 09-04-2023 01:46 PM
Last Post: Regend_Yealink
  On MP50s responding to some phone trees ends the call TRK45 1 1,451 05-18-2023 04:46 PM
Last Post: complex1
  Import xml contacts to Yealink Phone upon provisioning via TFTP vusald 1 2,377 02-18-2023 06:30 PM
Last Post: complex1
  W60B - URL for Remote Phone Book Bosstoad 2 2,934 01-06-2023 02:58 AM
Last Post: Bosstoad

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication