Very Computer

cause code 57 is describe  below

Cause No. 57 - bearer capability not authorized [Q.850]

                   This cause indicates that the user has requested a bearer
capability which
                   is implemented by the equipment which generated this
cause but the user is
                   not authorized to use.

first questions;

Looking at the debug,  your dialing  a  different number on the second call,
Is the SB using the  same line ? If so did you call the successful number
and see what you get.

I don't know what you have in your Isdn conf but that a look at the B
channels configure for  56 or 64kbps .

on the good call you are pick up the  channel and rate

    19:48:15 [isdn] l4_in: sending l4_conn_co, number 7033214887 rate 64
     channel_id 1, fd 6, des_call_apear 0

on the call that is drop,  the D -channel never setup the call on the   B
chnnl

   19:41:43 [isdn] l4_snd: called_number 3013204821 nai 0 conn_id 0

It look like the switch  immediately  release the setup and kick back a
error ( cause code 57 )

FYI. I ran across the same code and cause code 58  with a Ascend pipeline,
Ameritech had provision my line for  voice capability only, so If I tried a
data call at 56 or 64 kbps it was immediately drop. I tested the line with a
ISDN test set and was able to place the call as a voice call no problem. So
if this is a new line you might what to ask your  carrier. It look like your
dialing east coast east VA, and MD so I'm assuming Bell Atlantic.  Good
luck!

Quote:> Anyone had any luck in getting SunISD 1.0.4 working on the
> SparcBook?  Heck, any version...

yes,  I did a sparc 5 with sbus DBRI call, whent kinda okay.

Quote:

> I just moved the config over from my S10, and had no joy.
> Even tried using the S10's connection instead of just adding
> the SB to the bus.

> D Channel came up OK, SPID was OK'd by the switch (a 5ess,
> national), but all calls are immediately hung up with a
> cause code of 57 (decimal).  Same result when the S10 calls the SB.

> I've added a succesful and unsuccessful call from the SB and the S10.
> I don't see any diffs up to the point of the failed call.

> Wild a** guesses appreciated as well.

> Thanks,
> -sam

> Here is the log from a failed call from the SB:

> 19:41:43   [pppd] process_ifppp_msg: ctl.len 28 dat.len 84 message 101
> 19:41:43   [pppd] process_ifppp_msg: CONNECTION REQUEST, ifppp0 needs
> connection
> 19:41:43   [pppd] process_ifppp_msg: ip_spoofing is 0
> 19:41:43   [pppd] outgoing_call:  p 4bc30 linkid 0 mode 0
> 19:41:43 [isdn] accept_fifo_connection handle 0x10001 fds 0
> 19:41:43 [isdn] accept_fifo_connection recvfd.fd 5
> 19:41:43   [pppd] Sending isdn_conn_rq address 3013204821 cc_nai -1
> service D channel_group
> ing  1 overlap_sending 0 fd 10
> 19:41:43 [isdn] l4_ph_to_cc_nai: hit 1 found cc_nai_a 0, cc_nai_b -1
> associated to ph_nai 0
> 19:41:43 [isdn] found conn_id 0
> 19:41:43 [isdn] alloc_nai_and_connid: allocated conn_id 0, cc_nai 0
> based on ph_nai -1, pro
> file -1
> 19:41:43 [isdn] l4_snd: outgoing_call acu_mx_sz_called_nb 32
> 19:41:43 [isdn] l4_snd: outgoing_call Acu_conn_rq_ph_num_size 10
> 19:41:43 [isdn] l4_snd: outgoing_call call_appear =239
> 19:41:43 [isdn] l4_snd: outgoing_call context =19a490 conn_args 84
> buffer_data_size 98
> 19:41:43 [isdn] l4_snd: called_number 3013204821 nai 0 conn_id 0
> 19:41:43 [isdn] l4_snd: data_size 98 0 data_offset 36
> 19:41:43 [isdn] [state=outgoing] ACU_CONN_RQ-> nai 0 conn_id 0
> 19:41:44 [isdn] l4_rcv: received msg 64 cp 19a490 nai 0 conn_id 0
> 19:41:44 [isdn] Warning: [state=outgoing] <-ACU_CLEAR_CO nai 0 conn_id 0
> [releasing context
>  cp 19a490]
> 19:41:44 [isdn] clear cause: 57 dec, 39 hex
> 19:41:44 [isdn] txt: unknown code 019:48:13
> 19:41:44 [isdn] cost: 0
> 19:41:44   [pppd] recv_fd: io present on pipe fd 10
> 19:41:44   [pppd] recv_fd: HANGUP detected
> 19:41:44   [pppd] recv_fd: call on call_handle 10 failed
> 19:41:44   [pppd] terminate_path: TERMINATED p 4bc30 state 0 linkid 0

