pbxn

I'd check with your telco to see what they are sending out on that PRI. You may have to request them to add a number to that PRI.

Rachelle

For your own sanity, you might turn on D-channel messaging for a few minutes and capture what your PBX is sending to the telco. Then you can contact the telco, knowledgibly, and find out how they have this site listed in their database. Now, not all telco's use the same database and sometimes they refuse to share with one another. That means that it is possible for your digits to go but the name part may be changed to "Indiana Call" for example. Again, you will need to touch base with your LEC and LDC to confirm.


rlc

gogoGophers

pbxn and Rachelle,

Thanks !

gogoGophers

Have an update: some more help please.....................

The LEC (SBC) says "everything's fine on our end". What a surprise !
Does the progress message "originating end is not ISDN" mean there is some problem/programming error on the Option 11. Advice/Course of action please.

Thanks again.


HH 12 UIPE_OMSG CC_SETUP_REQ REF 00000017 CH 2 23 TOD 1158
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5175486200 NUM PLAN: E164
CALLED #:15173047869 NUM PLAN: E164

DCH 12 UIPE_OMSG CC_SETUP_REQ REF 00000014 CH 2 20 TOD 1120
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5486201 NUM PLAN: E164
CALLED #:5464210 NUM PLAN: E164

DCH 12 UIPE_OMSG CC_SETUP_REQ REF 00000012 CH 2 18 TOD 1124
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5175486201 NUM PLAN: E164
CALLED #:17348783123 NUM PLAN: E164

DCH 12 UIPE_OMSG CC_SETUP_REQ REF 00000011 CH 2 17 TOD 1132
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5486201 NUM PLAN: E164
CALLED #:8616061 NUM PLAN: E164

DCH 12 UIPE_OMSG CC_DISC_REQ REF 00000017 CH 2 23 TOD 1134
CAUSE: #16 - NORMAL CALL CLEARING

DCH 12 UIPE_OMSG CC_SETUP_REQ REF 00000017 CH 2 23 TOD 1140
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:5175486201 NUM PLAN: E164
CALLED #:15174042963 NUM PLAN: E164

Fletch

It means the originating station is not an ISDN device, like a video bridge etc. Your originating set is a digital phone. If it was a BRI (ISDN Phone) then it owuld be.

It's something most people think is an error, but is really not.

__________________
Fletch
Nortel Emergency Services PLM

For more on Nortel E911 Solutions on the web:
http://nortel.com/e911

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcasts

Rachelle

Is this on ALL calls or just calls to a particular area? To test this, call someone in your local exchange and see what shows on their caller ID box. If it shows the number then your problem is between two LECs and will be difficult to get resolved. If it does not show on the caller ID of your local person then the problem is within SBC. Your Dchannel messages show all of the digits being passed out of your PBX so your equipment appears to be doing it's job.

Good Luck!


rlc

gogoGophers

Local and LD get the same, "Unknown name". Looks like a classic game of
"the trouble is leaving here fine". Thanks to all. It's even more fun, because they have an alternative local carrier that I call, then they call SBC. We're talkin' fun city.

gogoGophers

At the risk of being a pain, I have more questions -

My friends at the LEC, continue to tell me that the problem is all me.
My contact sent me this SBC blather -

The PBX can control the blocking and/or delivery of CPN (Caller ID) using the privacy indicator in the "D" channel message on the PRI. SBC honors the privacy indicator on our network with a few exceptions such as 911 calls.

Does this apply to the Option 11 ? If so where do I check it ?
Alternatively, do the previous D-channel postings indicate that this is simply not the problem and I should tell them adjust thier attitudes ?

slagburn

Might help if you post up your DCH and RDB programming so we can take a gander at it... could be one little thing.