Re: isdn callback

From: sohu (xieji@sohu.com)
Date: Mon Jun 30 2003 - 22:28:59 GMT-3


Hello
    isdn callback does not require isdn caller ,it adds more security to your dial system.If you remove this command,and add ppp callbak request on your calling router and ppp callback accept on your called router,I think it is all ok.A few days I just test the ISDN callbck.Addtionally,you can see the cause of your isdn call failure:
4d19h: ISDN BR0: Incoming call rejected due to screening!!!! it is because you configure isdn caller on your called router.
   
      
----- Original Message -----
From: "SHARMA,MOHIT (HP-Germany,ex1)" <mohit.sharma@hp.com>
To: <ccielab@groupstudy.com>
Sent: Monday, June 30, 2003 10:28 PM
Subject: isdn callback

> HI All,
>
> I am trying isdn callback. I am using normal isdn numbers, so also have to
> use the isdn calling number <> at the calling router. However the called
> router still does not, recognise the calling router number. Is there any
> other way to make the called router see the calling number, if your provider
> does not support caller-id??
>
> interface BRI0
> ip address 138.1.122.1 255.255.255.0
> encapsulation ppp
> ip ospf cost 9999
> dialer idle-timeout 9999
> dialer map ip 138.1.122.2 name unit2 broadcast 230897
> dialer-group 8
> isdn switch-type basic-net3
> isdn calling-number 237340
> no peer neighbor-route
> ppp authentication chap callin
> ppp multilink
> ppp timeout multilink link add 120
> ppp timeout multilink link remove 45
> end
>
> the called router-
> ip address 138.1.122.2 255.255.255.0
> encapsulation ppp
> ip ospf cost 9999
> dialer idle-timeout 30
> dialer map ip 138.1.122.1 name unit1 broadcast 237340
> dialer-group 8
> isdn switch-type basic-net3
> isdn caller 237340 callback
> no peer neighbor-route
> ppp authentication chap
> ppp multilink
> end
>
> the debug on the called router-
> 4d19h: ISDN BR0: RX <- SETUP pd = 8 callref = 0x04
> 4d19h: Sending Complete
> 4d19h: Bearer Capability i = 0x8890
> 4d19h: Channel ID i = 0x89
> 4d19h: Calling Party Number i = 0x00, 0xA3, Plan:Unknown,
> Type:Unknown <<<<<------------------------------
> 4d19h: Called Party Number i = 0xC1, '230897', Plan:ISDN,
> Type:Subscrib)
> 4d19h: ISDN BR0: Incoming call rejected due to screening.
> 4d19h: ISDN BR0: TX -> RELEASE_COMP pd = 8 callref = 0x84
> 4d19h: Cause i = 0x8095 - Call rejected
> 4d19h: BR0 DDR: ip (s=135.1.122.2, d=224.0.0.5), 64 bytes, outgoing
> uninteresti)
> 4d19h: BR0 DDR: sending broadcast to ip 135.1.122.1 -- failed, not connected
> unit2#
> 4d19h: ISDN BR0: RX <- SETUP pd = 8 callref = 0x33
> 4d19h: Sending Complete
> 4d19h: Bearer Capability i = 0x8890
> 4d19h: Channel ID i = 0x89
> 4d19h: Calling Party Number i = 0x00, 0xA3, Plan:Unknown,
> Type:Unknown
> 4d19h: Called Party Number i = 0xC1, '230897', Plan:ISDN,
> Type:Subscrib)
> 4d19h: ISDN BR0: Incoming call rejected due to screening.
> 4d19h: ISDN BR0: TX -> RELEASE_COMP pd = 8 callref = 0xB3
> 4d19h: Cause i = 0x8095 - Call rejected
>
> Thanks as always for your input.
>
> Smiles,
> Mohit.
>
>
> _______________________________________________________________________
> You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:15 GMT-3