> And here is a successful call/connection from the S10.

> 19:48:13   [pppd] process_ifppp_msg: ctl.len 28 dat.len 76 message 101
> 19:48:13   [pppd] process_ifppp_msg: CONNECTION REQUEST, ifppp0 needs
> connection
> 19:48:13   [pppd] process_ifppp_msg: ip_spoofing is 0
> 19:48:13   [pppd] outgoing_call:  p 4abc8 linkid 0 mode 0
> 19:48:13 [isdn] accept_fifo_connection handle 0x10001 fds 0
> 19:48:13 [isdn] accept_fifo_connection recvfd.fd 6
> 19:48:13   [pppd] Sending isdn_conn_rq address 7033214887 cc_nai -1
> service D channel_grouping  1 overlap_sending 0 fd 11
> 19:48:13 [isdn] l4_ph_to_cc_nai: hit 1 found cc_nai_a 0, cc_nai_b -1
> associated to ph_nai 0
> 19:48:13 [isdn] found conn_id 0
> 19:48:13 [isdn] alloc_nai_and_connid: allocated conn_id 0, cc_nai 0
> based on ph_nai -1, profile -1
> 19:48:13 [isdn] l4_snd: outgoing_call acu_mx_sz_called_nb 32
> 19:48:13 [isdn] l4_snd: outgoing_call Acu_conn_rq_ph_num_size 10
> 19:48:13 [isdn] l4_snd: outgoing_call call_appear =239
> 19:48:13 [isdn] l4_snd: outgoing_call context =19a2f0 conn_args 84
> buffer_data_size 98
> 19:48:13 [isdn] l4_snd: called_number 7033214887 nai 0 conn_id 0
> 19:48:13 [isdn] l4_snd: data_size 98 0 data_offset 36
> 19:48:13 [isdn] [state=outgoing] ACU_CONN_RQ-> nai 0 conn_id 0
> 19:48:14 [isdn] l4_rcv: received msg 66 cp 19a2f0 nai 0 conn_id 0
> 19:48:14 [isdn] [state=outgoing] <-ACU_PROGRESS_IN nai 0 conn_id 0,
> [ignored]
> 19:48:15 [isdn] l4_rcv:Acu_alert_in display_nb 0
> 19:48:15 [isdn] l4_rcv: received msg 65 cp 19a2f0 nai 0 conn_id 0
> 19:48:15 [isdn] [state=outgoing] <-ACU_ALERT_IN nai 0 conn_id 0,
> [ignored]
> 19:48:15 [isdn] l4_rcv:Acu_conn_co display_nb 0
> 19:48:15 [isdn] l4_rcv: received msg 62 cp 19a2f0 nai 0 conn_id 0
> 19:48:15 [isdn] [state=outgoing] <-ACU_CONN_CO nai 0 conn_id 0
> channel_id 1
> 19:48:15 [isdn] l4_b_init_open: Use 64k B channel...
> 19:48:15 [isdn] l4_in: sending l4_conn_co, number 7033214887 rate 64
> channel_id 1, fd 6, des_call_apear 0
> 19:48:15 [isdn] send_l4_conn_co: putmsg on pipe_fd 6 ret 0
> 19:48:15   [pppd] recv_fd: io present on pipe fd 11
> 19:48:15   [pppd] call_cfm: TO   7033214887 connected, b_fd 12 B 1 rate
> 64
> 19:48:15   [pppd] start_ppp: PPP starting p 4abc8 linkid 0  s c
> 19:48:15   [pppd] set_lcp_conf_options: p 4abc8 linkid 0
> 19:48:17   [pppd] add_to_bundle: connection_name [erols], interface
> ifppp0, link 0, timeout set for 90 seconds
> 19:48:17   [pppd] process_ifppp_msg: ctl.len 16 dat.len 532 message 114
> 19:48:17   [pppd] process_ifppp_msg: EVENT INDICATION, ifppp0 muxid -1
> 19:48:18   [pppd] process_ifppp_msg: ctl.len 16 dat.len 764 message 114
> 19:48:18   [pppd] process_ifppp_msg: EVENT INDICATION, ifppp0 muxid -1
> 19:48:18   [pppd] process_ppp_msg: Local IP [207.96.105.167], address
> negotiation SUCCEEDED
> 19:48:18   [pppd] process_ppp_msg: Remote IP [10.11.64.84], address
> negotiation SUCCEEDED

