ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.

[James McGuire]

Funny that, I used to get a similar kind of thing with an asustek 
winbond (iwic) card. I would get T303's nine times out of ten when I 
dialed out -- on the odd occassion it would work though, and I had the 
same phone number setup, with the area code too. Anyway I'd be surprised 
if it is the area code doing it, because as soon as I switched to a 
Fritz card (ifpi) it worked fine. I tended to blame it on the iwic 
driver because the said card worked fine under other operation systems.

James

Volker wrote:

> Hi Marcel!
>
> At 09.04.2003 14:05, Marcel Dijk wrote:
> [snip]
>
>> >>local-phone-incoming    = 0505267744
>> >>remote-phone-incoming    = *
>> >>local-phone-dialout    = 0505267744    # This *MUST* be your local 
>> number
>> >>remote-phone-dialout    = 1234567    # ppp(8) will override this
>
>
> Your local phone number looks like it contains an area code (050...).
>
> As far as I remember, you should remove the area code from your local 
> numbers (I might be wrong about that - if so, would please somebody 
> correct me? - but depending on your telco provider your PBX might 
> reject the outgoing call if you're using a wrong local number).
>
> The calling party number (local number, outgoing call) has to contain 
> only the MSN without any area or country code by a definition of the 
> ITU (again, as far as I remember).
>
> As far as I remember means I haven't used an ISDN device on a direct 
> telco connection for a while. I'm using all devices behind a PABX and 
> the addressing is different within the local network.
>
>> >>Sorry for the mega e-mail but I thought I could best be as verbose 
>> as possible.
>
>
> At least when quoting, would you please cut down the quote to a 
> reasonable amount?
>
>> These are the errors I get after running ppp and trying to dial:
>>
>> Apr  9 12:52:03 truus ppp[122]: Warning: ifaddr: Invalid command
>> Apr  9 12:52:03 truus ppp[122]: Warning: ifaddr: Failed 1
>> Apr  9 12:52:10 truus /kernel: i4b: unit 0, assigned TEI = 84 = 0x54
>> Apr  9 12:52:10 truus /kernel: i4b-L3 F_UEM: FSM function F_UEM 
>> executing, state = ST_U11 - Disc Req
>> Apr  9 12:52:14 truus /kernel: i4b-L3 T303_timeout: SETUP not 
>> answered, cr = 61
>> Apr  9 12:52:14 truus /kernel: i4b-L3 next_l3state: FSM illegal 
>> state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout!
>
>
> Helmut or Gary should have a better understanding about these error 
> messages but I guess the really important thing is 'SETUP not 
> answered' (which AFAIK should mean the remote side didn't accept the 
> call or there's no device listening at the remote side or the call 
> won't be established by the PBX. I would guess there's any phone 
> number wrong (see my note about the area code).
>
> HTH,
>
> Volker
>
>
> _______________________________________________
> freebsd-isdn at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
> To unsubscribe, send any mail to "freebsd-isdn-unsubscribe at freebsd.org"
>
> .
>