Please Note – This should be performed on your LAB only.
There have been many times where I am tasked to perform interop on a device lacking a Broadsoft Partner Config Guide (PCG). These scenarios are great fun as there are some options that you initially set that CANNOT be changed via BWCLI or the GUI. The main options that come to mind are:
Is this Device Addressing?
Is this ‘Proxy Addressing’?
I used to make a device type and hope that it would work as planned. If not, I would remove all of my config (usually trunk groups with 10 + test users) and start over on a new device type. Then one day I got sick of it! I decided to poke around in the Database, and low and behold I found a solution.
1. From the AS (linux cli) launch ‘ttisql <DSN-NAME>’. Note – Your DSN is probably named ‘AppServer’>
2. Perform a query for the device name in question :
SELECT * from BWAS.DEVICE_TYPE WHERE DEVICE_TYPE = 'Cisco 36xx-Trunk' ; < 2401, Cisco 36xx-Trunk, N, -1, SIP , N, N, <NULL>, <NULL>, <NULL>, NONE , <NULL> > 1 row found.
If you interested in more details (column names) you can perform a ‘describe’ on the table:
DESCRIBE BWAS.DEVICE_TYPE ; Table BWAS.DEVICE_TYPE: Columns: *DEVICE_TYPE_UID INTEGER NOT NULL DEVICE_TYPE VARCHAR (40) INLINE NOT NULL OBSOLETE_FLAG CHAR (1) NOT NULL NUM_PORTS INTEGER NOT NULL PROTOCOL_NAME CHAR (20) NOT NULL MONITORING_ENABLED_FLAG CHAR (1) NOT NULL CPE_DEVICE_RESET_SUPPORTED CHAR (1) CPE_SYSTEM_FILENAME VARCHAR (256) NOT INLINE CPE_DEVICE_FILE_FORMAT VARCHAR (256) NOT INLINE CPE_RESET_EVENT VARCHAR (256) NOT INLINE CPE_CONFIG_TYPE CHAR (10) CPE_BLANK_PARAM VARCHAR (40) INLINE 1 table found. (primary key columns are indicated with *)
3. At this point, you are primarily concerned with the DEVICE_TYPE_UID. In my example, it is ‘2401’. We can now look at all of the options associated with this device using the following query :
SELECT * from BWAS.DEVICE_OPTION where DEVICE_TYPE_UID = 2401 ;con1: Command> select * from BWAS.DEVICE_OPTION where DEVICE_TYPE_UID = 2401 ; < 12904012, 2401, conferenceDevice, N > < 28573002, 2401, authenticationMode, enabled > < 46250484, 2401, e164Capable, N > < 29374604, 2401, forwardingOverride, N > < 90879096, 2401, intelligentDevice, Y > < 91040296, 2401, mobileDevice, N > < 16150412, 2401, mohDevice, N > < 49242892, 2401, pbxIntegration, N > < 83439424, 2401, registration, N > < 14534300, 2401, routeAdvance, N > < 70967144, 2401, staticRegistration, Y > < 16213366, 2401, supports3264Hold, N > < 97868544, 2401, trusted, N > < 45655300, 2401, useASAddressFlag, N > < 22684914, 2401, videoCapable, N > < 24849980, 2401, webBasedConfigURL, > < 82896368, 2401, ringbackToneEarlyMediaSupport, rtp-session > < 81499856, 2401, authenticateRefer, Y > < 25194988, 2401, autoConfigSoftClient, N > < 32188506, 2401, mobilityManagerDevice, N > < 3381306, 2401, requiresBroadWorksDigitCollection, N > < 16195688, 2401, requiresBroadWorksCallWaitingTone, N > < 58551144, 2401, requiresMWISubscription, N > < 17414268, 2401, useHistoryInfoHeader, N > < 50192144, 2401, aocCapable, N > < 94991328, 2401, supportCallCenterMIMEType, N > < 46558876, 2401, trunkMode, user > < 75805096, 2401, addPCalledPartyId, N > < 66933524, 2401, supportIdentityInUpdateAndReInvite, N > < 56298980, 2401, unscreenedPresentationIdentityPolicy, profilePresentationIdentity > 30 rows found.
4. Now you need to determine what you want to change. The Signaling Type is currently ‘Intelligent Device Addressing’. Do you want this to be Intelligent Proxy Addressing ? Change the ‘ useASAddressFlag’ value :
Command> UPDATE BWAS.DEVICE_OPTION set OPTION_VALUE='Y' where DEVICE_TYPE_UID = 2401 and OPTION_NAME = 'useASAddressFlag';
Do you want to change this to a NON Intelligent device? Update the ‘intelligentDevice’ value :
UPDATE BWAS.DEVICE_OPTION set OPTION_VALUE='N' where DEVICE_TYPE_UID = 2401 and OPTION_NAME = 'intelligentDevice';
As you can see, it is fairly easy to modify these values. I do stress – ONLY PERFORM THIS ON YOUR DEV/LAB ENVIRONMENT.