Solved: Grouping PRI Channels

rameezsardar · ‎01-21-2008

Friends,

I am working on voip setup where Ericsson PBXs are connected with cisco 3800

routers. You can see topology below:

Phones-------PBX-A----Router-A-------------------------Router-B------PBX-B--------Phones

PBX is connected with router through E1 Pri (qsiq) where as Router are

connected via E1 link.

Issue is: before voip setup PBXs are connected point to point and TDM

engineer divided channels in to two groups. One from channel 1-18 for

subscribers and other from 19-31 for Operators. So when subscriber come on

trunk, it was assigned channel from 1-18 and operators are assigned channel

from its range. Now i put routers between PBXs so when operator of PBX-A try

to dial number, operator is assigned channel from its range on PBX-A and

forward to Router-A. When that call reaches Router-B, it assign first

available channel on pri that is connected with PBX-B. But we want channels

are assigned by Router-B must be same that assigned by PBX-A.

Hope you will have understand my problem. And please tell me the

solution.......You immediate response will be appreciated.

Best Regards

Rameez

pcameron · ‎01-21-2008

Providing you use the gateway in H323 mode, you can use a new trunk group feature that allows you to specify individual timeslot members.

Here is an old config I got working a while back, it is relevant to your application and it should show you how to make your system work. Since you don't have a call manager, ignore the comments about route patterns. In your case, you would use a matching trunk group config on router B to direct calls to the outgoing trunk groups that correspond to the timeslots.

For ISDN -

controller E1 1/0

pri-group timeslots 1-31

trunk-group Channel_1 timeslots 1

trunk-group Channel_2 timeslots 2

trunk-group Channel_3 timeslots 3

trunk-group Channel_4 timeslots 4

trunk-group Channel_5 timeslots 5

.... (leave out D channel timeslot 16)

trunk-group Channel_31 timeslots 31

!

dial-peer voice 1 pots

description - enable DID on group 1

incoming called-number .

direct-inward-dial

trunkgroup Channel_1

!

dial-peer voice 2 pots

description - enable DID on group 2

incoming called-number .

direct-inward-dial

trunkgroup Channel_2

!

dial-peer voice 3 pots

description - enable DID on group 3

incoming called-number .

direct-inward-dial

trunkgroup Channel_3

!

dial-peer voice 4 pots

description - enable DID on group 4

incoming called-number .

direct-inward-dial

trunkgroup Channel_4

!

dial-peer voice 5 pots

description - enable DID on group 5

incoming called-number .

direct-inward-dial

trunkgroup Channel_5

!

...

!

dial-peer voice 31 pots

description - enable DID on group 31

incoming called-number .

direct-inward-dial

trunkgroup Channel_31

!

dial-peer voice 771 pots

trunkgroup Channel_1

description - Channel_1 : access code 771

destination-pattern 771

!

dial-peer voice 772 pots

trunkgroup Channel_2

description - Channel 2 : access code 772

destination-pattern 772

!

dial-peer voice 773 pots

trunkgroup Channel_3

description - Channel 3 : access code 773

destination-pattern 773

!

dial-peer voice 774 pots

trunkgroup Channel_4

description - Channel 4 : access code 774

destination-pattern 774

!

dial-peer voice 775 pots

trunkgroup Channel_5

description - Channel 5 : access code 775

destination-pattern 775

...

!

dial-peer voice 7731 pots

trunkgroup Channel_31

description - Channel 31 : access code 7731

destination-pattern 7731

!

On the CCM, you need to run H323 as the gateway signaling protocol

To make outwards calls, users would dial the particular number that corresponds to a channel on the PRI. The CCM route pattern would have a specific match on this string. For example, a user wants to make a call out on timeslot 1. They would dial the unique access code (771) and the rest of the number/s , which corresponds to a route pattern on the CCM. This access code would not be stripped from the dialed number sent to the H323 gateway. Since we have a specific dial peer that matchs on '771, the call is sent out on trunk group 'Channel_ 1' , which corresponds to timeslot 1. The 771 is stripped off by the outgoing POTS dial peer and the rest of the number is sent out the PRI.

For channels 2 to 31, users would dial the relevant number, and this would match on the other unique CM route pattern strings. The call would be treated similar to the above.

View solution in original post

paolo bevilacqua · ‎02-01-2008

You can use either a COR config, or "prefix digits".

In both cases you configure an incoming DP that with "answer-address" that matches number from operator, or other numbers.

With COR, you set corlist so that the ougoing DP is chosen based on COR config.

With "prefix digits", you use translation-profile so that some digits are added then removed, and the call is routed by these digits. See:

http://cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801c0a88.shtml

View solution in original post

