UC520 2xBRI basic setup instruction

[roydennemans]

Hello,

I'm new to Cisco voice.

I have a UC520 2xBRI (seperate lines with 2 blocks of 4 numbers).

Can someone give me the basic steps

to get BRI working?

I only need a simple setup.

Number forward to hunt group for general use (office number) and direct forwaring to specific telephones.

I see the line light up on call but I do not understand how to handle incoming calls.

Kind regards

Vincent

[paolo bevilacqua]

Hi, if you want them to see your extension calling number, you can set again a translation rule. Looking at the configuration, have you understood now how it works ? Also, if you have two bris active, you need trunk group. The config assistant isn't able to do these things.

[roydennemans]

Hi,

I created the trunk group using command line.

This also works.

But I still have troubles with the dial plan. (In the CCA is only North American plan available).

I changed some values and can now call

regional numbers as follows:

Our number starts with 024 and then 7 digits

I can call all other numbers that start with 024 in our region. I can not call e.g. Amsterdam starting with 020

Also I can not call mobile numbers which start with 06 and then 8 digits

Can you explain me (perhaps small example) how to change this correctly in command line?

Your help is much appreciated.

Kind regards.

[paolo bevilacqua · Accepted solution]

Sure. Let's assume you do not use any digit as access for external calls (thing that sually users like very much ebcuae it's like calling from home:

dial-peer voice 58 pots

desc international

destination-pattern 001.....T

prefix 001

trunkgroup bri

dial-peer voice xxx pots

desc cellphones

destination-pattern 06........

trunkgroup bri

dial-peer voice xxx pots

desc national

destination-pattern 0[1-9]........

prefix 0

trunkgroup bri

dial-peer voice xxx pots

desc emergency

destinaion-pattern 112

prefix 112

trunkgroup bri

Then you can remove the ununsed DPs.

[roydennemans]

Thanks, this works!!

One last question, incoming callerID is displayed without the 0 making it not possible to return missed calls (wrong number obviously) How do I correct this?

Kind regards,

[paolo bevilacqua · Accepted solution]

Add a translation-profile to the trunk group, for incoming, and recall teh following rule against calling number:

voice translation-rule 300

rule 1 // /0/ type national national

rule 2 // /00/ type international international

[roydennemans]

Hello,

How do I select the default outbound ISDN number. isdn calling-number does not work.

The customer wants to use the 3th number of the block of 4 numbers. The line defaults to the first number on outbound calling.

Thanks,

[paolo bevilacqua]

You can use either a translation rule at trunk-group level, or under each interface bri

isdn calling-number XXX

Note possibly you have to specify it without the 0.

In any case check what you're sending with "debug isdn q931" and "term mon".

[roydennemans]

Hello, I understand your config but somehow I can not get it working, I did this

voice translation-rule 4

rule 1 // /0/ type national national

rule 2 // /00/ type international national

!

voice translation-profile Add_Zero

translate called 4

!

!

dial-peer voice 50 pots

trunkgroup ISDN-LINES

description ** incoming dial peer **

translation-profile incoming Add_Zero

destination-pattern 0[1-9]........

incoming called-number .%

direct-inward-dial

prefix 0

!

dial-peer voice 51 pots

trunkgroup ISDN-LINES

description ** incoming dial peer **

translation-profile incoming Add_Zero

destination-pattern 06........

incoming called-number .%

direct-inward-dial

prefix 0

!

This does not add zero's

Kind regards.

[roydennemans]

Apparently I did not understand it,

I configured the profile on the ISDN-Trunk and now it's working, so please discard the config above.

Thank you very much for the excellent instructions!

[roydennemans]

My vlans were damaged in some way?

I have added a temp vlan using command line

which gives me access again to the unit.

I will try to update to the latest version (I see 15 feb 08 is the latest) first.