chriscaton
Vendor
I have an application for a car dealership where their call accounting folks are requesting forced and verified account codes. Sepcifically the request is this:
Schedule P - SMDR Integration. (outbound phone call tracking)
Physical Connection:
The Dealership phone vendor must provide the physical connection to the phone system.
This connection includes all data cabling and adapters needed between the phone system
and the THGG utility server.
The THGG utility server communications port #1 is used for SMDR integration. This is a
9-pinconnector closest to the mouse and keyboard connectors on the back of the server. It
is an industry standard DB9 RS232 male style interface.
** SMDR data transmission is usually limited to 50 total cable feet. Distances greater than 50 feet may require
additional communications equipment such as short-haul modems or Ethernet device servers.
**If the phone system is not in same building as the THGG servers, additional connection equipment such as Ethernet
device servers may be needed.
Phone System Programming:
The Dealership phone vendor must activate forced and verified account codes on the
phone system.
**These codes require a salesperson to dial a personal account number before placing an outgoing call. This feature can
usually be set on a per extension basis, eliminating the need for Service and Parts departments to enter codes.
**The phone system MUST be tracking the account codes. Call tracking implemented by a long distance carrier alone
will not suffice. You can usually identify carrier tracking because it requires a code to be entered after the number is
dialed instead of before.
Connection Settings:
The Dealership phone vendor must provide connection settings.
These settings include:
• Baud Rate
• Data Bits
• Parity Type
• Stop Bits
• Flow Control
Data Format:
The Dealership phone vendor must provide an explanation of the SMDR data output.
This explanation needs to include which characters indicate the following fields and in
what time
format they appear, i.e.: hh:mm:ss, hh:mm, hh:mm:10th of minutes, etc.
• Call Start or Call End Time
• Call Duration
• Number Dialed
• Account Code
• Outgoing Call Indicator
Optional fields can include:
• Call Start or End Date
• Extension Number
• Line Number
I've been reading through the old threads and cannot seem to completely understand whether to use a SMDR, CTA or both to accomplish this. any suggestions most helpful. Specifics greatly appreciated.
Thanks
Chris Caton
thread799-778939
Schedule P - SMDR Integration. (outbound phone call tracking)
Physical Connection:
The Dealership phone vendor must provide the physical connection to the phone system.
This connection includes all data cabling and adapters needed between the phone system
and the THGG utility server.
The THGG utility server communications port #1 is used for SMDR integration. This is a
9-pinconnector closest to the mouse and keyboard connectors on the back of the server. It
is an industry standard DB9 RS232 male style interface.
** SMDR data transmission is usually limited to 50 total cable feet. Distances greater than 50 feet may require
additional communications equipment such as short-haul modems or Ethernet device servers.
**If the phone system is not in same building as the THGG servers, additional connection equipment such as Ethernet
device servers may be needed.
Phone System Programming:
The Dealership phone vendor must activate forced and verified account codes on the
phone system.
**These codes require a salesperson to dial a personal account number before placing an outgoing call. This feature can
usually be set on a per extension basis, eliminating the need for Service and Parts departments to enter codes.
**The phone system MUST be tracking the account codes. Call tracking implemented by a long distance carrier alone
will not suffice. You can usually identify carrier tracking because it requires a code to be entered after the number is
dialed instead of before.
Connection Settings:
The Dealership phone vendor must provide connection settings.
These settings include:
• Baud Rate
• Data Bits
• Parity Type
• Stop Bits
• Flow Control
Data Format:
The Dealership phone vendor must provide an explanation of the SMDR data output.
This explanation needs to include which characters indicate the following fields and in
what time
format they appear, i.e.: hh:mm:ss, hh:mm, hh:mm:10th of minutes, etc.
• Call Start or Call End Time
• Call Duration
• Number Dialed
• Account Code
• Outgoing Call Indicator
Optional fields can include:
• Call Start or End Date
• Extension Number
• Line Number
I've been reading through the old threads and cannot seem to completely understand whether to use a SMDR, CTA or both to accomplish this. any suggestions most helpful. Specifics greatly appreciated.
Thanks
Chris Caton
thread799-778939
