If the PRI in question has been handling nothing but modem calls, it may not be provisioned properly to accept data calls. I don't know the specifics, but we had the opposite problem when we first installed digital modems -- the BRI circuits had to be re-provisioned to allow voice calls. Hope this helps, Richard Tabor Cargill Turkey Products rtabor at rocco.com > -----Original Message----- > From: owner-ascend-users-digest at max.bungi.com > [mailto:owner-ascend-users-digest at max.bungi.com] > Sent: Thursday, September 20, 2001 1:45 AM > To: ascend-users-digest at max.bungi.com > Subject: ascend-users-digest V96 #2377 > > > > ascend-users-digest Wednesday, 19 September 19101 Volume > 96 : Number 2377 > > In this issue: > > (ASCEND) TNT routing double hop ? > (ASCEND) cause code 88 incompatible destination > > ---------------------------------------------------------------------- > > From: ISPstuff <tom at ispstuff.com> > Date: Wed, 19 Sep 2001 09:02:34 -0500 > Subject: (ASCEND) TNT routing double hop ? > > When connected with any client machine to our new Max TNT, > traceroute shows > the first two hops as the TNT address (209.101.122.1) then > the next hop is > the gateway (our core router at 209.101.122.253). Everything > works fine. I > am just trying to remove the double hop at the start. Any ideas? > > A sample route statement follows. We are using static > routing. (note: real > IP addresses have been masked but are still accurate as an example.) > > > admin> netstat -r > Destination Gateway IF Flg Pref Met Use > Age > 0.0.0.0/0 209.101.122.253 ie0 SG 60 1 58392 > 11737 > 209.101.122.0/24 - ie0 C 0 0 6864 > 11737 > 209.101.122.0/24 209.101.122.12 wan176 *rGTM 60 > 1 0 > 193 > 209.101.122.0/24 209.101.122.10 wan161 *rGTM 60 > 1 0 > 661 > 209.101.122.0/24 209.101.122.33 wan140 *rGTM 60 > 1 0 > 1499 > 209.101.122.0/24 209.101.122.16 wan94 *rGTM 60 > 1 0 > 4114 > 209.101.122.0/24 209.101.122.24 wan44 *rGTM 60 > 1 0 > 7488 > 209.101.122.0/24 209.101.122.28 wan21 *rGTM 60 > 1 0 > 10665 > 209.101.122.0/24 209.101.122.253 ie0 *SG 60 > 8 0 > 11737 > 209.101.122.1/32 - local CP 0 0 5007 > 11737 > 209.101.122.10/32 209.101.122.10 wan161 rT 60 > 1 45 > 661 > 209.101.122.12/32 209.101.122.12 wan176 rT 60 > 1 55 > 193 > 209.101.122.16/32 209.101.122.16 wan94 rT 60 > 1 13821 > 4114 > 209.101.122.24/32 209.101.122.24 wan44 rT 60 > 1 34055 > 7488 > 209.101.122.28/32 209.101.122.28 wan21 rT 60 > 1 18620 > 10665 > 209.101.122.33/32 209.101.122.33 wan140 rT 60 > 1 1760 > 1499 > 209.101.122.64/26 - bh0 SP 254 15 16769 > 11737 > 209.101.122.64/32 209.101.122.64 wan10 rT 60 > 1 9242 > 11633 > 209.101.122.65/32 209.101.122.65 wan127 rT 60 > 1 1529 > 2360 > 209.101.122.69/32 209.101.122.69 wan15 rT 60 > 1 10370 > 11554 > 209.101.122.71/32 209.101.122.71 wan17 rT 60 > 1 7913 > 11501 > 209.101.122.72/32 209.101.122.72 wan134 rT 60 > 1 4365 > 1891 > 209.101.122.73/32 209.101.122.73 wan19 rT 60 > 1 4191 > 11300 > 209.101.122.75/32 209.101.122.75 wan137 rT 60 > 1 4047 > 1711 > 209.101.122.77/32 209.101.122.77 wan139 rT 60 > 1 1528 > 1590 > 209.101.122.81/32 209.101.122.81 wan144 rT 60 > 1 1353 > 1364 > 209.101.122.83/32 209.101.122.83 wan146 rT 60 > 1 1310 > 1209 > 209.101.122.86/32 209.101.122.86 wan150 rT 60 > 1 1514 > 936 > 209.101.122.89/32 209.101.122.89 wan43 rT 60 > 1 1769 > 7508 > 209.101.122.90/32 209.101.122.90 wan154 rT 60 > 1 3652 > 810 > 209.101.122.92/32 209.101.122.92 wan156 rT 60 > 1 2205 > 775 > 209.101.122.93/32 209.101.122.93 wan157 rT 60 > 1 1178 > 735 > 209.101.122.95/32 209.101.122.95 wan160 rT 60 > 1 1725 > 662 > 209.101.122.96/32 209.101.122.96 wan162 rT 60 > 1 4598 > 617 > 209.101.122.99/32 209.101.122.99 wan165 rT 60 > 1 7966 > 412 > 209.101.122.100/32 209.101.122.100 wan166 rT 60 > 1 2248 > 411 > 209.101.122.101/32 209.101.122.101 wan167 rT 60 > 1 765 > 383 > 209.101.122.102/32 209.101.122.102 wan168 rT 60 > 1 2024 > 368 > 209.101.122.103/32 209.101.122.103 wan169 rT 60 > 1 1360 > 345 > 209.101.122.104/32 209.101.122.104 wan170 rT 60 > 1 296 > 332 > 209.101.122.105/32 209.101.122.105 wan171 rT 60 > 1 2329 > 302 > 209.101.122.106/32 209.101.122.106 wan172 rT 60 > 1 1803 > 294 > 209.101.122.107/32 209.101.122.107 wan173 rT 60 > 1 187 > 288 > 209.101.122.108/32 209.101.122.108 wan174 rT 60 > 1 1953 > 209 > 209.101.122.109/32 209.101.122.109 wan175 rT 60 > 1 1810 > 202 > 209.101.122.112/32 209.101.122.112 wan179 rT 60 > 1 13 > 101 > 209.101.122.113/32 209.101.122.113 wan180 rT 60 > 1 3 > 41 > 209.101.122.114/32 209.101.122.114 wan181 rT 60 > 1 0 > 0 > 209.101.122.115/32 209.101.122.115 wan75 rT 60 > 1 2366 > 5030 > 209.101.122.117/32 209.101.122.117 wan77 rT 60 > 1 14492 > 4970 > 209.101.122.128/28 - bh0 SP 254 15 4070 > 11737 > 209.101.122.129/32 209.101.122.129 wan91 rT 60 > 1 2579 > 4219 > 209.101.122.132/32 209.101.122.132 wan96 rT 60 > 1 40586 > 4097 > 209.101.122.135/32 209.101.122.135 wan99 rT 60 > 1 45497 > 3993 > 209.101.122.143/32 209.101.122.143 wan109 rT 60 > 1 263 > 3561 > 209.101.122.144/29 - bh0 SP 254 15 2354 > 11737 > 209.101.122.150/32 209.101.122.150 wan117 rT 60 > 1 2631 > 3096 > 209.101.122.152/30 - bh0 SP 254 15 1090 > 11737 > 209.101.122.156/31 - bh0 SP 254 15 1668 > 11737 > 127.0.0.0/8 - bh0 CP 0 0 0 > 11737 > 127.0.0.1/32 - local CP 0 0 0 > 11737 > 127.0.0.2/32 - rj0 CP 0 0 0 > 11737 > 224.0.0.0/4 - mcast CP 0 0 9 > 11737 > 224.0.0.1/32 - local CP 0 0 0 > 11737 > 224.0.0.2/32 - local CP 0 0 136 > 11737 > 224.0.0.9/32 - local CP 0 0 0 > 11737 > 255.255.255.255/32 - ie0 CP 0 0 273 > 11737 > Total Routes = 67 Hidden Routes = 7 > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to > ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > > ------------------------------ > > From: Carl Espe <cespe at planeteria.net> > Date: Wed, 19 Sep 2001 10:33:34 -0700 > Subject: (ASCEND) cause code 88 incompatible destination > > I am trying to configure a max 4000 to accept isdn calls from a > pipeline 50. The max has one PRI and has handled modem calls for > years without trouble. But when I try to connect with the pipeline > 50, I get an error cause code 88 - incompatible destination. The max > doesn't show anything at all in the console display -- it doesn't > even look like the call got to it. > > I know the pipeline is configured correctly because it can connect > just fine to another max we have. > > Max 4000 > 7.0.22 > ftk.m40 > > TIA, > Carl Espe > ++ Ascend Users Mailing List ++ > To unsubscribe: send unsubscribe to > ascend-users-request at bungi.com > Archives: http://www.nexial.com/mailinglists/ > > ------------------------------ > > End of ascend-users-digest V96 #2377 > ************************************ > > ++ Ascend Users Mailing List Digest++ > To unsubscribe: > "echo unsubscribe | mail ascend-users-digest-request at bungi.com" > Archives: http://www.nexial.com/mailinglists/ > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com Archives: http://www.nexial.com/mailinglists/