Sonic Telecom - Support


Where can the telephone history be found at comity® server?	Every dialer has got it’s own directory in c:\\comity\\config. The directory name is the same as the device (TAS) serial number, which you can get by pressing the right mouse button over the serial number field in comity®. The telephone history will be saved per default in this directory in the file named by the call time like: Tel_JJJJMMDD_HHMM.txt (Ex. Tel_19991013_1747.txt)


At ISDN/IP download the old (wrong) configuration was loaded. It is not possible to update the configuration. What has to be remarked?	Before download the new configuration must be prepared. There are two ways: 1. Over Connection -> MAMS Support -> prepare data for server or during the ISDN/IP download in the appearing Confirm-Window instead of YES 2. Press the OK button for prepare data new and then transmit.


Where can one see, whether the dialer has done its watch dog calls?	Via the path Tools -> Watchdog -> Show all watchdog calls.


How can the configuration be printed? At the moment, it is not possible to print the configuration over Print -> with preview [-> print direct]->Device configuration.	In this case it is possible to export the configuration via .ccs file over File -> Export and then open this file with a text editor.


After firmware update over Connection -> FLASH update -> ISDN FLASH download is neither a Local nor an ISDN download of the configuration possible. Why?	This can happen if the software structure was changed by the FLASH download. The ISDN Flash download will be finished only after the reset call. You might: 1. After firmware download wait for reset call from dialer (Can last some minutes). 2. Over Tools -> Database management start the Update DB from userstring. 3. Prepare a new Konfig.bin. 4. ISDN download repeat.

Dialer has received a local FLASH update from software structure 8 (time-independent routing) to structure 10 or 11 (time-dependent routing), but in comity® you can´t use the time-dependent routing. Why?

Because comity® needs first the information that the dialer can now use the time-dependent routing. There are two ways for the update from one structure to another:

1. Over Connection -> Flash update -> ISDN Flash
download.

2. Over Connection -> Flash update ->-> Local
Flash download.

At the first example the update is just completed after the reset call. You must wait until the dialer makes a reset call to the server (Can last some minutes).

At the second example during the local flash download you will receive the comity error message \"Wrong DOR-Version! Can´t Download! DOR-Version in dialer: yy DOR-Version in Database: XX Updating Database? YES. Confirm it with YES. After this you must update the configuration of the dialer over Connection -> Local download.


No reaction from comity® during the preparation of the konfig.bin (only DB structure 11). Why?	This problem was up to date with older versions of comity® if there were infinite loops at alternative Carriers in the configuration. This problem is solved with comity® versions over 2.2.


Start of comity® causes Dial Up Networking - Internet connection.	It is a default setting of Win 95. Over Start -> Settings -> System control -> Internet -> Connection choose no automatic connection and then the OK button.


On comity® start, the error message \"no support of address family\" appears.	It is a message of Win95 to show that for communication between comity®, MAMS and/or a dialer a TCP/IP-Protocol is essential. Check whether the TCP/IP is configured. You must install the network over Start -> Settings -> System control -> Network. For further information look at *"Chapter 4 - Starting and setting up comity"* in the comity® manual.

What has to be noted if the dialer is connected between the NT and the comity® - server?

Because the NT has more than one call numbers the dialer and the ISDN card should have different call numbers. MAMS has to be configured as well with a different number. Therefore make a connection to MAMS. Then press with the right mouse button the connection icon for opening the menu. Over Properties -> Connection, then enter in the Destination – field the following:

For versions from comity® 2.3 or MAMS 1.37f type: /n=X /m=Y

For the earlier versions of comity® or MAMS: X Y
Here indicates X the number which is the receive call number of MAMS, and Y the own number of MAMS, which will be send from MAMS. Both numbers must be only local numbers without the prefix.

Example:
C:\\comity\\config\\MAMS.exe /n=7381 /m=7382


How can one enable Sonic Telecom GmbH remote access to a dialer?	The call number of Sonic Telecom GmbH +49(0)6172 5928 0 has to be entered in remote center four in the comity® -> remote control. Note: The remote center four will be used only for incoming calls. The dialer will never make a service call to this remote center.


Which flag has to be set in comity® -> Device Setup for ADC 30XXX?	The flags external channel demanded on pbx - setup and in earlier comity® versions (under 2.4) disable SABME to PBX if layer 2 missing should be set for every dialer in each configuration. The ADC30XXX can be configured only for one protocol and one port setting.

Which flags have to be set in comity® -> Device Setup for ADC 401?

The flags external channel demanded on pbx - setup and protocol and port settings -> standard in all fields (normal channel allocation, only successful used channels without rejecting calls with the cause \"channel not available\" will be used) should be set for every dialer. In this case the dialer learns the channel allocation permanently. This setting is especially good for normal channel usage with the right rejection of blocked channels.

Which flags have to be set in comity® -> Device Setup for ADC 403?

What should be noted at updating the Konfig by the ISDN/IP - Download?

The new configuration must be prepared for MAMS. There are two possibilities for this operation:

1. Comity® -> Connection -> MAMS Support ->
Prepare data for server (current device)

2. Press the ISDN dowload button, on request
enter the called number and confirm with OK.


What is important at ISDN-Download via carriers?	Do not use carriers that compress data during the transmission through their network.


What does the message information \"For the device XXX comity has more than one call per day detected. Please check the reasons\" in the list \"waiting for incoming calls\" mean?	That is made for security reasons to detect to many remote center calls as soon as possible. If the dialer calls his remote center during the last 24h more than one time this message will appear. The message can also come up if a watchdog call comes to late.


When do we use the db - service?	1. Create a new Database (DB). 2. Copy existing DB's. 3. Merge DB's. 4. DB-Reorganisation. 5. Transform different DB formats. 6. Transform different DB Systems.


After the change of the password for the level 2 entry in comity® -> Remote Control-> password for local access, a remote control of the dialer is not longer possible.	The password for level 2 must be always set to the standard password for Level 2.

After the Download the error message \"Download contains only remote centers\" appears. Why?

These reasons are possible:

1. No carrier is defined.

2. Duration in pricescript is under 100 ms (in earlier
comity® versions).

3. Cost of each charging unit is under 0,001 (in
earlier comity® versions).

4. No routing entry is defined.