Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Incoming DDI

Status
Not open for further replies.

amlancaster

Technical User
Jun 6, 2007
23
GB
Help!

We have used our 30 channel ISDN bearer for outgoing calls for the last year fine.

From today our supplier has set our DDI to come into the same bearer. The range is presented as 4 digits.

When you dial the new DDI range we currently get NU or Invalid Number. What settings do we need to set on the 3300 to allow incoming DDI calls?

Thanks
 
Is this a DASS2 circuit or and etsi/Q931 circuit?

depending on your extension range length but the least you need to do is assign a trunk service to the trunks and in the trunk service assignment form you need to set absorb digits field with a 0.
 
How many digits were you receiving before adding the DDI.

Do you have matching digits programmed in the 3300 for the 4 digits received.

The trunk service assignment for the ISDN Lines will have a value for absorb digits. what is it? (including zero)

*******************************************************
Hard work often pays off after time, but laziness always pays off now.
 
We have never had DDI coming in over the QSIG barring. The absorb digits is set to 0.

Our new DDI range is 725xxx. All of our internal numbers are 5xxx.
 
Sorry, I missed the outgoing only part.

Assuming that you are actually receiving 4 digits and the absorb digits are zero you should be good to go.

Hopefully you are using an NSU as your gateway and not embedded as troubleshooting is easier on the NSU.

Assuming NSU, Connect to the maint port with a VT-100 terminal application at 38.4kbs.

Type option + dispcall

Initiate test call, observe and post results.

*******************************************************
Hard work often pays off after time, but laziness always pays off now.
 
that was supposed to be "option +dispcall"

If you mistype press enter and start over.


*******************************************************
Hard work often pays off after time, but laziness always pays off now.
 
You can do the same tracing on the embedded cards, at least as of 3300ICP release 7.1, not sure how much earlier than that it was introduced. There's a maintenance command to turn on the tracing. "edt trace" I think, check the help file.
 
To Lundah, Yes but the embedded trace is very verbose and not user friendly.

Hopefully he has an NSU and we can avoid that pain

*******************************************************
Hard work often pays off after time, but laziness always pays off now.
 
Our maintainers have found out our DDI provider was not sending the 4 digits.
 
Occam's Razor, the simplest explaination is probably the correct one.

*******************************************************
Hard work often pays off after time, but laziness always pays off now.
 
I'll always check the number of digits received from telco in SMDR log before change any setings. We have 3 telco providers - none matched the number of digits they said, so sometimes I don't even ask them only if they ask me how many digits I want.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top