grahekf

I am using the change isdn public-unknown-numbering command to try to change the outgoing caller ID number being sent.

We have different ID's being sent depending on the extension number dialing out. It looks similar to this:

Ext Len - Ext Code - Trnk Grp- CPN Prefix
4 2 1 262XXX1234
4 2 5 262XXX1234
4 3 1 262XXX1234
4 3 5 262XXX1234
4 4 1 262XXX1234
4 4 5 262XXX1234
4 61 1 262XXX1235
4 61 5 262XXX1235
4 62 1 262XXX1235
4 62 5 262XXX1235
4 63 1 262XXX1235
4 63 5 262XXX1235

Currently extension 6100 properly shows 262-XXX-1235 when dialing out.

If I change the CPN prefix to 262-XXX-1236

(i.e
4 61 1 262XXX1236
4 61 5 262XXX1236
)

I no longer get the correct ID. It displays the main number associated with the PRI (i.e 262-XXX-1000)

Am I missing something? Can the carrier only allow certain ID's through?

Frank

liquidvw

Are you sure your are testing with trunk 1 or 5. Sounds like you have another entry in the list like:

4 61 blank 262-XXX-1000. This way if any trunk is used it will send 262-XXX-1000.

I would do a list trace on your test extension to verify the trunk being used is 1 or 5. Also check for other entries in the list.

PBXtech.info

 

grahekf

Thanks for responding. Trunk 5 is used only for outgoing calls. Trunk one is used for incoming and outgoing. It uses trunk 5 first and then trunk 1 for overflow.

There are no blank entries either. The odd thing is I only change the CPN Prefix by the last digit and it doesn't work. I change it back and it works again. Makes me think there is somewhere else to look.

grahekf

I did try the list trace and it shows me that it is correctly using trunk group 5.

It is also correctly showing me

Calling Number & Name 262XXX1236 NO-CPName

but yet the caller ID coming through is still 262XXX1000

So does this tell me it is being done at the carrier?

stubborne

Possibly. is 1236 a valid DID from the LEC? If not, the LEC would suppress any invalid DID and replace with the main number. Is your DID range 1000 - 1235?

__________________
Stu

grahekf

Sort of. The 1236 is a valid DID range from one carrier. The 1000 range is from the carrier handling the outgoing traffic. The only explanation as far as I can see is that the carrier is allowing 1235 to be passed through but not 1236.

PBXtech.info

 

liquidvw

Maybe. The LEC may be changing what you are sending out. Open up a "information only" ticket with you LEC and find out.

ahays

If your "list trace tac" shows the correct information passing to the PRI and it is not reaching the destination as you are sending it then: YES, your carrier is not allowing you to manipulate the digits to your liking. As suggested, contact your carrier to understand why. They may have a setting wrong or they may have some internal policy restricting you from making your proposed change.

regs,

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

grahekf

Yes, the carrier was not recognizing the number in their database. They added the number and now it works properly. Thanks for all the help.

KenHeer1

I'm having a similar problem. Our called ID is displayed correctly on local calls but long distance calls, even ones that stay within our provider, AT&T, do not show the called ID, it comes up as unknown or unavailable. I've spoken with AT&T and they have assured me that we are set up on their end to be able to pass whatever we have set up as our caller id.

I don't know if this is the area where I would change it, but when I enter the command "change pub 0", I get the same screen as what grahekf is showing but my table is empty.

Can anyone point me in the right direction? I'd also like to know where a good source of training would be for this.

Thanks
Kenny