rhwimmers

Just setup a new site with an avaya G350 LSP with an 8700 head-end. When this site makes a FNPA call it comes to our core site and then out - its showing the number for the core site, instead of his 10 digit number. On another site that is using the same trunk group for FNPA calls, their 10 digit shows up correctly. Doing a trace I think I found that the new site says NO_CPNumber and the working site has a number their, and no name (which is fine).
Not sure where that CPNumber is established.
TIA
Ross

ahays

If we had your release information then we could direct you ... Please review: http://www.pbxtech.info/definity-ser...ost-forum.html

.al.

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

PBXtech.info

 

martinyoung

If these are ISDN calls you might also do a "disp isdn pub". When you added the site, did you put any entries in this table for it? If you did not, then it will use the data that is in the table for the site that is providing the trunks by default.

__________________
Marty
Retired Avaya DSIC tech

ahays

That's why I requested the Release info ... on later releases of CM the command is different. I'm pretty sure it's simply "change public-unknown-numbering" without the preceeding "isdn"

.al.

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

martinyoung

I believe it changed to that command on 2.1 or 2.2. I do know that if you try the command I suggested on a switch that does not support it, you will get an error message that suggests using the new command. That is how I found out it changed.

Release number is very important because there can be drastic changes between releases. They still don't include a command I have been asking to have for two decades. The ability to busy and release a hunt group.

Since an LSP cannot be a higher release than the host switch, it is probably a 2.1 or 2.2.

Rhwimmer, if you are still out there, try Al's command instead.

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

Thank you very much for the command, I believe we are on 2.0. Im glad I came back to check the message board as I didnt get an e-mail notification that someone had responded so I was glad to see you guys had!
Thanks again for the help.
It is the change public...


Ross

PBXtech.info

 

rhwimmers

I tried to do this on a LD PRI (DVA) trunk group and the error message I got was "not an isdn trunk group" For whatever reason, this DVA is Group Type = TIE? Im pretty positive this should be ISDN... I think if I change to ISDN it will do the CPnumber appropriately, but dont know if changing it from TIE to ISDN is service affecting or what else that could change?

ahays

If the trunk group type is not currently set to ISDN and it is working then it IS NOT an ISDN trunk group. Type "tie" indicates that it is a plain vanilla T1 and changing it to ISDN will simply make it stop working.

You cannot send outbound caller-id on a plain vanilla T1. You will have to issue a change order with your LD provider to get an ISDN circuit provisioned ... either changing the existing circuit (risky) or having a new circuit installed and then cancelling the old one once you know the new one is working properly.

.al.

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

rhwimmers

Gotcha- guess I didnt realize that TIE and T1 were the same, that helps a lot. But I think you answered my question...Cant output DNIS information on a T1 that is used for voice -- end of story?
Thanks

oozenoz

TIE and T1 are NOT the same!

The service references can get confusing, and as a result, can often cause errors when attempting to set up systems. T1 refers to the facilities, not the service.

Tie lines are (mostly) T1 or E1 spans that connect (or 'tie') PABX systems or sites together. Avaya uses the term TIE in their provisioning to refer to the type of service provided by the trunks... it adds a layer of complexity and confuses the heck out of a lot of people.

Here's what you need to understand about voice services and CPN presentation:

ISDN and QSIG both support voice and run on T1 facilities. These protocols are feature-rich - QSIG provides the ability to transfer and drop calls between systems, while both allow you to provide calling party number information. It is possible to use ISDN or QSIG protocol on tie trunks (those that connect private voice systems without going through the PSTN); however you have to be very careful when filling out the forms on the PBX....

IF the tie span between nodes A and B is loop start, ground start, or E&M wink, no CPN information can be passed. No more than it could be if you used any of these protocols on your local trunks to telco.

__________________
- calvin

rhwimmers

Gotcha - yeah that was a typo - meant to say didnt realize the "werNT" the same.
So if I switch these to ISDN instead of just T1 - I should be able to use the cpnumber info. The name comes from the telco right, so I have to let them know what number should say what? Looks like if you arent set to ISDN as the trunk type the trunk config doesnt ask if its ground/loop/wink etc etc..so that makes sense.
Thanks for the help
Ross

oozenoz

Yes. You will need to change the signalling type on both ends (change ds1) to ISDN, and probably change the trunk form as well. You say you have a second location that works properly? Do it the easy way and compare/copy the configs.:devil:

Yes. ISDN and QSIG both support the passing of customer to customer information elements that include calling name, but most LSPs won't support it. They use a database to pull name display when ANI is presented to the destination.

You're correct... in a way. ISDN, QSIG, ground start, loop start and wink are all communication protocols - you can only ever use one at a time and it has to be the same on both ends.

T1 signalling (ISDN, robbed-bit, common-channel or CAS) is configured separately from the Trunk Group service type (tie, public network, etc.). Signalling defines what language the systems talk, service type defines which end is going to be the network end (e.g., CO side) and which end will be the terminal end (e.g., customer prem) of the span. (In a typical configuration, your LSP would program their end as network and your local PABX would be terminal. In tie configurations this is the same - one end (presumably your hub location if you have more than two sites) would be network and the remotes terminal - but this is completely up to you do decide.)

__________________
- calvin