Home > Uncategorized > Using account codes for client billing with Lync

Using account codes for client billing with Lync

Background: Traditional PBXs have often implemented what are known as account codes. These account codes are usually two digits and are used by companies that work with multiple clients and need to bill those clients for long distance calls made on those clients behalf. For example, a marketing firm might be placing calls for one of their clients and needs to track and bill for calls made for that particular client. With account codes the calling person dials the destination phone number and after hearing a double beep then enters a two digit account code. The account codes and double beep are provided by the local phone carrier. The customer then receives a bill from the carrier that shows the calls made according to account code. Some PBX manufacturers even provided a serial interface known as the SMDR cable that could be connected to a PC with software that collects in real time the inbound and outbound calling information which can then put in a database or spreadsheet.

Question: How can account codes be implemented in Lync? Although you can’t replicate the scenario described above with the double beeps and codes entered after the number, there is another scenario that does work in Lync.
Answer: Instead of putting the account codes at the end of the number you can have the outbound caller put them in front of the number to dial. For example instead of entering 208 555 1234 in Lync, the caller enters 832085551234 (account code of 83). You then use a Trunk Configuration Associated Translation Rule to remove the account code prior to sending the call to the PSTN. Although you can do this on a Media Gateway, by doing this on a Trunk Configuration the Monitoring Role will still store the dialed number in the LCDR database with the account code. Unlike with a legacy PBX, you are free to use any king of account codes you like, and do not need to have them created by your local phone carrier.
Managing the Trunk Configuration Translation Rules: Unlike media gateway rules, Lync Trunk Configuration Translation Rules can be added and removed with Powershell. This makes it very easy to change account codes anytime you like.<br>
Suppose you have a Trunk Configuration with the identity of: pstngateway:
To add a translation rule: New-CsOutboundTranslationRule -parent pstngateway: – Translation ‘$1’ -pattern ‘^53(\d{10})$’ -name Code53 -priority 2<br>
The above rule adds an account code that removes the number 53 from a 12 digit number and makes it the second rule in the list.

To remove a translation rule: remove-csoutboundtranslationrule -identity “pstngateway:”

Once you have collected this data then you can use Dell/Quest MessageStats to report against it.

Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: