called number in D channel transmission

called number in D channel transmission

Post by GTERRI » Tue, 05 Aug 2003 16:53:41



Hello everybody,

I have just one question, when I want to called a centre over D
channel, I know that Called party number and the Calling party number
should be empty. The called number should be placed in the
connect_b3_req.
  This a trace of my application( just for the connexion over D
channel):

CONNECT REQ, AppID 0x0001, MsgNr 0x0000
    Controller: 0x00000001
    CIP value: 7 (packet mode)
    Called Party Number (0x0):
    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: 0x0
        Modulo Mode: 0x8
        Window Size: 0x3
    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):

10:28:43.968 T 1 D2Assign  01 -- -- -- -- -- -- -- -- -- -- --
10:28:43.968 T 1 D2Assign 1 d_id=01
10:28:43.968 - CAPI20_GET(014)
  0x0000  01 00 02 81  00 00 01 01  00 00 00 00              
............
  ---
  CONNECT CONF, AppID 0x0001, MsgNr 0x0000
    PLCI: 0x00000101
    Info: initiated

10:28:43.968 - CAPI20_GET(015)
  0x0000  01 00 03 82  00 00 01 01  00 00 00 00  00          
.............
  ---
  CONNECT_ACTIVE IND, AppID 0x0001, MsgNr 0x0000
    PLCI: 0x00000101
    Connected Number (0x0):
    Connected Subaddress (0x0):
    LLC (0x0):

10:28:43.970 - CAPI20_PUT(012)
  0x0000  01 00 03 83  00 00 01 01  00 00                    
..........
  ---
  CONNECT_ACTIVE RESP, AppID 0x0001, MsgNr 0x0000
    PLCI: 0x00000101

10:28:43.970 - CAPI20_PUT(021)
  0x0000  01 00 82 80  00 00 01 01  00 00 08 01  00 01 96 35
...............5
  0x0010  61 33 00                                            a3.
  ---
  CONNECT_B3 REQ, AppID 0x0001, MsgNr 0x0000
    PLCI: 0x00000101
    NCPI (0x8):
      D-Bit: on
      PVC group number: 0x0
      PVC number: 0x1
      Bytes following id field (0x4): 96 35 61 33  

10:28:43.970 - N-RESET REQ
10:28:43.970 - D-X(003) 40 03 7F
10:28:43.970 - CAPI20_GET(014)
  0x0000  01 00 82 81  00 00 01 01  01 00 00 00              
............
  ---
  CONNECT_B3 CONF, AppID 0x0001, MsgNr 0x0000
    NCCI: 0x00010101
    Info: initiated

10:28:43.970 - CAPI20_GET(013)
  0x0000  01 00 83 82  01 00 01 01  01 00 00                
...........
  ---
  CONNECT_B3_ACTIVE IND, AppID 0x0001, MsgNr 0x0001
    NCCI: 0x00010101
    NCPI (0x0):

10:28:43.972 - CAPI20_PUT(012)
  0x0000  01 00 83 83  00 00 01 01  01 00                    
..........
  ---
  CONNECT_B3_ACTIVE RESP, AppID 0x0001, MsgNr 0x0000
    NCCI: 0x00010101

10:28:43.984 - D-R(003) 40 03 73
10:28:43.984 - D-X(009) 40 03 00 00 10 00 FB 00 00
10:28:44.004 - D-R(004) 40 03 01 02
10:28:44.020 - D-R(009) 42 03 00 02 10 00 FB 07 95
10:28:44.020 - D-X(004) 42 03 01 02
10:28:44.105 - D-R(008) FE FF 03 0F 00 00 04 FF
10:28:44.105 - D-X(008) FC FF 03 0F 7A 33 05 03
--
10:28:54.014 - D-X(004) 40 03 01 03
10:28:54.022 - D-R(004) 42 03 01 03
10:28:54.022 - D-X(004) 42 03 01 03
10:28:54.031 - D-R(004) 40 03 01 03
--
10:29:04.012 - D-X(004) 40 03 01 03
10:29:04.025 - D-R(004) 40 03 01 03
10:29:04.039 - D-R(004) 42 03 01 03
10:29:04.039 - D-X(004) 42 03 01 03
10:29:09.162 - CAPI20_PUT(022)
  0x0000  01 00 86 80  00 00 01 01  01 00 00 4C  F0 DE 05 00
...........Lp^..
  0x0010  00 00 00 00                                         ....
  ---

    As you can see the NCPI struct is coded as follow:
