News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

How to use OBiTalk portal to set CallerID Name on SP1?

Started by Telex, October 26, 2011, 07:11:05 PM

Previous topic - Next topic

Telex

I just received my OBi110 and, by using the OBiTalk portal, I had my device registered and sending/receiving calls via my voip.ms account within a few minutes.  Well done, Obihai!

The question I have concerns the use of the OBiTalk portal OBi Expert page to set a CallerID Name for SP1 (i.e. my voip.ms account).

I realize I can easily modify the CallerID Name by using the OBi110's administrative interface but, following ShermanObi's lead, I'd like to keep OBiTalk in sync and use its OBi Expert page.

I found CallerID Name in SP1's Calling Features section and discovered the following:

  • The field is blank and locked (i.e. I cannot enter text).
  • The Device Default checkbox is unchecked.
  • The OBiTalk Settings checkbox is checked and has an asterisk next to it.

From the OBi Expert page:
asterisk (*) indicating this parameter is currently being used in the OBiTALK portal for feature configuration
I don't know where ObiTalk configures the CallerID Name feature. I did not see it when setting up SP1.

If I uncheck the OBiTalk Settings checkbox, the Device Default check box is automatically checked and the field remains locked. I don't know what the Device Default checkbox signifies. Maybe it means that it defaults to using the CallerID Name set using the OBi110's administrative interface.

If I uncheck the Device Default checkbox, the field is unlocked. I assume whatever I enter as a name will be written to my OBi110 but I don't know how it affects the OBiTalk portal's usage of CallerID elsewhere in its interface.

I have not entered a name because I don't understand the implications of unchecking two checkboxes to get to this stage. Can someone please shed some light on this issue? Thanks!


Telex

No replies yet, so I'll simplify the question:

What is the function of the "Device Default" and "OBiTalk Settings" checkboxes in the OBi Expert section of the ObiTalk portal?

I'd like to know what are the repercussions of disabling the "Device Default" and "ObiTalk Settings" checkboxes. In order to supply a CallerID Name (via Obi Expert), I need to disable both of them.

For CallerID Name, its "OBiTalk Settings" checkbox has an asterisk next to it. Can someone elaborate on where it is used by OBiTalk?


QBZappy

Telex,
This is the official "How To" of how to use the Expert config. I think bottom part of the doc answers your question.

Quote from: ShermanObi on March 23, 2011, 12:02:48 AM

OBi Expert Configuration

Welcome to OBi Expert Configuration!  OBi Expert Configuration is, in essence, a portal within a portal for making any and all service-related configuration modifications to an OBi device.  Before we introduce the capabilities of the OBi Expert Configuration pages, let's review the functionality of the OBiTALK portal.

When an OBi device is added to the OBiTALK dashboard, it can be managed via the OBiTALK portal for device-specific things such as setting the device name, time-zone, AA PIN, etc.  The OBiTALK portal is also a place where services can be configured on a device – using either a service provider specific drop-down menu or with any service's SIP credentials and the Generic Service Provider template.  What's more, the OBiTALK portal can be used to configure network based functionality – applicable to all the OBi devices and the OBi soft phone owned by the user, e.g. Speed Dials and Trusted Caller ID Numbers and devices of his or her friends in Circles of Trust.

Now, that the higher-level OBiTALK portal has been described, let's talk about the OBi Expert Configuration Pages.  The OBi Expert Configuration pages are just that, for experts.  Users who do not feel comfortable with the on-board web-based OBi device configuration pages should stay away from the OBi Expert Configuration pages.  Users who do not feel comfortable reading the OBi Device Administration Guide should stay away from the OBi Expert Configuration pages.  When one uses the OBi Expert pages, they need to know that synchronization with settings and service indications as shown on the higher-level OBiTALK portal may display inaccurate configuration information.  The settings as shown in the OBi Expert pages trump all settings in the OBiTALK portal pages. 

