FXO private line

Posted: April 13, 2006 by sankar in Callmanager Express

To provide a private line for a user (so that he always uses the same FXO line to call out)

ephone-dn 1

number 1000

trunk 82

voice-port 1/0/0

connection plar opx 1000

dial-peer voice 1 pots

destination-pattern 82

Port 1/0/0

When the user goes off hook and dials a number 5551010, CME will prefix 82 to the number to make it look like 825551010. This will match the destination-pattern 82 and 82 is stripped off and rest of the digits are sent to PSTN.

  1. alsindi says:


    I have tried the above many times, but it doesn’t work, they say the only way it will work is through Translation Rules that it could identify the calling extension to associate it with the voice port.

    has anyone tried the above and it worked???

  2. bagus says:

    I have it work by adding T after 82:

    destination-pattern 82T

    The side effect is after I off-hook the phone, it will automatically connect to fxo port, but it still work.

  3. Brian D. Browne says:

    The problem with Cisco’s implementation of this functionality is that calls made using this private line GENERATE NO CDR. This in my opinion puts Cisco at a dis advantage when compared to other major competing products which all provide private line functionality without sacrificing the ability to capture call records via cdr. I have documented the problem in the UC500 support comunity asked the customer to report the problem to Cisco TAC and the following is Cisco’s response:

    “As we discussed the current behavior is expected as the line is being
    directly connected to the Telco.

    In order for that second line to record calls on CDR, it would need to
    be set up as a regular line, then configure a new dial-peer to match all
    call from that line, and send them out the same FXO port, this way the
    UC520 will actually make the routing decisions and the call will be
    recorded in CDR.”

    Honestly, I am a bit dissapointed by this response. The way the private line currently works for call handling, is exactly the way you along with other UC500 users want it to work: Just like a key system, and you should not have to sacrifice CDR records in order to get that functionality.

    You select a key and you get a dedicated private line. This operation is typical on many other key systems. (Eg Nortel Norstar, Nortel BCM, Avaya IP Office, Avaya Partner Plus ACS, Panasonic TD1230, etc). In all these systems, it is standard that CDR information is generated which contains the dialed number of the calling party as well as the line which was used.(I can give you samples if you require).

    This should not be a difficult thing for Cisco to do. I believe it was an oversight on Cisco’s part in that the CDR package was not modified to accomodate this feature. I hoped that this would have been addressed in release 8 of CME, but apparently it was not. Somehow, this needs to be brought to the attention of the Cisco CME development team so that, at the very least, it can be incorporated into the next major release of CME.

  4. Hi Brian,
    This is very good question. CME router doesn’t do CDR for PrivateLine.
    There is a good reason for this – Hey it’s the private line!! thats why.
    However, you might give call-forwrading trick a go. I hve not tried this but there are chances this might do the magic!

    ephone-dn 10

    let me know how you go. My lab is shut so can’t really simulate this.

    • Brian Browne says:

      Pushkarbhatkoti, not providing CDR for a “private line” because its a “private line” is not at all a good reason. It not even the official Cisco reason! As I stated in my previous post, Cisco’s TAC official response was:

      ““As we discussed the current behavior is expected as the line is being
      directly connected to the Telco”

      Also, you should know, that the term “private line” really refers more to the method in which the line is selected and external calls terminate on it(Direct line selection by pressing a dedicated key on the phone, rather than it’s privacy attributes. If that is the intent however, many Call Accounting systems including ours (Call Tracker) allow for private extension treatment in a number of ways. additionally, some PBXs even allow the administrator to suppress CDR for the extension. This is not what we are talking about here with CME CDR however.

      No other PBX vendor we know of (and we have worked with quite a few including Nortel, Avaya, Mitel, Fujitsu, Toshiba, Asterisk, Altigen, Panasonic etc) due to our work in Call Accounting (Call Tracker) treats CDR on a “private line” this way. They all provide call detail records on the call. I maintain that this is a deficiency in the Cisco CDR package that needs to be addressed. Thank you.

      • ahmad says:

        Can you plz put an example for this configuration?

      • Ahmad says:

        hello all, i need to make port 0/0/2 to all users use it when users press 09 number will auto be tack port 0/0/2 then user will dial the rest of number 0933060743,
        please help

  5. Ahmad says:

    hello all, i need to make port 0/0/2 to all users use it when users press 09 number will auto be tack port 0/0/2 then user will dial the rest of number 0933060743,
    please help

  6. Ehsan says:

    it works like charm.
    Thank you for your useful post.
    I have question
    We have need call duration limit on CME for ISDN or H323 . can any IOS command or script or EEM support this feature ?

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 )

Twitter picture

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

Facebook photo

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

Google+ photo

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

Connecting to %s