paolo bevilacqua · ‎01-21-2008

Hi,

In QSIG/PRI on cisco IOS, you cannot divide a same circuit in groups. It is not like using E1-R2 that allows such a logical division. So, in short, you cannot preserve channel order between PBX calls , not withstanding that, everything should work anyway, as you can for example limit the number of calls at DP level.

Now, if you want to avoid discussing with the PBX technicians and customer, configure T-CCS that will transport D-chan and B-chans unaltered. There are configuration examples on CCO on how to do this.

The disadvantage, is that you will need to configure VAD to prevent the B-chans to be open all the time!

Hope this helps, please rate post if it does!

pcameron · ‎01-21-2008

Providing you use the gateway in H323 mode, you can use a new trunk group feature that allows you to specify individual timeslot members.

Here is an old config I got working a while back, it is relevant to your application and it should show you how to make your system work. Since you don't have a call manager, ignore the comments about route patterns. In your case, you would use a matching trunk group config on router B to direct calls to the outgoing trunk groups that correspond to the timeslots.

For ISDN -

controller E1 1/0

pri-group timeslots 1-31

trunk-group Channel_1 timeslots 1

trunk-group Channel_2 timeslots 2

trunk-group Channel_3 timeslots 3

trunk-group Channel_4 timeslots 4

trunk-group Channel_5 timeslots 5

.... (leave out D channel timeslot 16)

trunk-group Channel_31 timeslots 31

!

dial-peer voice 1 pots

description - enable DID on group 1

incoming called-number .

direct-inward-dial

trunkgroup Channel_1

!

dial-peer voice 2 pots

description - enable DID on group 2

incoming called-number .

direct-inward-dial

trunkgroup Channel_2

!

dial-peer voice 3 pots

description - enable DID on group 3

incoming called-number .

direct-inward-dial

trunkgroup Channel_3

!

dial-peer voice 4 pots

description - enable DID on group 4

incoming called-number .

direct-inward-dial

trunkgroup Channel_4

!

dial-peer voice 5 pots

description - enable DID on group 5

incoming called-number .

direct-inward-dial

trunkgroup Channel_5

!

...

!

dial-peer voice 31 pots

description - enable DID on group 31

incoming called-number .

direct-inward-dial

trunkgroup Channel_31

!

dial-peer voice 771 pots

trunkgroup Channel_1

description - Channel_1 : access code 771

destination-pattern 771

!

dial-peer voice 772 pots

trunkgroup Channel_2

description - Channel 2 : access code 772

destination-pattern 772

!

dial-peer voice 773 pots

trunkgroup Channel_3

description - Channel 3 : access code 773

destination-pattern 773

!

dial-peer voice 774 pots

trunkgroup Channel_4

description - Channel 4 : access code 774

destination-pattern 774

!

dial-peer voice 775 pots

trunkgroup Channel_5

description - Channel 5 : access code 775

destination-pattern 775

...

!

dial-peer voice 7731 pots

trunkgroup Channel_31

description - Channel 31 : access code 7731

destination-pattern 7731

!

On the CCM, you need to run H323 as the gateway signaling protocol

To make outwards calls, users would dial the particular number that corresponds to a channel on the PRI. The CCM route pattern would have a specific match on this string. For example, a user wants to make a call out on timeslot 1. They would dial the unique access code (771) and the rest of the number/s , which corresponds to a route pattern on the CCM. This access code would not be stripped from the dialed number sent to the H323 gateway. Since we have a specific dial peer that matchs on '771, the call is sent out on trunk group 'Channel_ 1' , which corresponds to timeslot 1. The 771 is stripped off by the outgoing POTS dial peer and the rest of the number is sent out the PRI.

For channels 2 to 31, users would dial the relevant number, and this would match on the other unique CM route pattern strings. The call would be treated similar to the above.

paolo bevilacqua · ‎01-21-2008

Paul,

Which platform is that?

On a 3821 with 12.4(11)XW5 I don't have trunk-grup under controller E1:

BA-CCME(config)#controller E1 0/0/1

BA-CCME(config-controller)#?

Controller configuration commands:

cas-custom cas group customization configuration

channel-group Specify the timeslots to channel-group mapping for an

interface

clock Specify the clock source for a DS1 link

default Set a command to its defaults

description Controller specific description

detect Enable detection of loopback request

ds0 ds0 commands

ds0-group Configure group of timeslots to a particular signaling type

exit Exit from controller configuration mode

framing Specify the type of Framing on a E1 link

guard-timer Guard timer (0-20) for xcsp calls - timer duration and

accept/reject on expiry

help Description of the interactive help system

line-termination Specify the line termination for E1

linecode Specify the line encoding method for a E1 link