NCPI (0x8):
      D-Bit: on
      PVC group number: 0x0
      PVC number: 0x1
      Bytes following id field (0x4): 96 35 61 33  //number called

  I called the (1) 96 35 61 33
  The problem is that I have always a connection with any called
number I enter; I must have a problem somewhere.In fact the connection
looks like to be done but I don't think that I called the  good number
( after I have no reception with the called number but apparently I
can send data( but where ???).)

      My questions are:

1/ where should I place the called numder when I make a transmission
over D channel and is the NCPI struct well coded?

2/ In france we have a prefix( number 1) for D channel number, should
I put it with the rest of the number called or no?

                                                 Thank

                                              Guillaume Terrien

 
 
 

called number in D channel transmission

Post by Hans-Jürgen Ortman » Wed, 06 Aug 2003 23:40:24


Guillaume,

Quote:> 1/ where should I place the called numder when I make a transmission
> over D channel and is the NCPI struct well coded?

you must fill in the NCPI struct - the CONNECT_REQ->CalledPartyNumber is
ignored in case of X.31 vie the D channel.

Quote:> 2/ In france we have a prefix( number 1) for D channel number, should
> I put it with the rest of the number called or no?

that's a question, you have to ask your telco - in Germany every X.25
network has an own prefix, and you have to dial this 25 prefix, so that the
called X.25 network knows, which X.25 network you want to adress. I assume
the same could be valid in France, but I don't know. Specially the '1' seems
to be very short for this kind of prefix - but in your country a lot of
things are different ;)
In my (very old) books I found for France the prefixes 2081 for NTI network
and 2080 for Transpac...

If you get a CONNECT_B3_ACTIVE_IND for every number, you're dialing, your
controller is doing something wrong, or your network is very strange. In
this case a X.25 trace would be helpful. In your case you didn't offer
enough information - all we can see, is that a RESTART REQ collision occured
(both parties are sending a RESTART REQ), but there's no CALL REQ at all ?!

HansJuergen

Quote:> 10:28:43.984 - D-R(003) 40 03 73
> 10:28:43.984 - D-X(009) 40 03 00 00 10 00 FB 00 00  <--- RESTART REQ
> 10:28:44.004 - D-R(004) 40 03 01 02
> 10:28:44.020 - D-R(009) 42 03 00 02 10 00 FB 07 95 <--- RESTART REQ
> 10:28:44.020 - D-X(004) 42 03 01 02
> 10:28:44.105 - D-R(008) FE FF 03 0F 00 00 04 FF <--- 'normal' ISDN traffic
> 10:28:44.105 - D-X(008) FC FF 03 0F 7A 33 05 03 <---'normal' ISDN traffic
> --
> 10:28:54.014 - D-X(004) 40 03 01 03
> 10:28:54.022 - D-R(004) 42 03 01 03
> 10:28:54.022 - D-X(004) 42 03 01 03
> 10:28:54.031 - D-R(004) 40 03 01 03
> --
> 10:29:04.012 - D-X(004) 40 03 01 03
> 10:29:04.025 - D-R(004) 40 03 01 03
> 10:29:04.039 - D-R(004) 42 03 01 03
> 10:29:04.039 - D-X(004) 42 03 01 03


 
 
 

called number in D channel transmission

Post by GTERRI » Sat, 09 Aug 2003 00:17:10


I am sorry but I can't take a X25 frame, because I use a passive card
and the only "frame" I have is the one of DITRACE, and moreover I
haven't a line analyser for the moment.

1/How can I decode the messages as Hans-Juergen?

Quote:> 10:28:43.984 - D-R(003) 40 03 73
> 10:28:43.984 - D-X(009) 40 03 00 00 10 00 FB 00 00  <--- RESTART REQ
> 10:28:44.004 - D-R(004) 40 03 01 02
> 10:28:44.020 - D-R(009) 42 03 00 02 10 00 FB 07 95 <--- RESTART REQ
> 10:28:44.020 - D-X(004) 42 03 01 02
> 10:28:44.105 - D-R(008) FE FF 03 0F 00 00 04 FF <--- 'normal' ISDN traffic
> 10:28:44.105 - D-X(008) FC FF 03 0F 7A 33 05 03 <---'normal' ISDN traffic
> --

2/  In fact I have some probems withe the NCPI struct and the
connect_b3_req; I really think that it is the source of my problem.

     I configured the NCPI for B3 in protocol 2 (DTE-DTE);As I want to
