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!

Send all 4000's series numbers down route 6 1

Status
Not open for further replies.

RyanEOD

Programmer
Jan 11, 2008
675
US
All,

I am trying to dig up how to do this and I can't find exactly what I am looking for. I want to send all 4000's series numbers down my route 6, what is the best/easiest way for this? Thanks!
 
ld 87 steering code
create a dsc of 4 and send it to the appropiate rli for rte 6.

Mato' Was'aka
 
Big,

OK, here is what I have, doing the 47XX range down RTE 6:

RLI 3
ENTR 0
LTER NO
ROUT 6
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
SCNV NO
CNV NO
EXP NO
FRL 0
DMI 0
ISDM 0
FCI 0
FSNI 0
DORG NO
SBOC NRR
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0

Here is my DSC:

REQ prt
CUST 0
FEAT cdp
TYPE dsc
DSC 47
DSC 47
FLEN 4
DSP LSC
RLI 3
NPA
NXX

Here is what happens when I dial:

MEM AVAIL: (U/P): 99098796 USED U P: 5076823 76794 TOT: 104252413
DISK SPACE NEEDED: 105 KBYTES
REQ
DCH 6 OMSG SETUP REF 00000186 CH 96 0 2 0 TOD 17:16:17
FEAT :CRID
FEAT :CDS
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:6785 NUM PLAN: PRIVATE/ABBREVIATED (CDP)
CALLED #:4785 NUM PLAN: PRIVATE/ABBREVIATED (CDP)

DCH 6 IMSG CALLPROC REF 00000186 CH 96 0 2 0 TOD 17:16:17

DCH 6 IMSG DISC REF 00000186 CH 96 0 2 0 TOD 17:16:17
CAUSE :NTWK TEMP FAIL

DCH 6 OMSG RELEASE REF 00000186 CH 96 0 2 0 TOD 17:16:17

DCH 6 IMSG REL COMP REF 00000186 CH 96 0 2 0 TOD 17:16:17


Just getting a fast busy . . . Thoughts?
 
It is a Asterisk over a SIP trunk. 4785 is on a SIP phone at my desk. I am able to dial from the Asterisk to the CS1000, trying to go the other way now.
 
I didn't have my asterisk set up in my NRS, I just did that but my question is how do I make the Standby DB the active one?
 
Humm, I have figured out where to Cutover and Commit it, but something I am doing there is wrong. Still getting:


FEAT :CRID
FEAT :CDS
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:6785 NUM PLAN: PRIVATE/ABBREVIATED (CDP)
CALLED #:4785 NUM PLAN: PRIVATE/ABBREVIATED (CDP)

DCH 6 IMSG CALLPROC REF 00000186 CH 96 0 2 0 TOD 17:59:32

DCH 6 IMSG DISC REF 00000186 CH 96 0 2 0 TOD 17:59:32
CAUSE :NTWK TEMP FAIL

DCH 6 OMSG RELEASE REF 00000186 CH 96 0 2 0 TOD 17:59:32

DCH 6 IMSG REL COMP REF 00000186 CH 96 0 2 0 TOD 17:59:32
 
ryan it's quite simple switch the standby db to the active db.. in nrs utilities in db utilities that's a voice "Cut Over and commit" run this and should be fine..
 
Eddie,

Thank you for that, I am still getting that same error though after cutting over and commiting the database. Gerrrrr I don't think it is trying to reach out to the Asterisk because on wireshark I don't see it going out to the .75 address which is the Asterisk. Any ideas?
 
Try using TSC - Trunk Steering Code 'CDP'
Let us know the outcome

Cheers!!
 
SL1M1,

Would that go in here??

Here is my DSC:

REQ prt
CUST 0
FEAT cdp
TYPE dsc
DSC 47
DSC 47
FLEN 4
DSP LSC
RLI 3
NPA
NXX


Sorry it took a while to get back to you, I was on Vacation! :)
 
Yep you got it try TSC (Trunk)instead of DSC (Distant Steering Code)

Cheers!!
 
Ok, switched it to a TSC, and I know it is trying to send it out that trunk because when I dial a number I see:

DCH 6 OMSG SETUP REF 00000186 CH 96 0 2 0 TOD 15:43:09
FEAT :CRID
FEAT :CDS
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:6792 NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN)
CALLED #:4790 NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN)

DCH 6 IMSG CALLPROC REF 00000186 CH 96 0 2 0 TOD 15:43:09

DCH 6 IMSG DISC REF 00000186 CH 96 0 2 0 TOD 15:43:09
CAUSE :NTWK TEMP FAIL

