Quote:
|
Originally Posted by rhwimmers
So if I switch these to ISDN instead of just T1 - I should be able to use the cpnumber info.
|
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:
Quote:
|
Originally Posted by rhwimmers
The name comes from the telco right, so I have to let them know what number should say what?
|
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.
Quote:
|
Originally Posted by rhwimmers
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.
|
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.)