BCM50 VoIP trunk Question 1

[NARSBARS]

Just setting up a trial from an 81C, Succession 3.0 to a BCM50.
I made the entries into the switch and I can call from My 81 to another 61 and to the BCM50 using 3 digit loc codes and AC2 set to 8 and pointed at the VoIP route.

I cannot get from the 50 to the PBX and it feels like user error, (mine). Any help greatly appreciated. As I am not used to the VoIP side yet please use small words and write in crayon.

NARSBARS

 

[RYLSFAN]

have you opened up your monitor to see if the call is leaving he 50?

set a destination code to use a route that ha BlocA assigned to it and that shoud allow you to access your VoIP lines. Add lines 1-4 to BlocA.

If that doesn't help i might not understand the question....which is just more user error.

Thats not my fastball, thats my hurry up and get by you pitch... Satchel Paige

 

[NARSBARS]

I will check your advice, line by line and report back.
I set the dest code etc. But when I call for tech supp I shut up, follow the advice and then come back if it doesn't work.
If I already knew the answer I wouldn't need to call for help.
Thanks.

NARSBARS

 

[NARSBARS]

I have not used the monitor. "Picture me embarassed". Not sure how. I have used the BCM monitor on the 400s and 200s.
Is it the same?

I set a Dest code 8, absorb all to use Route 10. Bloc A DN type private.

Bloc A has lines one and two (VoIP trunks) assigned.
Test set has access to Bloc A.
I have only two VoIP trunks.








NARSBARS

 

[biv343]

BCM Monitor is the same on the 50, except your username is different (obviously).

Is there a sig server in the mix, or just ITG Trunk (with IPT 3.X software)?

Am I correctly guessing that you're using ESN (UDP/LOC) dialing between the 81 and 61?

 

[NARSBARS]

Sig Server, yes. UDP/LOC, yes.
I will test the BCM Monitor today.
Thanks for the help.

NARSBARS

 

[biv343]

I'd bet if you look at the D-channel messaging when a failed call comes across that you'll see it as rejected due to incorrect type.

Just for grins, try changing your Bloca route to public from private. The BCM doesn't play very well with UDP/LOC/ESN since there isn't really a NCOS value sent across.

 

[NARSBARS]

Changed from Public to private, No results.

Checked with BCM Monitor and the correct digits (seven) are being sent.

DID a TRAC on the outgoing to the 50 (successful) and to the 61 (failed)and everthing appears to match up as far as sent digits etc.

Now I can only dial the 50 Loc plus XXXX and I can no longer dial the 61 on the Network. I am waiting for one of our guys to get there and try to dial me from there.

Succession 3.0 with all patches. I just love working on old software.
Thanks again.

NARSBARS

 

[biv343]

One other thing just came to mind...

I'm going to guess that on your NRS (or Gatekeeper, since you're on 3.0) that the digits built against the main office are defined as a UDP (or level 1). Try adding the same digits as CDP (or level 0). I seem to remember a problem with a customer where the BCM sent the calls out marked as CDP, even though we were trying to do UDP. The NRS was kicking it back since there wasn't a matching CDP entry against the endpoint.

Once you do that, try a call. If it still fails, try changing your private network dialing plan to CDP on the 50 and give it a shot.

Some of my above terms about the gatekeeper may be off a bit - I'm on 4.5 here and don't have any 3.0 systems that I can get to to see the NRS.

 

[NARSBARS]

biv343,

I will check this out tomorrow and report back.

NARSBARS

 

[NARSBARS]

I have traced a successful call and a failed call.
Note the "UNASSIGNED NUMBER" listed as failure cause.
All of the entries appear the same in the PBX but this tells me I am missing something. I will move this to the PBX forum if you guys think I should.
Thank you

DCH 10 OMSG SETUP REF 000001A0 CH 96 0 1 31 TOD 8:18:00
FEAT :NCID
PROGRESS: ORIG ADDR IS NOT ISDN
CALLING #:4158 NUM PLAN: PRIVATE/UNKNOWN (UNKNOWN)
CALLED #:8815998 NUM PLAN: PRIVATE/RESERVED (LOC)

DCH 10 IMSG CALLPROC REF 000001A0 CH 96 0 1 31 TOD 8:18:00

DCH 10 IMSG DISC REF 000001A0 CH 96 0 1 31 TOD 8:18:00
CAUSE :UNASSIGNED NUMBER
DIAG: 003

DCH 10 OMSG RELEASE REF 000001A0 CH 96 0 1 31 TOD 8:18:00

DCH 10 IMSG REL COMP REF 000001A0 CH 96 0 1 31 TOD 8:1

NARSBARS

 

[biv343]

Are the extensions at the PBX site 4 digit (such as 5998)?

If so, you could put an IDC on that route to strip off the first three digits. If there are other PBX's out there, that might cause problems, but it worked for me - had an 11C at the middle with about 20 BCM's connected back to it. They do UDP-LOC as well - dial 5+ 2 digit LOC+extension. Their LOC was 00 - put an IDC to strip off the 00 and send the 4 digits on, and it worked like a charm.

 

[NARSBARS]

The extensions at the Main Sig Server and at the called location are both 4 digit.

I like the IDC idea. I have another 7 PBXs that will eventually be part of this if I ever get it right.
I thought that the loc code entry in the server, in this case 881,passed on the the digits after removing the loc code.



NARSBARS

 

[biv343]

It will if a PBX is at the far end, but the BCM is a little too dumb for the PBX. If the BCM truly spoke ESN/NARS/ UDP-LOC like the PBX does, it wouldn't be a problem.

 

[NARSBARS]

I can dial AC2 from the 81 +loc code + extension and get to the BCM.

I can also dial the BCM Loc code and random digits and still get to the BCM!

The Opt 61 is giving me the problems, but maybe a clue is that the VoIP trunks are not using a route in the 0 to 7 range and I need to reconfigure that switch.

The server appears to take the BCM Loc code, plus any four digits and pass them to the BCM. But when digits are received by the 61 the numbers are not seen as valid.
I will enable D channel messaging at the 61 and see if I can get an answer that way.

I will be trying the IDC idea just to keep from screaming.

NARSBARS

 

[NARSBARS]

Biv, the IDC on the PBX trunks works.Posted you a star.

The solution to being able to call the 50 but not place calls from the 50 was to set the payload size in the 50 to
20 for 711 and 729 to match the Gatekeeper.

Now to go on and learn all the ins and outs of CLID on VoIP.

Thank you to everyone, all the ideas helped.



NARSBARS