Avaya Support Forums  

Go Back   Avaya Support Forums > Enterprise PBX Communications Systems

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 12-03-2014, 12:55 PM
alindquist alindquist is offline
Whiz
.
 
Join Date: May 2010
Posts: 35
alindquist has 10 reputation points
Default Use of the DB9 on CLAN adapter.

Hello everyone,
I have a vendor who thinks that the DB9 port on the TN799 CLAN adapter can be used to collect call records. I have searched the whole web and I can't find out what that thing is used for. Does anyone know the purpose of the DB9 port?

Thanks,
alindquist
Reply With Quote
  #2  
Old 12-05-2014, 12:57 PM
mlombardi1's Avatar
mlombardi1 mlombardi1 is offline
Legend
 
Join Date: Sep 2010
Location: New York
Posts: 453
mlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation pointsmlombardi1 has 25 to 49 reputation points
Default

I'm pretty sure the DB9 on the TN799 is intended for a PPP connection, such as dial-up but I've never used it myself.
Reply With Quote
  #3  
Old 12-06-2014, 08:16 AM
rbrookes's Avatar
rbrookes rbrookes is offline
Guru
.
 
Join Date: Jan 2012
Location: rbrookes@avaya.com
Posts: 141
rbrookes has 10 reputation points
Default

This migh help you, found it in the Avaya Aura Soludion Design Considerations and Guidelines, Release 6.2, 03-603978, Issue 1, July 2012, around page 233 or 234:
http://support.avaya.com/css/P8/documents/100156905


Registration considerations for adjuncts
Both TN799 C-LAN circuit packs and Processor Ethernet can be used to support adjuncts and


services such as Call Management System (CMS), Avaya Aura
® Messaging, Call Detail
Recording (CDR), DMCC-based recording, and Application Enablement Services (AES). The
following adjuncts and services merit special allocation of C-LAN or Processor Ethernet
resources.
• If CMS is being used, dedicate one TN799 C-LAN circuit pack to support it. Alternatively,
a single Processor Ethernet interface can support up to two CMS applications.
• If Messaging is being used, dedicate one TN799 C-LAN circuit pack to support it.
• If neither CMS nor Messaging is being used, but

Connect Adjuncts: Asynchronous
Connections

field is set for thru C-LAN, then one TN799 C-LAN circuit pack must be
allocated to support adjuncts such as CDR recording and PMS links. Alternatively, a single
Processor Ethernet interface can support up to two CDR applications.
• A single Processor Ethernet interface can support up to 16 AES applications.
The information provided in the preceding bullet items is used to determine the number of CLAN
circuit packs and/or Processor Ethernet interfaces that are required to support just the
adjuncts, based on registration considerations

Also see ADMN101212 article https://support.avaya.com/ext/index?...&id=ADMN101212

__________________
Russ Brookes | Avaya, KCS Leader | +1 613.771.7590 | rbrookes@avaya.com | NA Eastern Time Zone

Last edited by rbrookes; 12-06-2014 at 08:38 AM.
Reply With Quote
  #4  
Old 12-12-2014, 06:40 AM
alindquist alindquist is offline
Whiz
.
 
Join Date: May 2010
Posts: 35
alindquist has 10 reputation points
Default Thanks for all the help!

The reason that this came up is that the customer's pollers are receiving double entries in the CDR records and we are trying to come up with a way to monitor the data coming from the CLAN to determin if the CM is sending the data twice. The customer has opened a ticket with Avaya and it has gone up to Tier 4. They are still working on a solution. I will post the resolution as soon as we here back form them. Thanks again for all your assistance, it is greatly appreciated.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:19 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.