Rollovers not reporting as PrimeDN in CDR

[tiver43809]

Ver 4.5 I have some rollover ext that send cdr with the rollover instead of the PrimeDN. How do I make it quit doing that. It is not on all phones, and it is NOT version 5 which has that option.

Thanks
Terry

 

[GHTROUT]

Do the KEY 1 and above DNs appear as KEY 0 on other sets? Could that be why there are call records against them?

Dogs roll over.


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[SAMMEE2]

I've always used CLID entry "D" for all but the Prime DN.

Key 0 SCR 4512 1=Your Clid entry

Key 1 SCR 34512 D All other line keys

 

[tiver43809]

GHTROUT I will check that, And Sammee2 that would be ok I could add them in the call accouting system using sql if they like that. These numbers are random and when we trace them back we find that they are rollovers for a prime DN. I guess I should of mentioned the random part huh? I feel like a user calling a help desk with only half the information needed.

 

[GHTROUT]

What sammee2 posted has nothing to do with what you see in CDR records. All that does is send the CLID from KEY 0 to the party you are calling.


~~~
[small]GHTROUT.com | Get the Input/Output Manuals | Tek-Tips FAQs | Recent Replies[/small]

 

[PhoneGuyy]

I just got asked this same question from one of our customers, so was wondering what the fix or answer is?

 

[tiver43809]

Never found one

 

[SAMMEE2]

Dialing from non prime key: When an external call is set up from a digital
set with multiple DNs programmed using any key other than the Prime DN
key, the Meridian 1 outputs a CDR N-record at the end of the call. The
ORIG-ID field of the N-record holds the value of the Prime Key DN.
A new class-of-service (CLS) is provided for digital sets. When the CLS
is OKCH then the ORIG-ID field of the N-record will contain the actual
originating DN.
When the CLS is PKCH then the ORIG-ID field of the N-record will contain
the Prime DN. PKCH is the default setting.