How to agregate some BRI up to 3 on ASS400

Unanswered Question
Jun 16th, 2008
User Badges:

We are working with a Trunking Gateway AS5400HPX in 12.4(13d) ios versions

The HW is

-AS5400HPX E1 8 PRI DFC

-AS5400HPX NP50 / NP108 DFC


The configuration is done according isdn in the following way



isdn switch-type primary-net5


!iua

AS as0 xx.xx.1.90 9900

AS as0 sctp-t1init 1000

AS as0 sctp-startup-rtx 5

ASP asp0 AS as0 xx.xx.1.37 9900

ASP asp0 sctp-keepalives xx.xx.1.37 4000

ASP asp0 sctp-t3-timeout xx.xx.1.37 2000

!

!

controller E1 7/0

framing NO-CRC4

ds0-group 1 timeslots 1-31 type none service mgcp

extsig mgcp

guard-timer 10 on-expiry reject

description TRUNKING OPM

!

controller E1 7/1

framing NO-CRC4

ds0-group 1 timeslots 1-31 type none service mgcp

extsig mgcp

guard-timer 10 on-expiry reject

description TRUNKING OPM

!

controller E1 7/2

framing NO-CRC4

ds0-group 1 timeslots 1-31 type none service mgcp

extsig mgcp

guard-timer 10 on-expiry reject

description TRUNKING OPM

!

controller E1 7/3

framing NO-CRC4

ds0-group 1 timeslots 1-31 type none service mgcp

extsig mgcp

guard-timer 10 on-expiry reject

description TRUNKING OPM

!

controller E1 7/4

framing NO-CRC4

pri-group timeslots 1-31 service mgcp

description T2IULAN1 - ISDN NETWORK-SIDE

!

controller E1 7/5

framing NO-CRC4

pri-group timeslots 1-31 service mgcp

description T2IULAN2 - ISDN USER-SIDE

!

controller E1 7/6

framing NO-CRC4

pri-group timeslots 1-31 service mgcp

description LAIPFTE2 (E10B3) - ISDN USER-SIDE

!

controller E1 7/7

framing NO-CRC4

ds0-group 1 timeslots 1-31 type none service mgcp

extsig mgcp

guard-timer 10 on-expiry reject

description LAIPFTE4 (E10B3) - ISUP


…./….

!

interface Serial7/4:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn protocol-emulate network

isdn bind-l3 iua-backhaul as0

no cdp enable

!

interface Serial7/5:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn bind-l3 iua-backhaul as0

no cdp enable

!

interface Serial7/6:15

no ip address

encapsulation hdlc

isdn switch-type primary-net5

isdn bind-l3 iua-backhaul as0

no cdp enable

…/…

mgcp

mgcp request timeout 3000

mgcp call-agent xx.xx.1.37 2427 service-type mgcp version 1.0

mgcp dtmf-relay voip codec all mode out-of-band

mgcp max-waiting-delay 5

mgcp modem passthrough voip nse

mgcp modem passthrough voip codec g711alaw

mgcp codec g729r8 packetization-period 40

mgcp quarantine mode discard loop

mgcp ip qos dscp ef signaling

mgcp quality-threshold lwm-jitter-buffer 4

mgcp quality-threshold hwm-jitter-buffer 100

mgcp playout adaptive 50 30 100

mgcp package-capability dtmf-package

mgcp package-capability rtp-package

mgcp tse payload 111

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp sdp notation undotted

no mgcp piggyback message

mgcp fax rate 14400

mgcp rtp payload cisco-pcm-switch-over-alaw 127

mgcp bind control source-interface Loopback2427

mgcp bind media source-interface Loopback2427

mgcp behavior auep v0.1

mgcp rtp payload-type clear-channel static

!

We want to use the AS5400 in the following way - without hw modification


Create ISDN access (may be to 1 BRI up to 3 BRI)

Use of this access to perform video conferencing.


To perform this it seems that the G nx64K could be used


But the point is

1) The TGW is managed by MGCP protocol so all the command are related to one End Point

2) The TGW are in the Core network and are not dedicated to a specific customer so the configuration has to be OK for every body whatever the usage is.


So I wonder how must be performed the aggregation of the B channel up to 6 channels if we want to reach 384 k


1) Is it possible to perform this on the Call Agent Side ?

2) Is there something to specify on the TGW

3) Is it necessary to add specific HW

4) Is it not possible to perform this kind of services using this TGW


Thank in Advance for all the help you can give me




  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 1 (1 ratings)
Loading.
htarra Fri, 06/20/2008 - 11:54
User Badges:
  • Bronze, 100 points or more

Codec will be negociated and same codec on both directions is determined normally by TGW.

Payload sizes normally are determined by the codec preferrence defined on each gateway.

And different payload sizes can interoperate, i.e, g723ar53 on one direction, g723ar63 on the other.

http://www.cisco.com/en/US/tech/tk1077/technologies_tech_note09186a0080094045.shtml

Actions

This Discussion