Kari,
The first thing that I would look at would be the spids that your
sending to the switch as it shows that they are INVALID.....You
know that your switch type is correct and fine in that your receiving
TEI = Terminal Endpoint Identifiers from the switch on that part.....
how did you configure the SPIDS on the config.....Could you post a
config of some sort as this looks to be the problem, or before you do
that check with Telco to see if they are seeing the correct SPIDS
coming from the CPE Equipment.....If they aren't then shut down the
interface and then bring it back up, and see what happens.....You may
have to reload the router.....If they are seeing the correct SPID's in the
ISDN switch coming from the router then verify them with what you have
programmed in the router then T/S as you would normally.....Also listen
to what Rodgers Moore was saying as I know that in the major cities in
Texas, they are about to start going to the 10-Digit Dial plan also.....Hope
this helps.....
Also do you have the spids programmed as follows
isdn spid1 <3 digit area code>< 7 digit dial number >< 4 digit trailing 0's
or 1's or 01's > < LDN >
isdn spid2 <3 digit area code>< 7 digit dial number >< 4 digit trailing 0's
or 1's or 01's > < LDN >
ex:
isdn spid1 99955522220101 5552222
isdn spid2 99955533330101 5553333
-jek-
"Kari Nurdin" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Hi All, I need help,
>
> I have a central site and a remote site in a ISDN BRI bridged environment.
> I have over and over verified the configuration and it all looks fine. I
> have a number of installs that are similar configurations and they all
> function(I have compared the configs).
>
> I am not able to connect, the following message echos:
> "02:37:133143986176: %ISDN-4-INVALID_CALLEDNUMBER: Interface BR0, Ignoring
> call, LDN and Called Party Number mismatch
> 02:37:146028888064: %ISDN-4-INVALID_CALLEDNUMBER: Interface BR0, Ignoring
> call, LDN and Called Party Number mismatch
> 02:37:158913789952: %ISDN-4-INVALID_CALLEDNUMBER: Interface BR0, Ignoring
> call, LDN and Called Party Number mismatch
> "
>
> When running the debug dialer command the following message echos:
> "02:35:28: BRI0 DDR: Dialing cause bridge (0xE0E0)
> 02:35:28: BRI0 DDR: Attempting to dial 99655555
> 02:35:141733920768: BRI0: wait for isdn carrier timeout, call id=0x8276
> 02:35:33: BRI0 DDR: Dialing cause bridge (0xE0E0)"
>
> I am researching this problem(looking over all my books), I have spoke to
> the telco and they say all is good, show isdn status shows:
> Georgian_H1#show isdn stat
> Global ISDN Switchtype = basic-ni
> ISDN BRI0 interface
> dsl 0, interface ISDN Switchtype = basic-ni
> Layer 1 Status:
> ACTIVE
> Layer 2 Status:
> TEI = 79, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
> TEI = 80, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
> TEI 79, ces = 1, state = 8(established)
> spid1 configured, spid1 sent, spid1 NOT valid
> TEI 80, ces = 2, state = 8(established)
> spid2 configured, spid2 sent, spid2 NOT valid
> Layer 3 Status:
> 0 Active Layer 3 Call(s)
> Activated dsl 0 CCBs = 1
> CCB:callid=82A0, sapi=0, ces=1, B-chan=2, calltype=DATA
> The Free Channel Mask: 0x80000001
> Total Allocated ISDN CCBs = 1
> Georgian_H1
>
> I don't want to make this post to long, however, if anyone has any ideas.
> Thanks in advance.
>
> P.S. This problem is a good one for me because I am currently studing for
> the BCRAN.
>
> Kari
> CCNA CCDA
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
> **NOTE: New CCNA/CCDA List has been formed. For more information go to
> http://www.groupstudy.com/list/Associates.html
> _________________________________
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
**NOTE: New CCNA/CCDA List has been formed. For more information go to
http://www.groupstudy.com/list/Associates.html
_________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
