logical disconnection during D channel transmission

logical disconnection during D channel transmission

Post by GTERRI » Thu, 17 Jul 2003 16:06:21



Hello,

Can anybody help me on the following:

   I try to transfert data over D channel;I have made a C program
which use CAPI functions.I think that my paramaters for the connection
set up are good

The analyser gives:
Controller: 0x00000001
    CIP value: 7 (packet mode)
    Called Party Number (0x9): 0x81 '96356133'
    Calling Party Number (0x0):
    Called Party Subaddress (0x0):
    Calling Party Subaddress (0x0):
    B protocol (0x1e):
      B1 protocol: 0 (64 kBit/s HDLC)
      B2 protocol: 3 (LAPD for D channel X.25)
      B3 protocol: 2 (ISO 8208 (X.25 DTE-DTE))
      B1 configuration (0x0):
      B2 configuration (0x5):
        TEI assignment: 0x3 (fixed value 1)
        Address B: 0x0
        Modulo Mode: 0x8
        Window Size: 0x3
        XID (0x0):
      B3 configuration (0x10):
        LIC: 0x0
        HIC: 0x0
        LTC: 0x1
        HTC: 0x1
        LOC: 0x0
        HOC: 0x8
        Modulo Mode: 0x8
        Window Size: 0x2
    BC (0x0): 04 04 88 C0 C6 E6
    LLC (0x0):
    HLC (0x0):
    Additional Info (0x6):
      B channel info (0x2): use D channel
      Keypad facility (0x0):
      User user data (0x0):
      Facility data array (0x0):

I have a physical connection but I have some problems with the logical
one;this is what is happen:

--> CONNECT_REQ
<-- CONNECT_CONF
<-- CONNECT_ACTIVE_IND
--> CONNECT_ACTIVE_RESP

--> CONNECT_B3_REQ
<-- CONNECT_B3_CONF
<-- DISCONNECT_B3_ACTIVE_IND        //
--> DISCONNECT_B3_ACTIVE_RESP       //

I don't understand why I haven't a CONNECT_B3_ACTIVE_IND and a
CONNECT_B3_ACTIVE_RESP message; apparently it is due to
"Reason_B3:0000" (clearing according to protocol).

            Can anybody help me on my disconnection problem?

                                                             thanks

                                                            Guillaume
Terrien

 
 
 

logical disconnection during D channel transmission

Post by Hans-Jürgen Ortman » Wed, 23 Jul 2003 20:46:50


unfortunately the ReasonB3 does not contain any information - but the NCPI
in the DISCONNECT_B3_IND may contain additional information. Otherwise you
would have to trace the X.25 layer - almost every manufacturer is offering
trace tools for b/d channel trace

HansJuergen

 
 
 

logical disconnection during D channel transmission

Post by GTERRI » Thu, 24 Jul 2003 18:53:32



> unfortunately the ReasonB3 does not contain any information - but the NCPI
> in the DISCONNECT_B3_IND may contain additional information. Otherwise you
> would have to trace the X.25 layer - almost every manufacturer is offering
> trace tools for b/d channel trace

> HansJuergen

The card I use is a EICON card(DIVA 2.01);I have already traced the
X25 layer but the only frames I have about DISCONNECT_B3-IND are:

DISCONNECT_B3 IND, AppID 0x0001, MsgNr 0x0001
    NCCI: 0x00010101
    Reason_B3: clearing according to protocol
    NCPI (0x5):       D-Bit: off
      PVC group number: 0x0
      PVC number: 0x0
      Bytes following id field (0x2): 13 26

Unfortunatelly, I don't understand why I obatain this disconnect
message just after a CONNECT_B3_CONF.Is it possible that the called
center refuses the connexion?

                                     If you a solution for my
problem...

                                          thanks

                                               Guillaume Terrien

 
 
 

logical disconnection during D channel transmission

Post by Jochen Klei » Thu, 24 Jul 2003 23:46:17


Hi,

Quote:> The card I use is a EICON card(DIVA 2.01);I have already traced the
> X25 layer but the only frames I have about DISCONNECT_B3-IND are:

Well, but what you priviede is a piece of a CAPI trace, not of a plain  or
X.31/X.25 formated D-Channel trace.

Quote:> DISCONNECT_B3 IND, AppID 0x0001, MsgNr 0x0001
>     NCCI: 0x00010101
>     Reason_B3: clearing according to protocol
>     NCPI (0x5):       D-Bit: off
>       PVC group number: 0x0
>       PVC number: 0x0
>       Bytes following id field (0x2): 13 26

If I analyze it correct (my active X.25 times are laying many, many years
back) it means Reson=13dec, Diag=26dec,
which means Reason=Destionation not reachable and diagnostics=invalid packet
type in state P7.

Quote:> Unfortunatelly, I don't understand why I obatain this disconnect
> message just after a CONNECT_B3_CONF.

Well with this CONF CAPI confirms that it has accepted and will process your
conenct_b3_req. Then it does process it and most likly gets a X.25/X.31
DISCONNECT and signals this to the application within a disconnect_b3_ind
msg.

Quote:>Is it possible that the called center refuses the connexion?

Could be, but according to the Reason and Diagnostics it seems to be a
differnet prob. I guess the destionation does ven not see your CONNECT
messages.

I think the best way is, as Hans-Jrgen allready suggested to make a X.25
(!) trace and analyze this.

Regards,
Jochen Klein
www.servonic.de

 
 
 

logical disconnection during D channel transmission

Post by GTERRI » Wed, 30 Jul 2003 21:00:24


My problem is solved.In fact the NCPI struct was incorrect; when we
use D channel we had to passed the called number in DCB, and no in
decimal.In fact I didn't called the good number, that is why I had a
disconnect_B3_req.

         These is how I code the connect_b3_req:

//Length
        CAPIMsg.info.connect_b3_req.structs[bCount++] = 8;
//flag
   CAPIMsg.info.connect_b3_req.structs[bCount++] = 1;
//group
   CAPIMsg.info.connect_b3_req.structs[bCount++] = 0;
//Channel
   CAPIMsg.info.connect_b3_req.structs[bCount++] = 1;
//Called number
        CAPIMsg.info.connect_b3_req.structs[bCount++] = 150;            //96
        CAPIMsg.info.connect_b3_req.structs[bCount++] = 53;             //35
        CAPIMsg.info.connect_b3_req.structs[bCount++] = 97;             //61
        CAPIMsg.info.connect_b3_req.structs[bCount++] = 51;             //33
//Facilities length
         CAPIMsg.info.connect_b3_req.structs[bCount++] =0;

        CAPIMsg.header.length = CAPIMSG_HEADER_LEN + bCount;

                                                          Best regards
                                                          Guillaume
Terrien

 
 
 

1. Disconnection of Phone Conversation During Computer Power-up

I have an interesting problem that I could use some input on.  I have a
Max-Link voice/data/fax 33.6 internal modem, and I always get
disconnected from a telephone conversation if I turn on my computer.  Is
this a hardware problem, or can Win98 settings rectify this?  Any input
would be appreciated....

-Tom-

2. No interface UP message(RTM_IFINFO) in routing socket for nt0

3. Disconnection during data transfer

4. sram crashing

5. Cisco X.25 load balancing over two logical channels

6. I will go on til somebody cares!!!!! GSM>Data

7. cellular modems

8. X31, number of logical channels (Re)

9. X.31, number of logical channels

10. X.31: more than one logical channel

11. speed of transmission, channel bandwidth, modulation

12. speed of transmission, channel bandwidth and modulation