loopback Put the entire E1 line into loopback

mode Configure the controller mode

no Negate a command or set its defaults

pri-group Configure the specified timeslots for PRI

shutdown Shut down a E1 link (send Blue Alarm)

snmp Modify SNMP controller parameters

tdm-group Configure DS0 group for TDM

pcameron · ‎01-21-2008

Just tested this on a 2851 running 12.4.11T, IP voice feature set.

You need to configure the pri-group first, otherwise the CLI parser won't allow the trunk-group command -

!

controller E1 0/0/0

pri-group timeslots 1-10

!

CME-Switch#conf t

Enter configuration commands, one per line. End with CNTL/Z.

CME-Switch(config)#controller e1 0/0/0

CME-Switch(config-controller)#trunk-group ?

WORD Trunk group label

paolo bevilacqua · ‎01-22-2008

Hi, I do have pri-group. Do you have VWIC or VWIC2 ?

CT-CCME#sh run | b controller

controller E1 0/2/0

pri-group timeslots 1-20

CT-CCME#sh ver

Cisco IOS Software, 2800 Software (C2800NM-IPVOICE-M), Version 12.4(11)XJ4, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Compiled Fri 13-Jul-07 22:43 by prod_rel_team

ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1)

CT-CCME uptime is 4 days, 3 hours, 51 minutes

System returned to ROM by power-on

System restarted at 08:42:20 CET Fri Jan 18 2008

System image file is "flash:c2800nm-ipvoice-mz.124-11.XJ4.bin"

Cisco 2851 (revision 53.51) with 249856K/12288K bytes of memory.

Processor board ID FCZ105072QA

2 Gigabit Ethernet interfaces

20 Serial interfaces

4 ISDN Basic Rate interfaces

1 terminal line

1 Channelized E1/PRI port

4 Voice FXO interfaces

11 Voice FXS interfaces

1 cisco service engine(s)

DRAM configuration is 64 bits wide with parity enabled.

239K bytes of non-volatile configuration memory.

62720K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

CT-CCME#sh diag

PVDM Slot 0:

48-channel (G.711) Voice/Fax PVDMII DSP SIMM PVDM daughter card

Hardware Revision : 4.0

Part Number : 73-8540-05

Board Revision : A0

Deviation Number : 0

Fab Version : 04

PCB Serial Number : FOC10435CFM

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Processor type : 00

Product (FRU) Number : PVDM2-48

Version Identifier : V01

EEPROM format version 4

EEPROM contents (hex):

0x00: 04 FF 40 03 ED 41 04 00 82 49 21 5C 05 42 41 30

0x10: 88 00 00 00 00 02 04 C1 8B 46 4F 43 31 30 34 33

0x20: 35 43 46 4D 03 00 81 00 00 00 00 04 00 09 00 CB

0x30: 88 50 56 44 4D 32 2D 34 38 89 56 30 31 20 D9 02

0x40: 40 C1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

WIC Slot 2:

E1 (1 port) Multi-Flex Trunk WAN daughter card

Hardware revision 1.0 Board revision B0

Serial number 35293166 Part number 800-04475-04

FRU Part Number VWIC-1MFT-E1=

Test history 0x0 RMA number 00-00-00

Connector type PCI

EEPROM format version 1

EEPROM contents (hex):

0x20: 01 21 01 00 02 1A 87 EE 50 11 7B 04 00 00 00 00

0x30: 58 00 00 00 06 10 05 00 FF FF FF FF FF FF FF FF

CT-CCME#conf t

Enter configuration commands, one per line. End with CNTL/Z.

CT-CCME(config)#controller E1 0/2/0

CT-CCME(config-controller)#trunk-group ?

% Unrecognized command

pcameron · ‎01-22-2008

not sure what is going on here, here is the router I am testing with -

CME-Switch(config-controller)#do sh ver

Cisco IOS Software, 2800 Software (C2800NM-IPVOICE-M), Version 12.4(11)T, RELEAS

E SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Compiled Sat 18-Nov-06 17:16 by prod_rel_team

ROM: System Bootstrap, Version 12.4(13r)T, RELEASE SOFTWARE (fc1)

CME-Switch uptime is 17 weeks, 4 days, 3 hours, 45 minutes

System returned to ROM by power-on

System image file is "flash:c2800nm-ipvoice-mz.124-11.T.bin"

Cisco 2851 (revision 53.51) with 249856K/12288K bytes of memory.

Processor board ID FHK1120F300

2 Gigabit Ethernet interfaces

88 Serial interfaces

33 terminal lines

8 Channelized E1/PRI ports

6 Voice FXO interfaces

16 Voice FXS interfaces