send data over D channel, I code The Ncpi struct as follow:
I put the flag to 1(D bit on), group and channel to 1 ( for
permanentVC) and finally I have to configure the content.
        I have just put the called number in it, but should I place
the source number and with which format? I have seen some examples
where Facility length and user data were too configured, is it
necessary ?(in the CAPI doc there is nothing about it).
Please can you tell me how can I code the connect_b3_req and
particulary the NCPI struct.

This is how I coded the connect_b3_req (the number I call is 96 35 61
33)

case (_CONNECT_B3_R):   // CONNECT_B3_REQ                                                                      
//Length
      CAPIMsg.info.connect_b3_req.structs[bCount++] = 7;
//flag
      CAPIMsg.info.connect_b3_req.structs[bCount++] = 1;
 //channel group number
      CAPIMsg.info.connect_b3_req.structs[bCount++] = 1;
 //Channel      number
     CAPIMsg.info.connect_b3_req.structs[bCount++] = 1;
//Content                                                                                                              
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;             //51

CAPIMsg.header.length = CAPIMSG_HEADER_LEN + bCount; // Header +
CONNECT_B3_REQ

                                   Thank you very much.

                                     Guillaume Terrien

 
 
 

called number in D channel transmission

Post by Hans-Jürgen Ortman » Fri, 15 Aug 2003 18:44:29




Quote:> I am sorry but I can't take a X25 frame, because I use a passive card
> and the only "frame" I have is the one of DITRACE, and moreover I
> haven't a line analyser for the moment.

> 1/How can I decode the messages as Hans-Juergen?

only manually, i.e. reading the X.25 specification and analysing (decoding)
the contents of the octets ;)

Quote:> I configured the NCPI for B3 in protocol 2 (DTE-DTE);As I want to
> send data over D channel, I code The Ncpi struct as follow:
> I put the flag to 1(D bit on), group and channel to 1 ( for
> permanentVC) and finally I have to configure the content.
> I have just put the called number in it, but should I place
> the source number and with which format?

I can't follow: if you're using a PVC, you don't need any number - the used
TEI defines, to which DTE the network will route this data. In this case
it's ok, that you always receive a CONNECT_B3_ACTIVE_IND (a pvc is not
circuit switched, it's a kind of 'leased line' iside the X.31 network). If
you don't use pVC, you have to code the numbers according to the X.25 spec
(see there)

Quote:> I have seen some examples
> where Facility length and user data were too configured, is it
> necessary ?(in the CAPI doc there is nothing about it).

That's not part of CAPI, but of X.25. Therfore you'll find information
there. If it's nesseccarry, depends on the network and subscription time
parameters. If you're using the right CAPI_RELEASE parameters, the
negotiation(!) of packet- und windosize is done without filling this values,
but you always have to interpret the answers of the network (at least for
the packet size)

So you will not succeed without detailled X.25 KnowHow...

HansJuergen

 
 
 

1. Need to take an ISDN/INS-1500 channel out of service

I was hoping someone here could help me out. I have a couple of
INS-1500 spans sitting in Tokyo. Calling the number will result
in hunting according to some hunt algorithm. What I'm trying to find
out is what steps need to be taken to cause an incoming call to hunt
past a particular channel and cause the call in question to be
presented to the 'next' channel.

We are using a Dialogic PRI-211 card. The API that comes with that
card has a function called pr_setmaint which ostensibly allows us to
rtansition the maintenance state between IN SERVICE, OUT OF SERVICE,
and MAINTENANCE state. It does not work and now I'm left with reading
the CCITT specs to find what in the protocol supports this type of
functionality.

Any help would be greatly appreciated. Please email and I will
summarize as needed.

Many thanks in advance.

--
----------Time flies like the wind. Fruit flies like bananas.------------------

----------Everybody repeat after me: "We are all individuals."-----------------

2. virushoax, jdbgmgr.exe, deleted in error

3. Inbound ISDN calls and Calling Number/Redirecting number information

4. T4000 ('386) vs. Compaq DP 386/16

5. Setting Number of Rings for Dial Ins

6. command line recall

7. Dumping an ISDN B channel when incoming call detected on D channel

8. osp.zip

9. CONFERENCE CALL BARGE-INS

10. ** Single Number or Separate Channel Numbering? **

11. speed of transmission, channel bandwidth, modulation

12. speed of transmission, channel bandwidth and modulation

13. logical disconnection during D channel transmission