The over-arching philosophy behind the OBi Expert Configuration Menu is to give users the ability to control their devices and services with a cloud-based management approach – affording all (or almost all) the flexibility of configuring the OBi via its integral browser based interface.  This capability is useful to Obihai customers and system integrators of Obihai products who gain considerable usefulness from the flexibility the OBi Expert Configuration management provides.

There are two data bases that come into play when interacting with the OBi Expert Configuration pages.  The OBiTALK configuration database stores the configurations that enable those functions made available on the OBiTALK portal.  Therefore, the OBiTALK portal pages will always represent the configuration settings associated with the OBiTALK database configuration for that particular device.  The functionality of the OBiTALK portal is continually changing.  With OBiTALK, Obihai is able to expose powerful features to the user which require somewhat complex and complicated configurations of the OBi device when used in conjunction with its owner's service provider accounts, soft phones and other OBi devices.

Note:  Neither database maintains storage of passwords used by OBi devices for administrative access or voice service registration.  When a password is entered and submitted via the OBiTALK or OBi Expert Configuration web pages, it is sent securely to the device (on the next profile re-sync) and then deleted.

OBi Expert Configuration Functions
When you enter the OBi Expert Configuration Menu, you are presented with the following function buttons:

Enter OBi Expert: Entering the OBi Expert configuration pages provides the user with the full breadth of every service-applicable parameter on the OBi device.

Reset OBi Expert Config: Selecting this option will perform a reset of applicable OBi Expert parameters to their factory default setting.

Revert to OBiTALK: When this option is selected every parameter will follow what is currently stored in the device's OBiTALK database configuration.

Importing a Configuration: At the bottom of the page there is an Import Configuration section, where there resides a function which allows the user to import (or upload) a previously saved XML configuration file as their OBi Expert database configuration.

When this option is selected, the OBi Expert database will import these settings and save them as the device's OBi Expert Configuration settings.  Once this configuration is in the database, the user can uncheck the OBiTALK setting box to selectively invoke parameter configurations contained in the imported config file. The OBiTALK box is checked by default because the OBi Expert mode requires that the user understand the changes they make while in the OBi Expert Configuration menus can possibly alter or break functionality associated with their OBiTALK configuration.  Also since OBiTALK controlled parameters change overtime, it is safer for the OBi Expert user to have to uncheck the OBiTALK Settings box in that a configuration that they previously knew to not be in conflict with OBiTALK may be in conflict the next time they go to import a config file.

Inside the OBi Expert Configuration pages, you will notice its resemblance to the OBi device web page menu, look and layout.  To the right of the configurable parameter value field, there may be a red exclamation mark (!).  When this mark is present, it means the parameter value next to where it appears has an OBi Expert configuration database entry that is different than the OBiTALK database entry.  If the Device Default and OBiTALK boxes are left unchecked, then the OBi will use this setting in its active configuration. 

On the right side of the OBiTALK Settings check box there may be an asterisk (*) indicating this parameter is currently being used in the OBiTALK portal for feature configuration.  Therefore, if the symbol resides next to a parameter setting that you choose to over-ride with an OBi Expert Configuration setting, the functionality configured by the OBiTALK portal is subject to conflicted operation.  It is important to note that the presence of the * may appear suddenly, when functionality is added to the OBiTALK portal that requires management of the parameter next to which the * appears.  We suggest that users uncheck the OBiTALK box for those parameters NOT marked with the *, when the particular parameter value is different for a configuration outside the realm of what is available in OBiTALK. Unchecking the OBiTALK box will ensure the custom value will not be overwritten by a future OBiTALK enhancement or modification.

Finally, before jumping to a new page to check on settings or make modifications, please do not forget to select the "Submit" button for each page on which you have made a modification that you want to save to the device's OBi Expert configuration file.
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

Telex

Thanks for your reply.  I read that post before submitting my question but, at least for me, it fails to clarify the operation of "Device Default".

