Difference between revisions of "UADs"

From Bicom Systems Wiki

m
m
 
(13 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
|-
 
|-
 
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
 
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
UAD (User Agent Device) department of the company is responsible for the development and documentation of the devices supported by our PBXware software. Amongst other things, we are responsible for:
+
The PBXware department is responsible for development and documentation of devices supported in our PBXware software. Among other things, we are responsible for:
* Adding provisioning support for new UADs.
+
* Adding the provisioning support for new UADs.
* Maintaining currently supported UADs.
+
* Maintaining the currently supported UADs.
* Resolving issues with currently supported UADs.
+
* Resolving any issues with the currently supported UADs.
 
* Documenting the UADs.
 
* Documenting the UADs.
  
For the list of currently supported UADs please check [[PBXware_5.3_End_Points| <span style="color: red;">'''SUPPORTED UAD LIST'''</span>]].
+
To see the list of the currently supported UADs, please refer to the[[MT_6_End_Points| <span style="color: red;">'''SUPPORTED UAD LIST'''</span>]].
|}
+
<!-- UAD-->
+
 
+
|-
+
<!-- ADDING NEW UADs -->
+
| style="height:100%;width:25em;border:1px solid #a48bbf;background-color:#ffffff;" valign="top" |
+
{| style="width:100%;"
+
|-
+
| <div style="margin:0;background:#39C;font-family:sans-serif;font-size:120%;font-weight:bold;border:1px solid #87CEEB;text-align:left;color:#fff;padding:0.4em;">ADDING NEW UADs</div>
+
|-
+
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
+
One of the main responsibilities of the UAD department is adding new UADs to the list of supported devices. As soon as the department receives needed UADs, time is allocated for development, testing and documentation.
+
 
+
What is important to notice is that PBXware release cycle is dictated by PBXware department, which is also in charge of importing new work done by UAD dept. This means that UAD department cannot set concrete date as to when new additions will be available to the users of our software.
+
 
+
If a customer needs the support for the new UAD before the new software is released, department can arrange a patch to be applied to the given system. Of course, standard patching warnings apply in such case.
+
|}
+
<!-- ADDING NEW UADs ends-->
+
 
+
|-
+
<!-- UAD MAINTENANCE -->
+
| style="height:100%;width:25em;border:1px solid #a48bbf;background-color:#ffffff;" valign="top" |
+
{| style="width:100%;"
+
|-
+
| <div style="margin:0;background:#39C;font-family:sans-serif;font-size:120%;font-weight:bold;border:1px solid #87CEEB;text-align:left;color:#fff;padding:0.4em;">UAD MAINTENANCE</div>
+
|-
+
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
+
Part of our daily duties is constant testing and inventing new scenarios of UAD usage. This ensures that we minimize number of defects in UAD support, and offer best possible experience with our system.
+
|}
+
<!-- UAD MAINTENANCE-->
+
 
+
|-
+
<!-- DOCUMENTATION -->
+
| style="height:100%;width:25em;border:1px solid #a48bbf;background-color:#ffffff;" valign="top" |
+
{| style="width:100%;"
+
|-
+
| <div style="margin:0;background:#39C;font-family:sans-serif;font-size:120%;font-weight:bold;border:1px solid #87CEEB;text-align:left;color:#fff;padding:0.4em;">DOCUMENTATION</div>
+
|-
+
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
+
Although documentation tends to be put aside, we have set a goal of maintaining it as often as we do testing of existing UADs support. This means that any new UAD gets a page on our wiki explaining manual and provisioning details as well as brief feature support list.
+
 
+
We also, work on current documentation and try to make it even better and clearer than before.
+
|}
+
<!-- DOCUMENTATION-->
+
  
 
|-
 
|-
Line 69: Line 25:
 
|-
 
|-
 
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
 
| <div style="font-size:115%;font-weight:bold;text-align:left;color:#87CEEB;"></div>
When a customer needs a new UAD supported in PBXware, they need to make an official request to add support for that UAD. These are the steps that have to be completed in order to start with the process:
+
If a customer needs a new UAD to be supported in PBXware, s(he) should make an official request of adding support for the specified UAD. Before starting the procedure, a customer has to follow a set of steps presented below.
* Contact [mailto:uad-team@bicomsystems.com <span style="color: red;">'''UAD Team'''</span>] with your request.
+
* Developers will do a research into the UAD technicalities to confirm that the UAD can be supported in the PBXware.
+
  
* Developers determine the time needed to implement the UAD support. Experience has shown that developers need at least one week for the UAD support implementation, which is a direct consequence of the increasing technical complexities that new UADs present. Considering this, multitudes of technical pages are used during the research so we could seamlessly implement the UAD.
+
* Contact the [mailto:uad-team@bicomsystems.com <span style="color: red;">'''PBXware Team'''</span>] by sending the official request.
 +
* Upon receiving the request, developers will conduct a research into the UAD technicalities to confirm that the UAD can be supported in PBXware.
 +
* Developers will determine the time needed to implement support for the specified UAD.
 +
* In case there was no previous arrangement made with the customer, s(he) is quoted with the developers' time. This is necessary due to the fact that the roadmaps for the software are already set.
 +
* Bicom Systems reserves the right to add the UAD changes into mainstream support.
  
* If there was no previous arrangement made with the customer, they are quoted with developer time. This is needed due to already set roadmaps for the software.
+
Please note the following:
** Bicom Systems reserves the right to add the UAD changes into the mainstream support.
+
  
* If the customer agrees on above terms, they must provide two non-returnable samples to our developers. In case of expensive UADs (like conference phones etc.), one sample is enough.
+
* Support for new UADs cannot be implemented for older PBXware versions.
 +
* The provisioning guide for the requested UAD must be available on the official website.
 +
* In case of a new manufacturer, direct contact with their Support team must be established.
  
 
<!--To ship the UADs to the developers, customer must do the following:
 
<!--To ship the UADs to the developers, customer must do the following:

Latest revision as of 14:24, 7 May 2020

UAD

The PBXware department is responsible for development and documentation of devices supported in our PBXware software. Among other things, we are responsible for:

  • Adding the provisioning support for new UADs.
  • Maintaining the currently supported UADs.
  • Resolving any issues with the currently supported UADs.
  • Documenting the UADs.

To see the list of the currently supported UADs, please refer to the SUPPORTED UAD LIST.

UAD REQUEST PROCEDURE

If a customer needs a new UAD to be supported in PBXware, s(he) should make an official request of adding support for the specified UAD. Before starting the procedure, a customer has to follow a set of steps presented below.

  • Contact the PBXware Team by sending the official request.
  • Upon receiving the request, developers will conduct a research into the UAD technicalities to confirm that the UAD can be supported in PBXware.
  • Developers will determine the time needed to implement support for the specified UAD.
  • In case there was no previous arrangement made with the customer, s(he) is quoted with the developers' time. This is necessary due to the fact that the roadmaps for the software are already set.
  • Bicom Systems reserves the right to add the UAD changes into mainstream support.

Please note the following:

  • Support for new UADs cannot be implemented for older PBXware versions.
  • The provisioning guide for the requested UAD must be available on the official website.
  • In case of a new manufacturer, direct contact with their Support team must be established.