MGCP Gateway With ISDN BRI interface

Hi Guys,
I have a voice gateway with a BRI card on slot 0/3/0 (port 0/1) and I wanted to terminate both WAN and PSNT connection to the same gateway with MGCP protocol, and as I'm new to voice over IP world can anyone suggest/recommand me a proper guide which includes the stepts and proper explanations to acheive this task.
Thank you
Regards,
Suthakar

Hi Aman,
As discussed please find the attached output as follows,
#sh isdn status
Global ISDN Switchtype = basic-net3
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 0. Layer 3 output may not apply
ISDN BRI0/0/0 interface
dsl 0, interface ISDN Switchtype = basic-net3
L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER 0x0003
    Layer 1 Status:
DEACTIVATED
    Layer 2 Status:
Layer 2 NOT Activated
    Layer 3 Status:
0 Active Layer 3 Call(s)
    Active dsl 0 CCBs = 0
    The Free Channel Mask:  0x80000003
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 1. Layer 3 output may not apply
ISDN BRI0/0/1 interface
dsl 1, interface ISDN Switchtype = basic-net3
L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER 0x0003
    Layer 1 Status:
DEACTIVATED
    Layer 2 Status:
Layer 2 NOT Activated
    Layer 3 Status:
0 Active Layer 3 Call(s)
    Active dsl 1 CCBs = 0
    The Free Channel Mask:  0x80000003
ISDN BRI0/3/0 interface
dsl 12, interface ISDN Switchtype = basic-net3
    Layer 1 Status:
ACTIVE
    Layer 2 Status:
Layer 2 NOT Activated
    Layer 3 Status:
0 Active Layer 3 Call(s)
    Active dsl 12 CCBs = 0
    The Free Channel Mask:  0x80000003
%Q.931 is backhauled to CCM MANAGER 0x0003 on DSL 13. Layer 3 output may not apply
ISDN BRI0/3/1 interface
dsl 13, interface ISDN Switchtype = basic-net3
L2 Protocol = Q.921 0x0000  L3 Protocol(s) = CCM MANAGER 0x0003
    Layer 1 Status:
ACTIVE
    Layer 2 Status:
Layer 2 NOT Activated
    Layer 3 Status:
0 Active Layer 3 Call(s)
--More--                               Active dsl 13 CCBs = 0
    The Free Channel Mask:  0x80000003
    Total Allocated ISDN CCBs = 0
#sh ccm-manager
MGCP Domain Name: xxxxx.com
Priority        Status                   Host
============================================================
Primary         Registered               x.x.x.x
First Backup    None                    
Second Backup   None                    
Current active Call Manager:    x.x.x.x
Backhaul/Redundant link port:   2428
Failover Interval:              30 seconds
Keepalive Interval:             15 seconds
Last keepalive sent:            11:10:43 AEDST Nov 21 2013 (elapsed time: 00:00:11)
Last MGCP traffic time:         11:10:43 AEDST Nov 21 2013 (elapsed time: 00:00:11)
Last failover time:             None
Last switchback time:           None
Switchback mode:                Graceful
MGCP Fallback mode:             Enabled/OFF
Last MGCP Fallback start time:  05:28:32 AEDST Nov 18 2013
Last MGCP Fallback end time:    11:57:01 AEDST Nov 20 2013
MGCP Download Tones:            Disabled
TFTP retry count to shut Ports: 2
Backhaul Link info:
    Link Protocol:      TCP
    Remote Port Number: 2428
    Remote IP Address:  x.x.x.x
    Current Link State: OPEN
    Statistics:
        Packets recvd:   3
        Recv failures:   0
        Packets xmitted: 5
        Xmit failures:   0
    BRI Ports being backhauled:
        Slot 0, VIC 0, port 1
        Slot 0, VIC 0, port 0
        Slot 0, VIC 3, port 1
Configuration Auto-Download Information
=======================================
Current version-id: 1384908973-2cefe363-d1ae-423b-a6ef-a85a0d4216af
Last config-downloaded:00:00:00
Current state: Waiting for commands
Configuration Download statistics:
Download Attempted             : 6
  Download Successful          : 3
  Download Failed              : 1
  TFTP Download Failed         : 8428