ShermanObi's post states:
Unchecking the OBiTALK box will ensure the custom value will not be overwritten by a future OBiTALK enhancement or modification

That's clear to me but, in fact, simply unchecking the OBITalk Settings box does not let you enter a value. You have to uncheck both OBiTalk Settings and Device Default. That is stated in the post as well:

If the Device Default and OBiTALK boxes are left unchecked, then the OBi will use this setting in its active configuration.  

So what happens if you uncheck OBiTalk Settings but leave Device Default checked? In this mode, the value field remains locked.

So how does it work if only "Device Default" is checked? For example, from where would the Obi110 source its CallerID Name if only Device Default is checked? Will it simply use whatever has been set via the OBi110's administrative interface?


QBZappy

Quote from: Telex on October 28, 2011, 09:36:04 AM
So how does it work if only "Device Default" is checked? For example, from where would the Obi110 source its CallerID Name if only Device Default is checked? Will it simply use whatever has been set via the OBi110's administrative interface?

There are 3 possible places to setup config info:
1) OBi unit
2) Expert
3) OBiTALK

The way I understand this is that the unit OBi default values will be used in your above mentioned scenario. By default the OBi unit CID is blank. If you want CID via portal I think you need to uncheck both and enter your value in the Expert. Don't forget about the auto provisioning setup. You must enable both ITSP and OBi Provisioning on the unit for the settings to stick.

I don't use the Expert config method myself. Someone else more knowledgeable might be able to help.
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

dailyglen

Hi,

After reading this I'm still confused and am trying to get my Caller ID Name working with Voip.ms and I'm in Canada.  On the Obi dashboard my device has my name "John Doe" and in ObiExpert config I have:

SP1 Service -> CallerIDName: [                  ] !    [ ] [X] *
SP2 Service -> CallerIDName: [                  ] !    [ ] [X] *
ObiTALK Service -> DisplayName: [John Doe ] !    [ ] [X] *

If I understand the above posts then my SP1 and SP2 CallerIDName is set to be blank by the Obi Dashboard and to John Doe on ObiTalk Service.  Why doesn't the dashboard set the correct callerid for SP1 and SP2?  Is this a bug?

Even if I set the CallerIDName by myself (by unchecking the two boxes) I can't get voip.ms to carry it along to whom I'm calling.  I have disabled the caller ID number override with voip.ms but I still get my DID as the CallerIDName instead of my name.  Has anyone figured this out?

Thanks

wyliesdiesels

Quote from: dailyglen on December 06, 2011, 08:23:24 AM
Hi,

After reading this I'm still confused and am trying to get my Caller ID Name working with Voip.ms and I'm in Canada.  On the Obi dashboard my device has my name "John Doe" and in ObiExpert config I have:

SP1 Service -> CallerIDName: [                  ] !    [ ] [X] *
SP2 Service -> CallerIDName: [                  ] !    [ ] [X] *
ObiTALK Service -> DisplayName: [John Doe ] !    [ ] [X] *

If I understand the above posts then my SP1 and SP2 CallerIDName is set to be blank by the Obi Dashboard and to John Doe on ObiTalk Service.  Why doesn't the dashboard set the correct callerid for SP1 and SP2?  Is this a bug?

Even if I set the CallerIDName by myself (by unchecking the two boxes) I can't get voip.ms to carry it along to whom I'm calling.  I have disabled the caller ID number override with voip.ms but I still get my DID as the CallerIDName instead of my name.  Has anyone figured this out?

Thanks

I realize this is a really old thread. however, i stumbled on it trying to figure out the same thing as you. then i did some more searching and found the answer.

If youre in the US there is no way to transmit the CNAM- caller ID name, or config it in your device or voip .ms portal. CNAMs are controlled by a national CNAM database and if you want it updated, you have to pay $10 to do so.

more info here under outgoing outgoing caller ID name

https://wiki.voip.ms/article/Caller_ID