DCH 6 OMSG RELEASE REF 00000186 CH 96 0 2 0 TOD 15:43:09

DCH 6 IMSG REL COMP REF 00000186 CH 96 0 2 0 TOD 15:43:09

So I know it is trying to out that trunk but not reaching out and "touching" anything. Now I can call in the other direction so I know that works. I know I am missing something small probably, next steps?
 
Is there a D-channel monitor on the Asterisk, to see if it's even getting to the Asterisk?

Do you have the 47xx routing entry built in NRS against the Asterisk endpoint?

Can you give us your NRS config for the Asterisk?

-Matthew

Matthew - Technical Support Engineer
 
Matt, for sure here is how I have it set:

Gateway Endpoints:

Name: Asterisk
Description: SIP Trunk
Endpoint Authentication enabled: Not Configured
E.164 country code:1
E.164 Area Code:704 (Yes, Charlotte :))
Static endpoint address type: IPv 4
Static endpoint address: 192.168.1.80
H.323 Support: H.323 not supported
SIP support: Static SIP endpoint
SIP transport: UDP
SIP port: 5060

Then in Routing Entries:

Endpoint: Asterisk

#1
DN Prefix: 47
Private level 0 regional(CDP steering Code)
Route Cost: 1
SIP URI Phone Context: udp.cdp


No I don't have a D-Channel monitor on the Asterisk that I know of . . . Just let me know what else you need!


 
Are all other SIP calls OK; IE, can you call from the Asterisk to the CS1K? Point being, the DSP's can cause this if no DSP is available or something wrong w/ them.

Do you know how to use the NRS trace logs via signaling server CLI? Is your NRS co-res on a signaling server or standalone?

I've never configured an NRS for Asterisk so not sure what type of call the Asterisk is expecting; it could have something to do with that. It might want private.special, etc... I'll see if I can find any white papers.

Matthew - Technical Support Engineer
 
Thanks man, I appreciate it. Asterisk to CS1k does work. So I know I can go that way . . here is a switch log of that succeeding and me answering:

DCH 6 IMSG SETUP REF 00008186 CH 96 0 2 0 TOD 16:21:03
CALLING #:96 NUM PLAN: NUM UNKNOWN/UNKNOWN (UNKNOWN)
CALLED #:6785 NUM PLAN: NUM UNKNOWN/UNKNOWN (UNKNOWN)

DCH 6 OMSG CALLPROC REF 00008186 CH 96 0 2 0 TOD 16:21:03

DCH 6 OMSG ALERT REF 00008186 CH 96 0 2 0 TOD 16:21:03
PROGRESS: DEST ADDR IS NOT ISDN

DCH 6 OMSG CONNECT REF 00008186 CH 96 0 2 0 TOD 16:21:13

DCH 6 IMSG CONN ACK REF 00008186 CH 96 0 2 0 TOD 16:21:13

DCH 6 OMSG DISC REF 00008186 CH 96 0 2 0 TOD 16:21:13
CAUSE :NORMAL CALL CLEARING

DCH 6 IMSG RELEASE REF 00008186 CH 96 0 2 0 TOD 16:21:13
CAUSE :NORMAL CALL CLEARING

DCH 6 OMSG REL COMP REF 00008186 CH 96 0 2 0 TOD 16:21:13


I have never messed with NRS as this is my first attempt, and I am failing miserably, so I don't know how to use the trace logs. But, I tend to think I am a quick learner!

I have dug around and have seen tons of people ask how to do it, then never see anything posted on how to get it going. I know some have been successful, but they never posted configs, I think it is a closely guarded secret . . .

Thanks again!
 
I would *guess* w/o looking at the NRS trace logs or SIP trace logs that the Asterisk doesn't like the call type in the NRS.

Try it as each of the following:
Private Level 1
Private Level 0
Private Special

You may have to build a DMI to change the call type on your RLI to either SPN or UKWN; I'd start trying combinations. I haven't found anything specific yet about how the Asterisk expects the call.

Is there SIP logging of any sort on the Asterisk that you can turn on?

-Matthew

Matthew - Technical Support Engineer
 
Matthew,

I have gone through the Routing Entries in NRS and tried all the different types for dialing prefix 47, no dice on any of them.

And the next part I need to step through, you are saying a DMI (Assuming Digit Manipulator) to change my RLI to SPN or UKWN . . . hummm how?

The Asterisk guru is saying he isn't even sitting it hit his machine, makes me think it doesn't know to go to that IP addy.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top