Anyone had any luck in getting SunISD 1.0.4 working on the
SparcBook?  Heck, any version...

I just moved the config over from my S10, and had no joy.
Even tried using the S10's connection instead of just adding
the SB to the bus.

D Channel came up OK, SPID was OK'd by the switch (a 5ess,
national), but all calls are immediately hung up with a
cause code of 57 (decimal).  Same result when the S10 calls the SB.

I've added a succesful and unsuccessful call from the SB and the S10.
I don't see any diffs up to the point of the failed call.

Wild a** guesses appreciated as well.

Thanks,
-sam

Here is the log from a failed call from the SB:

19:41:43   [pppd] process_ifppp_msg: ctl.len 28 dat.len 84 message 101
19:41:43   [pppd] process_ifppp_msg: CONNECTION REQUEST, ifppp0 needs
connection
19:41:43   [pppd] process_ifppp_msg: ip_spoofing is 0
19:41:43   [pppd] outgoing_call:  p 4bc30 linkid 0 mode 0
19:41:43 [isdn] accept_fifo_connection handle 0x10001 fds 0
19:41:43 [isdn] accept_fifo_connection recvfd.fd 5
19:41:43   [pppd] Sending isdn_conn_rq address 3013204821 cc_nai -1
service D channel_group
ing  1 overlap_sending 0 fd 10
19:41:43 [isdn] l4_ph_to_cc_nai: hit 1 found cc_nai_a 0, cc_nai_b -1
associated to ph_nai 0
19:41:43 [isdn] found conn_id 0
19:41:43 [isdn] alloc_nai_and_connid: allocated conn_id 0, cc_nai 0
based on ph_nai -1, pro
file -1
19:41:43 [isdn] l4_snd: outgoing_call acu_mx_sz_called_nb 32
19:41:43 [isdn] l4_snd: outgoing_call Acu_conn_rq_ph_num_size 10
19:41:43 [isdn] l4_snd: outgoing_call call_appear =239
19:41:43 [isdn] l4_snd: outgoing_call context =19a490 conn_args 84
buffer_data_size 98
19:41:43 [isdn] l4_snd: called_number 3013204821 nai 0 conn_id 0
19:41:43 [isdn] l4_snd: data_size 98 0 data_offset 36
19:41:43 [isdn] [state=outgoing] ACU_CONN_RQ-> nai 0 conn_id 0
19:41:44 [isdn] l4_rcv: received msg 64 cp 19a490 nai 0 conn_id 0
19:41:44 [isdn] Warning: [state=outgoing] <-ACU_CLEAR_CO nai 0 conn_id 0
[releasing context
 cp 19a490]
19:41:44 [isdn] clear cause: 57 dec, 39 hex
19:41:44 [isdn] txt: unknown code 019:48:13  
19:41:44 [isdn] cost: 0
19:41:44   [pppd] recv_fd: io present on pipe fd 10
19:41:44   [pppd] recv_fd: HANGUP detected
19:41:44   [pppd] recv_fd: call on call_handle 10 failed
19:41:44   [pppd] terminate_path: TERMINATED p 4bc30 state 0 linkid 0

And here is a successful call/connection from the S10.

