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 Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Private Recieved is not working on IP trunks

Status
Not open for further replies.

nooop

Technical User
May 12, 2007
311
US
Same issue I have been working on. I noticed a new discovery. If a DID ie is ending 5206, and public recieved is set to 5206 and we listen for 4 digits we get calls from teh PRI perfectly. If I dial from another site and dial 5206 we get the call perfectly. The issue is Private recieved, if I have a set that does not match the last 4 digits of the DID, then IP trunks will not route to the target line, it goes to prime and rings the front desk of that site. I have changed the block to Private,public,national, and no changes. I tried CDP, UDP, and no luck. I have tried 3 digits priv recieved, and 4 no luck. Why will my target line only answer the public recived and not private? Do i need another target line for each set and put the DN as public recieved?
 
I assigned a second target line set to ring only, and public recieved to the DN, and now it works. Not sure why Priv recieved does not, because it would be nice to just set the priv in the existing target line, but for a small office of 12, I am happy now.

Thanks
 
I think you need MCDN to use only 1 target line for both public and private recveived digits
 
I think at 3.7, for sure 4.0 you can have under 1 Target Line a different Private Recvd. then Public Recvd. So you only have to apply 1 Target line to a telephone. Public Recvd. would be your incoming DID from Telco. Private recvd. would be your VoIP trunks.

Adversity is Opportunity
 
I am on BCM 400 4.0 at site 1, and BCM50 2.0 at site two. But good to know that target lines can perform only 1 role on lower software versions. My work around is working like a champ, I am a happy person now.

Thanks
 
It may be working, but something is still wrong.
You shouldn't have to do that ... unless you don't have an MCDN keycode.
The MCDN keycode turns on Private Networking, as well as other features like name display, TAT, TRO, etc.
The UIP tab on the BCM monitor tool will allow you to view the setup messages and determine the TON the call is using. If it doesn't show up as Private/CDP, you'll never match the digits up in the Target Line Private Recvd. Number field.



-SD-
 
I don't have mcdn licensed. That explains it. Nortel never made it clear to me why to purchase that. I would have purchased it for sure. So this would never had come up then. I will purchase that asap.

Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top