Avaya Support Forums  

Go Back   Avaya Support Forums > IP Telephony and Convergence

Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old 04-10-2013, 01:43 PM
garg19 garg19 is offline
Whiz
 
Join Date: Feb 2013
Location: Houston
Posts: 30
garg19 has 10 reputation points
Default Query on station form- urgent

Main Number- 817-865-4400 Up to 4800



1408 and 9408 type of phones

Main Number- 817-865-4400 Up to 4800

Ext: 4751----- When this ext making an outgoing call then the outbound caller id must be 817-865-4751

In the Station form; in the Per Station CPN - Send Calling Number? Field changes to Y

Ext: 4556--- When this ext making an outgoing call then the outbound caller id must be 817-865-4400

In the Station form; in the Per Station CPN - Send Calling Number? No changes

Ext: 4551----- When this ext making an outgoing call then the outbound caller id must be 817-865-4500

Last edited by garg19; 04-10-2013 at 01:49 PM.
Reply With Quote
  #2  
Old 04-10-2013, 07:00 PM
rvengco rvengco is offline
Whiz
.
 
Join Date: Jul 2010
Posts: 35
rvengco has 10 reputation points
Default

Hi garg19,

Is your requirement like this?

Ext: 4751----- When this ext making an outgoing call then the outbound caller id must be 817-865-4751

Ext: 4556--- When this ext making an outgoing call then the outbound caller id must be 8178654400

Ext: 4551----- When this ext making an outgoing call then the outbound caller id must be 8178654500
You may want to configure them in the change public-unknown-numbering form

You may try the setting below:

change public-unknown-numbering 4 Page 1 of 2
NUMBERING - PUBLIC/UNKNOWN FORMAT
Total
Ext Ext Trk CPN CPN
Len Code Grp(s) Prefix Len


4 4751 1 817865 10
4 4556 1 8178654400 10
4 4551 1 8178654500 10

I am assuming you are using ISDN for your trunk and in the above example, I use trunk group 1 as the trunk for ISDN.

I put there the CPN length of 10 which will control on how many digits you would like to send to service provider.

The example above shows that if you dial from extension 4751 going out to trunk group 1, you have a prefix of 817865. The CPN Prefix will be appended to the extension thus resulting to 8178654751

For the second example if you make a call from extension 4556 going out to trunk group 1, the CPN prefix should be added to your extension 4751 as well which should be 81786544004556 but since the CPN length was set to 10 then only 8178654400 will be sent out as your outbound caller id.

For the 3rd example, it should be the same thing as the second.

Hope this helps

Last edited by rvengco; 04-10-2013 at 07:10 PM.
Reply With Quote
  #3  
Old 04-10-2013, 08:26 PM
garg19 garg19 is offline
Whiz
 
Join Date: Feb 2013
Location: Houston
Posts: 30
garg19 has 10 reputation points
Default

Thanks a lot for your reply.

1. The solution given by me for the 1st two is incorrect. Will my solution work too?
2. We have total 300 extensions where I need to do this.
and I think it will be very difficult to programme every ext in unknown numbering plan right.
3. Is this programming is extension wise?

Thanks again

Amit
Reply With Quote
  #4  
Old 04-11-2013, 10:32 AM
rvengco rvengco is offline
Whiz
.
 
Join Date: Jul 2010
Posts: 35
rvengco has 10 reputation points
Default

Hi garg19,

I apologize, if the suggestion doesn't work, may I know what went wrong with the outbound caller id when you did the same?
I agree with you that it is difficult to program each extension in the unknown-numbering plan if the each of your extensions need to be translated to a different outbound callerid. I just thought you are limited to your 3 examples only but didn't know that you need to translate it for a lot of extensions.

Usually, whatever customer extensions are assigned to, are part of the outbound caller ID of the customer for example: for 4xxx extensions, you can just put 4 their under extension length and put the required cpn prefix. it should already translate to cpn prefix + 4xxx as the outbound caller-id thus not needing to add all the extensions.. but in your requirement you would like to translate an extension number to an outbound caller id in which the extension is not a part of the outbound caller-id so if you have a lot of extensions that needs translating then it will be a tedious task for programming.
Reply With Quote
  #5  
Old 04-11-2013, 01:09 PM
garg19 garg19 is offline
Whiz
 
Join Date: Feb 2013
Location: Houston
Posts: 30
garg19 has 10 reputation points
Default

Thanks for the reply.

Here is what I am thinking...If I do below will this work? because below looks weasy for me to do...Pls suggest

Ext: 4751 (150 extensions) ----- When this ext making an outgoing call then the outbound caller id must be 817-865-4751

In the Station form; in the Per Station CPN - Send Calling Number? Field changes to Y

Ext: 4556 ( 100 extensions)--- When this ext making an outgoing call then the outbound caller id must be 817-865-4400

In the Station form; in the Per Station CPN - Send Calling Number? No changes

Ext: 4551 ( 10 extensions)----- When this ext making an outgoing call then the outbound caller id must be 817-865-4500
I will programme them in publick- unknown because only 10 extensions.

Thanks again Thanks
Reply With Quote
  #6  
Old 03-12-2014, 09:52 AM
fsloss fsloss is offline
Aspiring Member
 
Join Date: Mar 2014
Posts: 1
fsloss has 10 reputation points
Default

Hi garg19,

Not sure if you have got this sorted yet, but it seems that you might have misunderstood what Per Station CPN - Send Calling Number? does.
This allows per station control of whether to Send CLID or Withold CLID. This does not control the number the station gives out as CLID.

Do you still require help on the public unknown numbering?

Regards,
Finn
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 06:51 AM.

This Forum is provided solely for the use and convenience of Avaya customers and partners. Use of the Forum is subject to the Terms and Use and Privacy Statement found at www.avaya.com. No other use is permitted. The Forum including all content posted is “AS IS” and Avaya expressly disclaims all warranties and/or guarantees as to its accuracy, reliability, usefulness, quality or non-infringement of intellectual property. Avaya reserves the right to remove any content posted on the Forum at any time and for whatever reason.

Avaya will not be liable for any content posted on this Forum, including, without limitation, any errors or omissions or for any losses or damages of any kind incurred as a result of use or reliance on any content, regardless of its origin.

You expressly understand and agree that you assume all risks associated with use or reliance on this content.