19:48:13   [pppd] process_ifppp_msg: ctl.len 28 dat.len 76 message 101
19:48:13   [pppd] process_ifppp_msg: CONNECTION REQUEST, ifppp0 needs
connection
19:48:13   [pppd] process_ifppp_msg: ip_spoofing is 0
19:48:13   [pppd] outgoing_call:  p 4abc8 linkid 0 mode 0
19:48:13 [isdn] accept_fifo_connection handle 0x10001 fds 0
19:48:13 [isdn] accept_fifo_connection recvfd.fd 6
19:48:13   [pppd] Sending isdn_conn_rq address 7033214887 cc_nai -1
service D channel_grouping  1 overlap_sending 0 fd 11
19:48:13 [isdn] l4_ph_to_cc_nai: hit 1 found cc_nai_a 0, cc_nai_b -1
associated to ph_nai 0
19:48:13 [isdn] found conn_id 0
19:48:13 [isdn] alloc_nai_and_connid: allocated conn_id 0, cc_nai 0
based on ph_nai -1, profile -1
19:48:13 [isdn] l4_snd: outgoing_call acu_mx_sz_called_nb 32
19:48:13 [isdn] l4_snd: outgoing_call Acu_conn_rq_ph_num_size 10
19:48:13 [isdn] l4_snd: outgoing_call call_appear =239
19:48:13 [isdn] l4_snd: outgoing_call context =19a2f0 conn_args 84
buffer_data_size 98
19:48:13 [isdn] l4_snd: called_number 7033214887 nai 0 conn_id 0
19:48:13 [isdn] l4_snd: data_size 98 0 data_offset 36
19:48:13 [isdn] [state=outgoing] ACU_CONN_RQ-> nai 0 conn_id 0
19:48:14 [isdn] l4_rcv: received msg 66 cp 19a2f0 nai 0 conn_id 0
19:48:14 [isdn] [state=outgoing] <-ACU_PROGRESS_IN nai 0 conn_id 0,
[ignored]
19:48:15 [isdn] l4_rcv:Acu_alert_in display_nb 0
19:48:15 [isdn] l4_rcv: received msg 65 cp 19a2f0 nai 0 conn_id 0
19:48:15 [isdn] [state=outgoing] <-ACU_ALERT_IN nai 0 conn_id 0,
[ignored]
19:48:15 [isdn] l4_rcv:Acu_conn_co display_nb 0
19:48:15 [isdn] l4_rcv: received msg 62 cp 19a2f0 nai 0 conn_id 0
19:48:15 [isdn] [state=outgoing] <-ACU_CONN_CO nai 0 conn_id 0
channel_id 1
19:48:15 [isdn] l4_b_init_open: Use 64k B channel...
19:48:15 [isdn] l4_in: sending l4_conn_co, number 7033214887 rate 64
channel_id 1, fd 6, des_call_apear 0
19:48:15 [isdn] send_l4_conn_co: putmsg on pipe_fd 6 ret 0
19:48:15   [pppd] recv_fd: io present on pipe fd 11
19:48:15   [pppd] call_cfm: TO   7033214887 connected, b_fd 12 B 1 rate
64
19:48:15   [pppd] start_ppp: PPP starting p 4abc8 linkid 0  s c
19:48:15   [pppd] set_lcp_conf_options: p 4abc8 linkid 0
19:48:17   [pppd] add_to_bundle: connection_name [erols], interface
ifppp0, link 0, timeout set for 90 seconds
19:48:17   [pppd] process_ifppp_msg: ctl.len 16 dat.len 532 message 114
19:48:17   [pppd] process_ifppp_msg: EVENT INDICATION, ifppp0 muxid -1
19:48:18   [pppd] process_ifppp_msg: ctl.len 16 dat.len 764 message 114
19:48:18   [pppd] process_ifppp_msg: EVENT INDICATION, ifppp0 muxid -1
19:48:18   [pppd] process_ppp_msg: Local IP [207.96.105.167], address
negotiation SUCCEEDED
19:48:18   [pppd] process_ppp_msg: Remote IP [10.11.64.84], address
negotiation SUCCEEDED

hi

where do you find the descriptions of all the codes ?
any url ?

--
best regards from vienna           |   mayer (at) unisys.co.at_SPAM
hans                               |   mayer (at) relay.bfl.at_SPAM

You might find them in the chapter on layer 3 signalling at

    http://veda-home.com/Blackshaw2

at least I think I listed the lot.

Bob

--
"Since when was genius found respectable?"
                         E. B. Browning