1 cisco service engine(s)

DRAM configuration is 64 bits wide with parity enabled.

239K bytes of non-volatile configuration memory.

62720K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

CME-Switch(config-controller)#

CME-Switch(config-controller)#?

Controller configuration commands:

cas-custom cas group customization configuration

channel-group Specify the timeslots to channel-group mapping for an

interface

clock Specify the clock source for a DS1 link

default Set a command to its defaults

description Controller specific description

detect Enable detection of loopback request

ds0 ds0 commands

ds0-group Configure group of timeslots to a particular signaling type

exit Exit from controller configuration mode

framing Specify the type of Framing on a E1 link

guard-timer Guard timer (0-20) for xcsp calls - timer duration and

accept/reject on expiry

help Description of the interactive help system

line-termination Specify the line termination for E1

linecode Specify the line encoding method for a E1 link

loopback Put the entire E1 line into loopback

mode Configure the controller mode

no Negate a command or set its defaults

pri-group Configure the specified timeslots for PRI

shutdown Shut down a E1 link (send Blue Alarm)

tdm-group Configure DS0 group for TDM

trunk-group Configure interface to be in a trunk group

CME-Switch(config-controller)#

CME-Switch(config-controller)#tr

CME-Switch(config-controller)#trunk-group ?

WORD Trunk group label

CME-Switch(config-controller)#trunk-group test ?

timeslots Add specific timeslots into trunk group from signaling interface

CME-Switch(config-controller)#trunk-group test timeslots ?

<1-16> List of timeslots to configure under trunk group

CME-Switch(config-controller)#trunk-group test timeslots 1-10 ?

preference configure the preference for DS0 trunk group

CME-Switch(config-controller)#trunk-group test timeslots 1-10

CME-Switch(config-controller)#

E1 interface is a VWIC-2MFT-E1

WIC Slot 0:

E1 (2 port) Multi-Flex Trunk WAN daughter card

Hardware revision 1.0 Board revision C0

Serial number 35642695 Part number 800-04479-04

FRU Part Number VWIC-2MFT-E1=

Test history 0x0 RMA number 00-00-00

Connector type PCI

EEPROM format version 1

EEPROM contents (hex):

0x20: 01 23 01 00 02 1F DD 47 50 11 7F 04 00 00 00 00

0x30: 60 00 00 00 07 04 09 00 FF FF FF FF FF FF FF FF

can you try with a two port e1 card ?

paolo bevilacqua · ‎01-31-2008

I got the time to try that again. A 3845, with latest 12.4 mainline, then 12.4(11)XJ4, tried VWIC-MFT 1 and 2 ports.

All gave no problem. I have no idea what is preventing me from configuring on the other box.

Thanks!

rameezsardar · ‎01-31-2008

Dear p.bevilacqua,

Ahan. that may be some configuration issue. I am also using this trunk-group on 3800 router. I knew this command before but i just knew that it used for bundling interfaces but didn't know to use it in this way.

Regards

rameezsardar · ‎01-23-2008

Dears,

I have vwic-2mft-2t1/e1, vwic2-2mft-2t1/e1 and nm-hdv2 but i could not check configuration......

get you later

rameezsardar · ‎01-24-2008

Dear,

Bundle of thanks your suggested method is working fine. I configure trunk-groups and assigned channel to them. Everything is ok.

Best regards

rameezsardar · ‎01-31-2008

Brothers,

I need your assistance again. I have created two trunk group one "sub" for subscriber and other "opr" for operator. Now issue arise that i have to forward calls so that if call come from sub trunkgroup on router1, on router2 it must forward on sub trunkgroup and same for opr trunkgroup. You can see topology below:

PhoneA----- PBX 1------------Router1-----------Router2---------PBX2---------PhoneB

Please tell me the way how can i do that.

Waiting for positive immediate response..

Best Regards

rameezsardar · ‎02-01-2008

Friends,

Still waiting for answer of question above...

Regards

paolo bevilacqua · ‎02-01-2008

You can use either a COR config, or "prefix digits".

In both cases you configure an incoming DP that with "answer-address" that matches number from operator, or other numbers.

With COR, you set corlist so that the ougoing DP is chosen based on COR config.

With "prefix digits", you use translation-profile so that some digits are added then removed, and the call is routed by these digits. See:

http://cisco.com/en/US/tech/tk652/tk90/technologies_configuration_example09186a00801c0a88.shtml

rameezsardar · ‎02-06-2008

Dear P.Bevilacqua,

Thanks for your responding. Translation-profile solve my issue. Everything is working fine. Can we also use COR for this purpose? To the best of my knowledge, COR can only be used for allow/restrict calls.

Best Regards