Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Info required

Status
Not open for further replies.

mabery

Technical User
Oct 1, 2001
125
GB
On Opt 61 using software 25.15 can it provide extn level billing information for network provider. They need to see 1840. DN. number dialled. Have got 1840 workin to select specific route but & LID 1. What else do I need to do ?
 
LID 1 ? for cdr you need to build cdr data in ld 15, build a adan tty user cty and turn it on per route..

john poole
bellsouth business
columbia,sc
 
thanks, as the information is being read and processed by the network provider, they need to see everything, will this enable them to see what they want ?
 
yes, that gives orig number, number dialed and duration of call

john poole
bellsouth business
columbia,sc
 
okay , how do you 'turn it on' ?
 
Can you clarify something for me please ?
I thought that the tty port needs to be connected to an device ?
 
yes it has to dump to something... a pc with procomm works for me... it will be truned on when you complete cdr data and the adan build.. then on the routes cdr yes

john poole
bellsouth business
columbia,sc
 
okay, that is not want I need. All the call records are to be presented to the network provider so that they get all this information and process it. Nothing is done on site.
 
the network provider can give you a bill on your trunks.. but not your stations

john poole
bellsouth business
columbia,sc
 
Are you saying the Vendor needs to see the number 1840 in front of the number called on the trunk???


ie: 18401NPANXXxxxx Does this need to be sent out on the trunk to the Vendor?
 
In the RLB see what DMI it uses and then change the DMI to insert 1840 and the Vendor of the trunk should get the CLI of the phone making the call.
 
thanks, that is what has already been set-up and according to the Network Vendor, they are not 'seeing' this info. How can I check to see what is being sent out ?
 
Enable DCH messaging in ld 96 (don't do it in peak traffic times)

enl msgo XX <--- XX = dch number.

Then do a test dial. You should see what your system is sending on your maintenance terminal if it is configured with SCH MTC BUG.
 
what is the current situation with this - did you get it working
 
NO - there is no way that this will work, all the info can only be collected locally.
 
as far as i am aware - and i'm pretty certain - there is no way to acheive 'itemised / extension' billing on an option. Equally, billing by cli is not possible [if it was you could probably fake the og cli and bung the call on anther's bill! etc etc]
 
On Sept 7 he says "nothing is done on site" then 28 nov he says "the info can only be collected locally"

not sure what he wants, he was given good directions to collect all his data locally but that wasn't what he wanted.

You can get itemized extention billing on an option. You have to have your CDR set up and collected of course, but it will show you what extension calls where and for how long, the billing part is just software after that.

JohnThePhoneGuy

"If I can't fix it, it's not broke!
 
i think we're talking at cross purposes here.
when [in the uk] 'they' [they = third party networks] say they want extension billing - someone says 'yes i can do that'. but what 'they' really want is a form of dialling from the system as opposed to information from the system.
eg, what they want is an extension to go off hook and dial 9 + telephone number. what they want the switch to actually dial out is xxxx [access code which tells the pstn provider to give the call to a prticular third party network] + yyyy[extension dn number ie 2066] + a pause + full telephone number of called party.
this means that the network will produce bills for the customer under extension headings or department headings if yyyy = dept group.
systems like the panasonc kxtd have this as a built in s/w option which you just switch on. as the option uses ars only it needs the 'insert dn' into dialling stream ability together with an 'insert pause' ability - both of which can't be done.
The other way this 'can be done' [ie can't] is where the option provides a cli individual to the extn which the network 'reads' to produce a bill for that particular extn. However, I have spoken with network engineers who say they can't process this information anyway. Even if they could, the extn CAN send its own cli but what about all the extns with no o/g cli [ddi] assigned? To incorporate them you would have to give them pretend DDIs to allow them to give out an individual cli. However, if you say had 100 ddi's on a switch but 300 extns you would give a block of 200 ddis which could actually exist in the real world. ergo if you had some info on a customer you could make calls at his expense etc etc. the list is endless why this method does not work.

ie this is all about how the network produces a bill, ideally, at the exchange for the customer.
the only way the network can acheive this is by paying for cdr capture at the site and download the info via dial up etc and apply calculus to the cdrs - unless i'm wrong - which i'm not - or am i
 
Jusy like 1010 codes in the USA. On the RLI there is a DMI assigned to that RLI, chg the DMI to insert the 1840.




This is a Signature and not part of the answer, it appears on every reply.

This is an Analogy so don't take it personally as some have.

Why change the engine if all you need is to change the spark plugs.


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top