Yep, calls to my ISP ended the same as calls to the S10 from the SB3.

Quote:

> I don't know what you have in your Isdn conf but that a look at the B
> channels configure for  56 or 64kbps .

I copied the working config from my S10; changed the numbers to the
other
SPID, and booted.

When that didn't work, I just moved the wire from the S10 over to the
SB3
and re-copied the working config to see if I could just clone the S10.

Quote:> It look like the switch  immediately  release the setup and kick back a
> error ( cause code 57 )

> FYI. I ran across the same code and cause code 58  with a Ascend pipeline,
> Ameritech had provision my line for  voice capability only, so If I tried a
> data call at 56 or 64 kbps it was immediately drop. I tested the line with a
> ISDN test set and was able to place the call as a voice call no problem. So
> if this is a new line you might what to ask your  carrier. It look like your
> dialing east coast east VA, and MD so I'm assuming Bell Atlantic.  Good
> luck!

What?!?!  Ask Bell Atl for help?!?!?!  :)  Fortunately, this is a
(relatively)
stable extant line.  I don't think I have the guts to try the SB3 with a
new
line given my experience with the S10 (which works like a champ!)

Thanks a bunch,
-sam

:> first questions;
:>
:> Looking at the debug,  your dialing  a  different number on the second call,
:> Is the SB using the  same line ? If so did you call the successful number
:> and see what you get.

: Yep, calls to my ISP ended the same as calls to the S10 from the SB3.

:>
:> I don't know what you have in your Isdn conf but that a look at the B
:> channels configure for  56 or 64kbps .
:>
: I copied the working config from my S10; changed the numbers to the
: other
: SPID, and booted.

: When that didn't work, I just moved the wire from the S10 over to the
: SB3
: and re-copied the working config to see if I could just clone the S10.

I too thought the SB3 could be swapped for the S10 (same line/DN) and
that would point you to your problem.

In any case I am including my configuration files below in hope they
might be of help --- SB3 running 2.5.1 and SB3GX running 2.6 ---

You might also think about using the isdntool to reconfigure the SB3
as multiple files are being edited under
"/etc/opt/SUNWisdn"
"/etc/opt/SUNWisdn/ppp"
"/etc/opt/SUNWisdn/te"

----------   isppp.cf   ---------------
#================================================================
#      This file is automatically generated by isdntool.        =
#      Please don't edit this manually                          =
#================================================================
#
version 1              
#
use_caller_id   on      
#
ifconfig ifppp0 plumb 208.XXX.XXX.XXX 204.XXX.XXX.XXX netmask + up
isdn_path                       # BTG
#----------------------------------------------------------------
# IP Interface
#----------------------------------------------------------------
        name                     BTG
        interface                ifppp0
        ip_spoofing              on
        default_route
#----------------------------------------------------------------
# Connection
#----------------------------------------------------------------
        lcp_encapsulation        PPP
        ipcp_compression         vj
        bandwidth_controller     off
        inactivity_timeout       120
#----------------------------------------------------------------
# Callback
#----------------------------------------------------------------
        hunt_mode                off
        negotiate_address        off
#----------------------------------------------------------------
# Security
#----------------------------------------------------------------
        will_do_authentication   chap
        require_authentication   off
        chap_name                xxxxxxx
        chap_secret              xxxxxxx
#----------------------------------------------------------------
# Phones
#----------------------------------------------------------------
        called_number 343XXXX              1 any    A    data64 #
#----------------------------------------------------------------
# Advanced Options
#----------------------------------------------------------------
#   LCP
        restart_timer            1000
        max_restarts             10
        lcp_mru                  1500
#   Misc.
        network                  nil
#----------------------------------------------------------------
# Routes
#----------------------------------------------------------------
route add net 204.XXX.XXX.0 208.XXX.XXX.XXX 0
#
#       End of BTG
----------   end of isppp.cf   ---------------