Configuration Attempted        : 3
  Configuration Successful     : 3
  Configuration Failed(Parsing): 0
  Configuration Failed(config) : 0
Last config download command: New Registration
FAX mode: disable
Configuration Error History:
Regards,
Suthakar

Similar Messages

  • No dialer command under ISDN BRI interface

    Hi all,
    I have a 2901 router voice bundle with 4 ISDN BRI ports and would like to have them bundled under Dialer1 interface. Unfortunately it doesn't give me option for Dialer command under BRI interface as expected. 
    router(config-if)#int bri0/0/0
    router(config-if)#dia
    router(config-if)#dia
                             ^
    % Invalid input detected at '^' marker.
    router(config-if)#dialer
                             ^
    % Invalid input detected at '^' marker.
    router(config-if)#
    I assume it's down to the UC license installed on the device but not sure. Does the ISDN BRI interface behave in different way under this license?
    Pasting portion of "show ver" as well.
    Cisco CISCO2901/K9 (revision 1.0) with 479232K/45056K bytes of memory.
    Processor board ID 
    2 Gigabit Ethernet interfaces
    4 ISDN Basic Rate interfaces
    1 terminal line
    DRAM configuration is 64 bits wide with parity enabled.
    255K bytes of non-volatile configuration memory.
    250880K bytes of ATA System CompactFlash 0 (Read/Write)
    License Info:
    License UDI:
    Device#   PID                   SN
    *0        CISCO2901/K9          
    Technology Package License Information for Module:'c2900'
    Technology    Technology-package           Technology-package
                  Current       Type           Next reboot
    ipbase        ipbasek9      Permanent      ipbasek9
    security      None          None           None
    uc            uck9          Permanent      uck9
    data          None          None           None
    Configuration register is 0x2102

    Hi,
              Snippet of "sh ver" with IOS version is below:
    router#show ver
    Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.2(4)M5, RELEASE SOFTWARE (fc2)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2013 by Cisco Systems, Inc.
    Compiled Fri 13-Sep-13 14:59 by prod_rel_team
    ROM: System Bootstrap, Version 15.0(1r)M16, RELEASE SOFTWARE (fc1)
    router uptime is 2 days, 21 hours, 47 minutes
    System returned to ROM by reload at 16:48:03 UTC Mon Aug 18 2014
    System restarted at 16:50:01 UTC Mon Aug 18 2014
    System image file is "flash0:c2900-universalk9-mz.SPA.152-4.M5.bin"
    Last reload type: Normal Reload
    Last reload reason: Reload Command
    The output of trying to type dialer command is in the initial post, I'm also pasting all available commands under bri0/0/0.
    router(config-if)#int bri0/0/0
    router(config-if)#?
    Interface configuration commands:
      aaa                     Authentication, Authorization and Accounting.
      access-expression       Build a bridge boolean access expression
      arp                     Set arp type (arpa, probe, snap), timeout, log
                              options or packet priority
      authentication          Auth Manager Interface Configuration Commands
      autodetect              Autodetect Encapsulations on Serial interface
      bandwidth               Set bandwidth informational parameter
      bgp-policy              Apply policy propagated by bgp community string
      bridge-group            Transparent bridging interface parameters
      carrier-delay           Specify delay for interface transitions
      cdp                     CDP interface subcommands
      clns                    CLNS interface subcommands
      clock                   Configure serial interface clock
      cwmp                    Configure CPE WAN Management Protocol(CWMP) on this
                              interface
      dampening               Enable event dampening
      default                 Set a command to its defaults
      delay                   Specify interface throughput delay
      description             Interface specific description
      dot1q                   dot1q interface configuration commands
      dot1x                   Interface Config Commands for IEEE 802.1X
      down-when-looped        Force looped serial interface down
      encapsulation           Set encapsulation type for an interface
      ethernet                Ethernet interface parameters
      exit                    Exit from interface configuration mode
      flow-sampler            Attach flow sampler to the interface
      full-duplex             Configure full-duplex operational mode
      h323-gateway            Configure H323 Gateway
      half-duplex             Configure half-duplex and related commands
      help                    Description of the interactive help system
      history                 Interface history histograms - 60 second, 60 minute
                              and 72 hour
      hold-queue              Set hold queue depth
      ip                      Interface Internet Protocol config commands
      iphc-profile            Configure IPHC profile
      ipv6                    IPv6 interface subcommands
      isdn                    ISDN Interface configuration commands
      isis                    IS-IS commands
      iso-igrp                ISO-IGRP interface subcommands
      keepalive               Enable keepalive
      line-power              Provide power on the line.
      llc2                    LLC2 Interface Subcommands
      load-interval           Specify interval for load calculation for an
                              interface
      logging                 Configure logging for interface
      loopback                Configure internal loopback on an interface
      mab                     MAC Authentication Bypass Interface Config Commands
      mac-address             Manually set interface MAC address
      macro                   Command macro
      metadata                Metadata Application
      mop                     DEC MOP server commands
      mtu                     Set the interface Maximum Transmission Unit (MTU)
      netbios                 Use a defined NETBIOS access list or enable
                              name-caching
      network-clock-priority  Configure clock source priority
      no                      Negate a command or set its defaults
      ntp                     Configure NTP
      ospfv3                  OSPFv3 interface commands
      pulse-time              Force DTR low during resets
      rate-limit              Rate Limit
      redundancy              RG redundancy interface config
      routing                 Per-interface routing configuration
      sdllc                   Configure SDLC to LLC2 translation
      serial                  serial interface commands
      service-policy          Configure CPL Service Policy
      shutdown                Shutdown the selected interface
      smds                    Modify SMDS parameters
      snapshot                Configure snapshot support on the interface
      snmp                    Modify SNMP interface parameters
      source                  Get config from another source
      tarp                    TARP interface subcommands
      timeout                 Define timeout values for this interface
      topology                Configure routing topology on the interface
      transmit-interface      Assign a transmit interface to a receive-only
                              interface
      trunk-group             Configure interface to be in a trunk group
      tx-ring-limit           Configure PA level transmit ring limit
      vpdn                    Virtual Private Dialup Network
      vrf                     VPN Routing/Forwarding parameters on the interface
      waas                    WAN Optimization
    router(config-if)#

  • ISDN BRI INTERFACE

    Isdn bri interface is used as backup by serial interface
    backup delay 10 60
    under bri interface following command is also configured
    dialer idle-timeout 900
    what will be idle timeout of bri interface if serial interface comes back and functional.

    Hello Jabbar,
    this looks like a cisco BCRAN question, here it goes:
    the backup delay 10 60 , means that it will take 10 seconds before the secondary link comes up, after the primary goes down, and it will take 60 seconds after the primary goes back up, before the secondary goes down.
    dialer idle-timeout 900:
    this command indicates how long the call can stay idle before it is disconnected.
    from cisco:
    "This command is used on lines for which there is no contention. When contention occurs, the dialer fast-idle command is activated. For example, when a busy line is requested to send another packet to a different destination than it is currently connected to, line contention occurs and the dialer fast-idle command is activated.
    By default, this command applies to inbound and outbound calls. For example, if a receiving system needs to make outgoing calls, you might configure it with a short idle timeout.
    Only packets that match the dialer group reset the idle timer."
    So, I guess it would be 900s
    HTH,
    please rate this post if it does,
    Vlad

  • Isdn bri interfaces

    If I had 2 isdn routers on different sites and wanted them to connect, do I need to put both BRI interfaces on the same subnet or does it not matter with isdn ?

    Hi
    AFAIK there are 2 ways one is considering the isdn connectvitiy as a seperate point to point link and assigining a seperate /30 block for that connectivity or else you can also use ip unnunmbered option and make use of your ethernet ip or the loopback ip.
    But i would suggest to go with the first option coz of the simplicity involved, also the second option may create or result in some operational problems if you have some routing protocol in place between your locations.
    regds

  • IDLE-TIMEOUT IN ISDN BRI INTERFACE

    If bri isdn interface is backup by serial interface. Two commands are president for timeout bri interface
    one under backup serial interface
    1. backup delay 10 30
    The other under bri interface
    2. dialer idle-timeout 800
    My query is when interface serial comes back what will be time bri interface to in the disconnect position 30 or 800.

    hi
    AFAIK ideally the time would be 830 (30+800) coz the traffic will only get diverted back to serial interface after its observed stable for the configured time period which is 30 here.
    Once it starts getting the traffic thru main serial interface the dialer interface will become idle..
    so it will have to stay upto the timeout period (800 here)configured to get disconnected..
    regds

  • Set B Channel ID information to Preferred in MGCP Gateway

    Hi All,
    We recently had some E1 PRI issues and our Service Provider has asked us to set B Channel ID information to Preferred.
    We are using a MGCP Gateway with CUCM 9.1.2
    When we enable ISDN debug we could see the Channel ID as Exclusive.
    Jul 25 13:02:07.566: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8  callref = 0x0043
            Sending Complete
            Bearer Capability i = 0x8090A3
                    Standard = CCITT
                    Transfer Capability = Speech
                    Transfer Mode = Circuit
                    Transfer Rate = 64 kbit/s
            Channel ID i = 0xA98381
                    Exclusive, Channel 1
    I tried to change it to Preferred by configuring the command, "isdn negotiate-bchan"   under the serial interface but still debug shows it as Exclusive only.
    Let me know whether we can change the B Channel information either in CUCM or MGCP Gateway.

    Hi
    Can you try the below:-
    1- interface x/x/x:15
    isdn protocol-emulate network
     isdn bchan-number-order ascending
    then test again
    2-Go to CUCM - gateway and do the below
    CHANNEL IE TYPE " TIMESLOTS " 
    Thanks
    please rate all useful information

  • ISDN BRI U

    Hi All,
    I recently purchased Cisco 2811 with ISDN BRI U HWIC for ISDN connectivity. Unfortunately, when I connect the card to my ISDN NT box, the light on the ISDN NT box keeps flashing signifying no connectivity, while there are no signs of light behind the HWIC card either. When I swapped this out with a normal ISDN BRI S/T card, I can see a steady light on the NT box and also light behind the HWIC on the router meaning there is connectivity between the router and the ISDN NT box.
    A quick check on Cisco website shows that these type of cards require RJ-49C connector (see site below)
    http://www.cisco.com/en/US/prod/collateral/modules/ps5949/data_sheet_c78_439537.html
    Can someone be kind enough to let me know if/why normal RJ-45 cables cannot be used? Also, I am struggling to  get information online on these RJ-49C connectors.
    Thanks
    Austin

    ISDN needs proper cabling, not Ethernet cabling.
    The pinour is in the product manual.

  • Configuring BRI interface for Voice ( MGCP gateway

    hi there,
    i have a Call Manager which is connect to Cisco 2800 series acting as MGCP getway. ISDN connection between the 2800 and the carrier ( telestra sydney ). the call manager is seeing the gateway and i have configured a numbering plan on the call manager for the phones. the phones can call internally but externally i dont what configuration i should configure under the BRI interface for the carrier ( telestra ) to recongnise my number plan. please if you have any demo configuration or configuration that has perviously used post to me.

    this is a basic MGCP config on the Gateway on your area
    BRI Switchtype Information
    BRIs in Australia require no service profile identifiers (SPIDs).
    There are two ISDN switch-types that can be used:
    basic-net3?Currently the most commonly used.
    basic-ts013?For older ISDN switches such as MicroLink.
    isdn switch-type basic-net3 or 5
    voice-card 2
    dspfarm
    dsp services dspfarm
    controller T1 2/0
    description T1 link to SRST
    framing esf !--- Automatic method automatically adds
    clock source internal
    linecode b8zs !--- Automatic method automatically adds
    cablelength short 133
    pri-group timeslots 1-2,24 service mgcp !--- Automatic method
    !--- automatically adds 24 channels.
    !---You can manually edit channels.
    description T1 link to SRST
    interface Serial2/0:23
    no ip address
    isdn switch-type primary-ni !--- Automatic method automatically adds
    isdn protocol-emulate network !--- Simulated Lab ISDN
    isdn bind-l3 ccm-manager !--- Allows all Q931 to be backhauled over TCP to
    !--- CallManager; automatic method automatically adds
    no cdp enable !--- Automatic method automatically adds
    ccm-manager mgcp
    ccm-manager music-on-hold
    ccm-manager config server 171.69.103.225
    ccm-manager config !--- Enables automatic config download from CallManager
    !--- Automatic method automatically adds these commands
    mgcp
    mgcp call-agent 171.69.103.225 2427 service-type mgcp version 0.1
    mgcp dtmf-relay voip codec all mode out-of-band
    mgcp rtp unreachable timeout 1000 action notify
    mgcp modem passthrough voip mode nse
    mgcp package-capability rtp-package
    mgcp package-capability sst-package
    no mgcp package-capability fxr-package
    mgcp package-capability pre-package
    no mgcp timer receive-rtcp
    mgcp sdp simple
    mgcp fax t38 inhibit
    mgcp rtp payload-type g726r16 static
    mgcp profile default

  • Back to Back PRI with MGCP Gateways

    I?ve got a 3825 with T1 voice modules (RJ45)..
    They are configured as MGCP managed by a set of call managers.
    On Friday, I have to integrate this gateway with an old Mitel switch, which will be used during a 2 year phased migration to get calls between old and new systems? To prepare for that, I have setup the T1s back to back for testing/validation that my MGCP config is working.
    I can configure those T1s as ?T1 CAS? trunks, and put a crossover cable between them, make a route pattern 3.xxxx and have the call go out one T1, and back in the other, and it works great? The problem is that there?s no caller ID information set. In the trunk configuration screens, there are fields to specify that callerID should, or should not be sent, etc, but it just doesn?t go.. I?m not terribly surprised by this, because I don?t think there?s any protocol defined for the ?plain? T1 to transfer callerID.. I guess I was just hoping that somehow, it would work! :-)
    What I would REALLY like to do, is to put these two T1s in PRI mode, since I *KNOW* a PRI can send callerID, but to do that, I have to have one of the ports emulate the CO-side switch.
    When configured as PRI signalled T1s, I saw a pull-down that said something like ?Protocol Side? or ?Protocol Mode? (Sorry, it?s not configured as PRI right now, so I can?t look at the verbiage), and the selections were ?Network? and ?User?, which sound to me as if it?s EXACTLY what I need, but I couldn?t get it to come up to even test? It acted as if I had a timing issue, even though I hadn?t changed any timing parameters from the T1 CAS settings that worked (One internal, one external).. I was getting intermittent amber alarms, and the trunk never came up.
    Unfortunately, I can only change the configs on this thing early in the morning, because yesterday, some of the MGCP control I was doing through the CM gui actually bounced their WAN T1s that are in the same router, so now I have to be careful!!
    What I would like, is to get a definitive answer to whether two MGCP controlled T1s can be back to back in a PRI signaling mode, and/or if there?s another way to get callerID across a T1 link without one end of it being the CO itself. Ultimately, it won't be a cisco-cisco crossover, but rather a cisco-mitel solution, so whatever I come up with MUST be standards based, so at least I can have something to expect the Mitel engineer to be able to do..
    Any help would be GREATLY appreciated!!!
    -Steve

    Steve,
    Never tried a back-to-back PRI with both routers being MGCP. I have in my lab two routers back to back with one router being edge voice gateway controlled by mgcp and the other being a pstn simulator. On the edge voice gateway the following configs exist.
    controller t1 1/0
    pri-group timeslots 1-24 service mgcp
    ccm-manager mgcp
    mgcp
    mgcp call-agent
    int s1/0:23
    isdn switch-type
    isdn incoming-voice voice
    On the PSTN router (which emulates a PSTN switch)
    controller t1 1/0
    pri-group timeslots 1-24
    int s1/0:23
    isdn protocol-emulate network
    isdn switch-type
    isdn incoming-voice voice
    This should work for back-to-back PRI pretty well.

  • Remote C2901 MGCP gateway won't register with CUCM

    Hi, all,
    We have a central call manager, we are setting up a remote office with a C2901 voice gateway that has a T1 PRI, this gateway is being configured as a H.323 gateway, everything worked fine. Now I want to get SRST working such that when WAN goes down, employees can still make outbound calls and take inbound calls. I followed SRST documentations when configuring CUCM and C2901, I would say the documentations are clear and easy to follow -- only thing is there is no adequate explanation of why those commands need to be there and I can not get SRST to work.
    1), First, a basic concept question, why do we need to configure "ccm-manager fallback-mgcp"? or any MGCP related configuration on C2901? how does MGCP play the role in SRST? the router is configured as a simple voice gateway, when WAN is intact, we use H.323 protocol, when WAN goes down, we still don't need MGCP ...
    2), Assuming that we needed all those SRST related MGCP configuration, I would expect C2901 to register to call manager, but I could not get this device to register as a MGCP gateway, debug mgcp packets shows:
    *Sep  5 16:52:47.571: MGCP Packet sent to 10.128.181.5:2427--->
    RSIP 201356931 *@voicegw-remoteoffice.local.domain MGCP 0.1
    RM: restart
    <---
    *Sep  5 16:52:47.631: MGCP Packet received from 10.128.181.5:2427--->
    500 201356931
    <---
    I verified the domain name is exactly the same as the name configured on CUCM, I tried multiple time toggling ip domain name on C2901 also, somehow CUCM does not like RSIP message from C2901, I don't have knowledge to get debug information from CUCM side of why CUCM does not like the MGCP message sent by C2901
    3), When the communication is blocked from C2901 to central call manager (by using a simple ACL on C2901's default gateway device), I can still make the inbound call to an IP phone, which means, phones were correctly registered to C2901 when communication to call manager is broken, but I can not make outbound call, phones always get quick busy beeps, test call from C2901 itself (by using "csim start") is fine, which means dial-plan and ISDN/PRI is fine.
    I believe we are just doing very very basic configuration and this is a common scenario, what could I do wrong?

    You dont need the mgcp related commands if you are using H323. The commands that you need are:
    application
    global
    service alternate default
    call-manager-fallback (or) telephony-service and the relevant commands under it.
    Also make sure that SRST reference has been added to the DP and the phones reset after the change made. This is what tell the phone to register to the SRST gateway when the WAN is down. The IP specified in the SRST reference should match whats configured under call-manager-fallback.

  • Trouble adding second port BRI in a 2801 MGCP gateway

    my config is CCM 413 with a 2801 SRST including a VIC2-2BRI .
    I have configured the 2801 as MGCP gateway on the CCM, added the module VIC2-2BRI and configured the BRI 0/0/0 in this gateway.
    this BRI work properly with the PSTN . I can make successfull call inbound and outbound
    Now I want to add the second BRI (ie BRI 0/0/1 ) in the gateway for the same hunt group, the same PSTN provider.
    When I do that this BRI can't register and make different kind of problem on the existing well working BRI.
    for example I noticed that I can make inbound or outbound call with connected state but no voice in the two way.
    I noticed also that the first BRI become completely blocked after two call.
    I have verified the conf of the BRI 0/0/1 but i don't see any difference with the BRI 0/0/0 .
    the only way to get back good working of the BRI 0/0/0 is to remove BRI 0/0/1 from the gateway conf.

    Hello,
    That is a good news though. Can you please share to me the TAC case nr? So I can refer this to tAC. Because we have also opened a CASE for the same problem on the 3725 but not hear from TAC yet for the patch!
    I got another image ie. IPVOICE version 12.4.1.9 from a friend that has the patch for this problem on the 2801 but there is no SPSERVICES image yet.
    Now it looks that Cisco has a newer image.
    Thanks in advance.
    Regards

  • Router with BRI interface

    i need your support to know model Router with BRI interface

    The Cisco 876 (cheapest option) provides ADSL over ISDN
    http://www.cisco.com/en/US/products/hw/routers/ps380/products_data_sheet0900aecd8028a976.html
    For integrated ISDN BRI, I suggest looking at the 1800 Series
    http://www.cisco.com/en/US/products/ps6184/index.html

  • Problem connecting isdn bri voice interface to pstn

    i'm trying to configure my ISDN BRI NT/TE voice interface card (VIC-2BRI-NT/TE) on router 3825 to link to my PSTN provider. This must allow my Cisco IP phones to pass call to the PSTN through my call manager 4.1.
    I suscribe to two isdn line. The provider told me that the SWITCH TYPE is VN6 (COTE d'IVOIRE or Ivory Coast).
    For my bri configuration, see file "interfaces configuration..."
    My problem is that when i pass call from my Ip telephony network, the first call goes well. But after this first call, when i type the command isdn status, i can see that the layer 1 of my isdn interfaces are DEACTIVATED, and after a few minutes, it turn back to ACTIVE. During these minuite, i can't pass any call through my isdn interface.
    for outputs of show isdn status command, and isdn debug q931 commands
    see file "show isdn status and debug..."
    Notice: when the status of the isdn layer is in the deactvated status, i can receive call from the pstn, but i can't passe call to pstn (the state changes to ACTIVE when incomming call from pstn arrive, but still stay DEACTIVATED when outgoing call is initiated)
    Please help me

    I've entered the "isdn transition-delay 1" interface command and things seem to work well.According to the IOS help on my router,this command clears the ISDN D-CHANNEL after a delay of 1 second.
    But i would like to get more information on this command, and also on the isdn layer 2 and 3 timers, and even possible on all the "isdn" interface command option.
    THANKS

  • SRST with T1 CAS MGCP Gateway

    Hello - we are trying to configure SRST on our T1 CAS MGCP gateway. We have been informed by a Cisco engineer that we cannot use SRST on a T1 CAS MGCP gateway and that the gateway must first be reconfigured as an H.323 gateway in order to implement SRST. Router is version 12.2(15)T14 and CCM 4.1 Any comments would be truly appreciated...thank you.

    SRST doesn't support MGCP but does support MGCP to H.323 failback. You can still configure your router/CCM with MGCP then use the fallback commands for MGCP.
    Looking at the SRST 4.0 system guide, page 42, T1 CAS is supported. With your version of IOS you would be running SRST 2.1, this is also supported.
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t15/srst21/srstv21.pdf
    http://www.cisco.com/univercd/cc/td/doc/product/voice/srst/srst40/srst40ad/s40sa.pdf
    The ccm-manager fallback-mgcp command was added in IOS 12.2(11)T so it should be in your version. This is what you would need to do MGCP fallback to your H323 along with the call application alternate default.
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123tcr/123tvr/vrht_c4.htm#wp1061367
    http://www.cisco.com/univercd/cc/td/doc/product/software/ios123/123tcr/123tvr/vrht_c1.htm#wp1670149
    I would say it might be possible as I don't see anything saying no. Though remember MGCP fallback to H323 over SRST doesn't have call preservation.
    Lastly here is a document on the SRST MGCP/H323 fallback.
    http://www.cisco.com/en/US/tech/tk1077/technologies_configuration_example09186a008012ecc6.shtml
    Please rate any helpful posts
    Thanks
    Fred

  • Understanding ISDN BRI Voice Interface Cards

    Hi all,
    I was wondering about the VIC-2BRI-NT/TE VIC:
    In NT mode, what kind of BRI interface I can connect to it? Is it a BRI S/T interface (The device that is been connected to it)?
    I got a PBX that has BRI S/T interfaces... can i connect them to this card (while in NT state)?
    Will DID work in this case?
    Thanks,
    Edy.

    Hi Malleyne,
    Thanks for the response.
    I looked at the document, and I found my answers indeed. The only way to understand from the document (or any other on the net) that it will connect to an S/T interface is by the fact is says it acts as a NT1 device. Couldn't they make it more simple? :)
    Thanks again,
    Edy.

Maybe you are looking for