[nsp] Bad Bearercap: AS5300 to DEX-600E ISDN
Burns, Keith
Keith_Burns at icgcomm.com
Fri Nov 7 16:53:15 EST 2003
The problem "more than likely" is that you are sending out the Calling
Party# parameter list with the Type and Plan set to unknown/unknown instead
of ISDN and National.... and by YOU I mean.. the Cisco 5300/5400.
Some mobile carriers handle this, some don't (hence the apparent weirdness).
We found on our 5400, we had to use voice translation rules to set these (we
also have other outstanding Cisco issues to do with privacy on the same
deal... more on that later).
Here is a sample config:
! This bit sets those params to National and ISDN
!
voice translation-rule 50
rule 1 // // type any national plan any isdn
!
! Now we create the equivalent of a "voice" route-map
!
voice translation-profile CPN_RDN
translate calling 50
translate redirect-called 50
!
! Now we apply the sucker to a dial-peer
!
dial-peer voice 12960 pots
description To Support Trunk Group 1296/1297
translation-profile outgoing CPN_RDN
etc etc
Best of luck, and I hope this helps... if anything it MIGHT give you lead
with which to talk to the TAC... they weren't much help with us, but our 5E
dudes were instrumental in explaining to the TAC how Q.931 works in the
voice world.
Cheers
Keith
Keith Burns
Principal Network Architect
ICG Telecommunications
IP Ph: 303-414-5385
Cell: 303-912-3777
"The dogs may bark, but the caravan rolls on...."
> -----Original Message-----
> From: Andrew Melton [mailto:andy at meltons.net]
> Sent: Friday, November 07, 2003 10:37 AM
> To: cisco-nsp at puck.nether.net; Vincent De Keyzer
> Subject: RE: [nsp] Bad Bearercap: AS5300 to DEX-600E ISDN
>
>
> ---------- Original Message ----------------------------------
> From: "Vincent De Keyzer" <vincent at dekeyzer.net>
> Date: Fri, 7 Nov 2003 11:21:03 +0100
>
> >I think this might not be bad at all. The bearer cap problem
> could just be
> >that the AS5300 is not configured to accept "such" calls.
> >
> >For instance, when I place test calls from a PRI on a
> router, I can get to
> >call some mobile phones but not some others!... It has to be
> the right
> Here's the sh isdn status:
>
> ISDN Serial0:23 interface
> dsl 0, interface ISDN Switchtype = primary-dms100 :
> Primary D channel of nfas group 0
> Layer 1 Status:
> ACTIVE
> Layer 2 Status:
> TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
> Layer 3 Status:
> 0 Active Layer 3 Call(s)
> Active dsl 0 CCBs = 0
> The Free Channel Mask: 0x807FFFFF
> Number of L2 Discards = 1, L2 Session ID = 224
> --More--
>
> I can make calls into the switch, however, they're not
> routing out. The CDR says "no routing information in
> database". I'm not sure if that's a problem with our route
> lists or whether it's unable to route due to a bearercap mismatch.
>
> One thing I did accomplish, when I set the voice-port to
> 'isdn incoming-calls data/modem' calls to make it into the
> router, without the bearer cap error. Problem is, the call
> isn't routed to the DSP farm or to the VoIP dial peer I have...
>
>
> >combination of ISDN/voice/data etc., and both terminal
> equipments have to
> >agree on those.
> >
> >Can you place outgoing calls? (try different mobile
> phones/ISDN lines/fixed
> >phones, etc.)
> >
> >What does the 'sh isdn status' say for your Serial0?
> >
> >Vincent
> >
> >
> >> I'm trying to connect an AS5300 to an Alcatel Megahub 600E.
> >> The 600E can only communicate as DMS-250 or ANSI T1.607. We
> >> are using NFAS.
> >>
> >> I have tried isdn switch-type primary-dms100, but on all
> >> calls from the 600E to the gateway, my q.931 debug says:
> >>
> >> "Nov 5 17:35:14.282: ISDN Se0:23 **ERROR**: call_incoming:
> >> Received a call id 0x3D with a bad bearercap from 3103215708
> >> on b channel 12 Nov 5 17:35:14.286: ISDN Se0:23 Q931: TX ->
> >> RELEASE_COMP pd = 8 callref = 0x800C
> >> Cause i = 0x80BA - Bearer capability not available"
> >>
> >> I'm not sure what bearercap it's talking about. Has anyone
> >> had success with ISDN PRI signaling between an AS5300 and
> >> Alcatel/DEC DEX600?
> >>
> >> Any feedback would be helpful. Thanks.
> >>
> >> _______________________________________________
> >> cisco-nsp mailing list cisco-nsp at puck.nether.net
> >> https://puck.nether.net/mailman/listinfo/cisco> -nsp
> >> archive at
> >> http://puck.nether.net/pipermail/cisco-nsp/
> >>
> >
> >_______________________________________________
> >cisco-nsp mailing list cisco-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nsp
> >archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list