----------   isdn.cf   ---------------
#
# SunISDN 1.0.4 ISDN configuration file
#
#      /etc/opt/SUNWisdn/te/0
#
#================================================================
#      This ISDN file is automatically generated by isdntool.   =
#      Please don't edit this manually.                         =
#================================================================
#
#----------------------------------------------------------------
# ISDN configuration
#----------------------------------------------------------------
#
isdn_config
#
#----------------------------------------------------------------
# Call Control parameters
#----------------------------------------------------------------
#
cc_config
#
#----------------------------------------------------------------
# PROFILE A
#----------------------------------------------------------------
#
cc_profile              A
cc_na_country           usa
cc_na_operator          5ess
cc_calling_nb           212XXXXXXX
cc_force56              off
cc_cli                  off
#
#----------------------------------------------------------------
# Network Signalling parameters (Q.931)
#----------------------------------------------------------------
#
ns_config
ns_profile              A
ns_spid                 212XXXXXXX0000
#
#----------------------------------------------------------------
# Data Link Parameters (Q.921/LAPD)
#----------------------------------------------------------------
#
dl_config
dl_tei_time_assignment  DL_TEI_TIME_ASSIGN_USA
dl_tei_time_removal     DL_TEI_TIME_REMOVAL_USA
#
#----------------------------------------------------------------
# dl_sapi: SAP identifier
#----------------------------------------------------------------
#
dl_sapi                 0
dl_dlcep_nb             2
dl_rc_nb                1000
dl_sapi                 63
dl_dlcep_nb             2
dl_rc_nb                1000
#
#----------------------------------------------------------------
# Physical layer parameters
#----------------------------------------------------------------
#
ph_config
#
----------   end of isdn.cf   ---------------

Good luck

Patrick Arnoux

I actually tried that, but half heartedly, as I was convinced it
wouldn't
matter.  Knowing that you were able to do it without extras from Tadpole
is a great help.

 [Config files snipped]

Quote:> Good luck

> Patrick Arnoux

Thanks so much!

I'll give it a try and report back.

Regards,
-sam

Yippee!  The encouragement to try again is what I needed.  It works
peachily now!

Thinking I must have fat fingered something, I save the hand-edited
files to compare with the tool created ones.  Interesting diffs:

isppp.cf:
8c8
< use_caller_id         on      
---

Quote:> use_caller_id         off      

16c16
<       ip_spoofing              on
---

Quote:>       ip_spoofing              off

I don't really believe either of these made a diff, as I have
changed them on the S10.  But perhaps....  

There were no diffs in the te/0 file between what I had hand edited and
what the tool generated.

The only other thing that I can think of is that I didn't sufficiently
stop the processes on the S10 when I tried before.  

Ah well, gotta love them heisenbugs!

-sam

:>
:> >
:> > You might also think about using the isdntool to reconfigure the SB3
:>
:> I'll give it a try and report back.
:>

: Yippee!  The encouragement to try again is what I needed.  It works
: peachily now!

Congrats !!

The SB3 is such a neat box innit?!

Now if only I could find a way to access the voice features of the
ISDN line with it, that would really give me that warm fuzzy feeling.
(Sorry I coul'nt resist the pun).

I seem to recall in one of your previous post you mentionned a fellow
using his Sun/ISDN with TAM software, anything ever come of that?
Sun wants mucho bucks for that XTL library but all I really want is
the interface definition to the ISDN driver. If any such information
were to come your way, please give a holler.

Patrick Arnoux

(sorry about that, just remove the "_h8spam" to use this address)

David Evans wrote me recently and said:

Hmmm...  Yeah, we were doing that back in '89 with the original
ISDN design on the SS1 (not SS10).  It is quite possible to do the
above with the Teleservices API. If I recall correctly it is even a
demo-app.

:>
: David Evans wrote me recently and said:

: Hmmm...  Yeah, we were doing that back in '89 with the original
: ISDN design on the SS1 (not SS10).  It is quite possible to do the
: above with the Teleservices API. If I recall correctly it is even a
: demo-app.

You would'nt happen to know the whereabout of said demo-app by chance ??

Patrick

I can't find it right off hand, but someone wanted to know about the
ability of SunISDN to receive calls.  I just spent some time with my
SparcBook3 and my S10 to no avail.

I need to do this as well, so I will continue looking into this.  If
I get anywhere, I'll post back.

-sam

Got it working!

I just posted the details under the subj:

                 SunISDN1.04 on a SS10 as a RAS : receive call ONLY

which was how the original poster that I had recalled
had noted their query.

-sam