Feb 11

    ISDN-PRI Auto callback with Alcatel exchange

    Faraz Sharif
    S8300/G450 - CM 5.2 is tie using ISDN PRI with Alcatel 4400. Autocall back feature is working within avaya but that feature is not working with Alcatel 4400.
    I have configured trunk parameters according to guide CM features description and implementation manual.
    ISDN CCBS Supplementary Service on Busy
    Faraz Sharif
    I will appreciate if some one can help me on this subjected problem.

    Thanks in advance.
    Ferdinand Villanueva
    [Gulfsat Communications]
    Show some captured fields like trunk group, signalling and DS1.

    Max Barker
    Go back to Alcatel and ask why they are rejecting the Callback Request and post the answer. (I see 'bad ie' in trace you posted on other forum)

    Are you sure the Alcatel is configured for QSIG? Maybe they reject the callback because they are not QSIG.
    Faraz Sharif
    First of all thanks for reply.

    Below are the configuration captures of DS1, Signaling Group & Trunk Group.

    Voice System name: KHI-S8300 - DS1 CIRCUIT PACK

    Location: 001V4 Name: Test PRI 2
    Bit Rate: 2.048 Line Coding: hdb3

    Signaling Mode: isdn-pri
    Connect: pbx Interface: peer-master
    TN-C7 Long Timers? n Peer Protocol: Q-SIG
    Interworking Message: PROGress Side: a
    Interface Companding: alaw CRC? y
    Idle Code: 11111111 Channel Numbering: sequential
    DCP/Analog Bearer Capability: speech

    T303 Timer(sec): 4
    Disable Restarts? n

    Slip Detection? n Near-end CSU Type: other

    Echo Cancellation? n

    Signaling Group

    Voice System name: KHI-S8300 - SIGNALING GROUP

    Group Number: 10 Group Type: isdn-pri
    Associated Signaling? y Max number of NCA TSC: 10
    Primary D-Channel: 001V416 Max number of CA TSC: 0
    Trunk Group for NCA TSC:
    Trunk Group for Channel Selection: 2
    TSC Supplementary Service Protocol: b

    Trunk Group
    Voice System name: KHI-S8300 - TRUNK GROUP

    Group Number: 2 Group Type: isdn CDR Reports: y
    Group Name: OUTSIDE CALL COR: 1 TN: 1 TAC: *3
    Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
    Dial Access? y Busy Threshold: 255 Night Service:
    Queue Length: 32
    Service Type: tie Auth Code? n TestCall ITC: rest
    Far End Test Line No:
    TestCall BCC: 4

    Group Type: isdn

    Codeset to Send Display: 6 Codeset to Send National IEs: 6
    Max Message Size to Send: 260 Charge Advice: none
    Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc

    Trunk Hunt: cyclical
    Digital Loss Group: 13
    Incoming Calling Number - Delete: Insert: Format:
    Bit Rate: 1200 Synchronization: sync Duplex: full
    Disconnect Supervision - In? y Out? y
    Answer Supervision Timeout: 0
    Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n

    ACA Assignment? y Measured: none Wideband Support? n
    Long Holding Time(hours): 1 Internal Alert? n Maintenance Tests? y
    Short Holding Time(sec): 10 Data Restriction? n NCA-TSC Trunk Member: 2
    Short Holding Threshold: 15 Send Name: y Send Calling Number: y
    Used for DCS? n Hop Dgt? n Send EMU Visitor CPN? n
    Suppress # Outpulsing? y Format: public
    Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

    Replace Restricted Numbers? n
    Replace Unavailable Numbers? n
    Send Called/Busy/Connected Number: y
    Hold/Unhold Notifications? y
    Send UUI IE? y Modify Tandem Calling Number? n
    Send UCID? y
    Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

    Apply Local Ringback? y
    Show ANSWERED BY on Display? y
    Network (Japan) Needs Connect Before Disconnect? n

    TSC Method for Auto Callback: always-retain
    Diversion by Reroute? y
    Path Replacement? y
    Path Replacement with Retention? n
    Path Replacement Method: always
    SBS? n
    Display Forwarding Party Name? y
    Character Set for QSIG Name: eurofont
    QSIG Value-Added? y
    QSIG-Value Coverage Encoding: standard

    Administered Members (min/max): 1/30
    GROUP MEMBER ASSIGNMENTS Total Administered Members: 30

    Port Code Sfx Name Night Sig Grp
    1: 001V401 MM710 B PRI 1 10
    2: 001V402 MM710 B PRI 2 10
    3: 001V403 MM710 B PRI 3 10
    4: 001V404 MM710 B PRI 4 10
    5: 001V405 MM710 B PRI 5 10
    6: 001V406 MM710 B PRI 6 10
    7: 001V407 MM710 B PRI 7 10
    8: 001V408 MM710 B PRI 8 10
    9: 001V409 MM710 B PRI 9 10
    10: 001V410 MM710 B PRI 10 10
    11: 001V411 MM710 B PRI 11 10
    12: 001V412 MM710 B PRI 12 10
    13: 001V413 MM710 B PRI 13 10
    14: 001V414 MM710 B PRI 14 10
    15: 001V415 MM710 B PRI 15 10
    Bob Kennedy
    [Continuant, Inc.]
    Codeset to Send Display: 6 Codeset to Send National IEs: 6
    Max Message Size to Send: 260 Charge Advice: none
    Supplementary Service Protocol: b Digit Handling (in/out): enbloc/enbloc

    b is the ISO/ETSI QSIG privae network setting. You may want to try c or d one time.

    Bob K.
    AvayaTier3 bsh bshamilton
    [B & D Consulting]
    [LEFT]Automatic Callback used to only work on Definity to Definity over DCS networked Avaya switches.
    This changed with qsig:
    Automatic Callback works the same way as it does on a local server, on the following networks:[/LEFT]
    [LEFT]● On a Distributed Communication Server (DCS) network, Automatic Callback (ACB)
    requests from or to a station located on a different Communication Manager are queued
    and processed.[/LEFT]
    [LEFT]● If your public service network provider supports ISDN Call Completion Busy Subscriber
    (CCBS), the CCBS requests are queued and processed.[/LEFT]
    [LEFT]● On a QSIG network, ACB requests from or to a station located on a different[/LEFT]
    Communication Manager are queued.
    [LEFT]QSIG Call Completion - Administrable TSC Signaling Connection[/LEFT]
    [LEFT]This capability covers auto callback within a private corporate network only, for example,
    through QSIG. Communication Manager Release 4.0 or later provides an administrable option
    on the Trunk Group screen to allow users to specify the method of signaling connection the
    system uses while waiting for a busy station to become idle.
    TSC Method for Auto Callback field on the QSIG Trunk Group Options page of the Trunk
    Group screen allows customers to administer whether or not to retain the Temporary Signaling
    Connection (TSC) when QSIG Call Completion (QSIG-CC) is activated with other
    Communication Manager servers, or with non-CM servers (like the I55 or Siemens Hicom). The
    default value for the
    TSC Method for Auto Callback is drop-if-possible. The other option is to
    set the value to
    Older QSIG-CC standards require Path Reservation, which is not supported by Communication
    Manager. QSIG-CC can fail if the QSIG TSC is dropped when connected to a server that does
    not support the latest version of the QSIG-CC standards. In order for Communication Manager
    to work with servers based on old QSIG-CC standards, this retaining option is needed.
    Currently, the preferred QSIG-CC signaling connection method used by Communication
    Manager is the signaling connection release. In other words, Communication Manager
    populates the element
    retain-sig-connection in CCBS/CCNR invoke APDUs with the
    hard-coded value FALSE.
    With Communication Manager 4.0 or later, the new administration option on the Trunk Group
    screen controls:[/LEFT]
    [LEFT]● the element retain-sig-connection in CCBS/CCNR invoke APDUs, when CM is the
    originating PINX[/LEFT]
    [LEFT]● the signaling connection method for the QSIG-TSC when CM is the terminating or the[/LEFT]
    outgoing gateway PINX

    All Times America/New_York

    Copyright © 2018. The International Avaya User Group. All Rights Reserved

    All material, files, logos and trademarks within this site are properties of their respective organizations.

    Terms of Service - Privacy Policy - Contact