ADSL and dialer interface

Hi
I was wondering if you can use things such as dialer watch when you use a dialer interface on an ADSL connection. I have an ADSL connection I don't want used unless my main leased line goes down so I want to keep the interface down until needed. I'll get a chance to test this later this week but would be interested if anyone knows the answer beforehand.
Thanks, Stephen.

The configuration is;
A site has a leased line terminating on a router intended to take all traffic to and from a site under normal circumstances. There is another router on the site with an ADSL line intended as a backup to the leased line. So for traffic leaving that site I can easily choose that it goes via the leased line. The ADSL terminates on a particular BAS which receives a per-user static route from a radius server once ppp authentication occers.
Now, a second site only has an ADSL line. It terminates on the same BAS. So when traffic from that site hits the BAS going to the site with ADSL as backup it sees a static route with an AD of 1 via what is supposed to be the backup ADSL line and it sends traffic that way. If the backup ADSL line wasn't up there is another route that will go to a PE and over the leased line. The radius server is sending the per-user static route with an AD of 210 but the BAS seems to ignore this and installs it with AD of 1 hence beating the dynamic protocol AD.
My thought was since the ADSL line is configured as a dialer we could try to emply some of the ISDN type dialer configurations to keep the line from coming up and authenticating until it is needed and therefore keeping the per user static route out of the BAS routing table until the line is needed.
I have no idea why the BAS is not accepting the AD of 210 supplied by Radius but I am not in control of that part of the circuit. I am in control of the ADSL router used for backup and as such hoped there was something I could do there to influence the problem. I could run a routing protocol but wanted to try and see if I could keep the ADSL down somehow first.
S.

Similar Messages

Virtual template interface vs Dialer interface?

Hi all,
I am little confusing about virtual template interface and dialer interface. I understood that both of them are logical interface and will be mapped to physical interface dynamically. What is different? When would I use virtual template interface or dialer interface?
Please suggest too.
Thanks a lot,
Nitass

hi
AFAIK we use virtual template in L2TP scenarios where you will have LAC and LNS .
the configs related to VT comes in LNS which is ur local network server for your remote clients from where the L2 tunnel gets orginated.
And about your dialer interfaces we use them very frequently in most of the situations like where you require to club 2 Physical isdn lines and to make use them as a single pipe or using single isdn line and connect it to 2 different locations using 2 B channels using 2 dialers...
if you need to know more about them would suggest to check out this link which will give fair idea about them..
http://www.cisco.com/en/US/tech/tk801/tsd_technology_support_category_home.html
hope this helps u out..
regds

Cisco 877w -Configuration of subinterfaces and main interface within the same bridge group is not permitted

Hi,
I have another problem - after upgrade ios wirelles connection not work.
After reload i have :
Configuration of subinterfaces and main interface
within the same bridge group is not permitted
STP: Unable to get the port parameters.
Please configure the bridge group on this interface first.
Please configure the bridge group on this interface first.
Please configure the bridge group on this interface first.
SETUP: new interface NVI0 placed in "shutdown" state
my old configuration work propertly in the old software, but after update i have notificatio.
Old thread:
https://supportforums.cisco.com/discussion/12379491/cisco-877w-no-wireless-connection
my current sh run:
version 12.4
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
service password-encryption
hostname cisco
boot-start-marker
boot system flash:c870-advipservicesk9-mz.124-24.T6.bin
boot-end-marker
logging message-counter syslog
logging buffered 4096 informational
enable secret 5 $1$eCNp$rWuBfZ/cexnwnkm7L447s.
aaa new-model
aaa session-id common
dot11 syslog
dot11 ssid ciscowifi
vlan 1
authentication open
authentication key-management wpa
guest-mode
wpa-psk ascii 7 050D031D26595D0617
dot11 wpa handshake timeout 500
ip source-route
no ip dhcp use vrf connected
ip dhcp excluded-address 192.168.56.1
ip dhcp pool CLIENT
import all
network 192.168.56.0 255.255.255.0
default-router 192.168.56.1
dns-server 8.8.8.8 194.204.159.1 194.204.152.34
lease 0 2
ip cef
no ip domain lookup
no ipv6 cef
multilink bundle-name authenticated
username marek password 7 00121A0908500A
archive
log config
hidekeys
ip tcp path-mtu-discovery
bridge irb
interface ATM0
description Polaczenie ADSL do ISP$ES_WAN$
no ip address
no atm ilmi-keepalive
pvc 0/35
encapsulation aal5mux ppp dialer
dialer pool-member 1
hold-queue 224 in
interface FastEthernet0
description Edzia
interface FastEthernet1
description dom
interface FastEthernet2
description Dziadek
interface FastEthernet3
interface Dot11Radio0
no ip address
no ip redirects
ip local-proxy-arp
ip nat inside
ip virtual-reassembly
no dot11 extension aironet
encryption vlan 1 mode ciphers tkip
encryption mode ciphers aes-ccm tkip
broadcast-key change 3600
ssid ciscowifi
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0 48.0 54.0
station-role root
world-mode dot11d country AU indoor
no cdp enable
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 spanning-disabled
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
interface Dot11Radio0.1
description ciscowifi
encapsulation dot1Q 1 native
no cdp enable
interface Vlan1
no ip address
bridge-group 1
interface Dialer0
description Interfejs dzwoniacy
ip address negotiated
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer-group 1
ppp chap hostname [email protected]
ppp chap password 7 xxxxxxxxxxxxxxxxxxxxxx
interface BVI1
description Polaczenie dla sieci LAN
ip address 192.168.56.1 255.255.255.0
ip nat inside
ip virtual-reassembly
no ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer0
no ip http server
no ip http secure-server
ip nat inside source list 100 interface Dialer0 overload
ip nat inside source static tcp 192.168.56.10 80 interface Dialer0 80
ip nat inside source static tcp 192.168.56.10 22 interface Dialer0 22
logging trap debugging
logging 192.168.56.10
access-list 100 permit ip 192.168.56.0 0.0.0.255 any
access-list 100 deny ip any any
no cdp run
snmp-server community ciskacz RO
snmp-server chassis-id ciskacz
control-plane
bridge 1 protocol ieee
bridge 1 route ip
line con 0
no modem enable
line aux 0
line vty 0 4
exec-timeout 0 0
transport preferred ssh
transport input ssh
scheduler max-task-time 5000
end
please help - thanks!

Hello Marek,
I suppose you are not planning to do any kinds of advanced config using several VLANs and multiple SSIDs so let's just make your configuration simple and working.
In short, you need to remove all references to VLAN 1 and to any subinterfaces possibly related to the VLAN 1. This means in particular (follow these steps in sequence):
Remove the Dot11Radio0.1 subinterface entirely
In the Dot11Radio0 section, remove the encryption vlan 1 mode ciphers tkip command
In the dot11 ssid ciscowifi section, remove the vlan 1 command
After performing these steps, make sure that the ssid ciscowifi and encryption mode commands are still present in the Dot11Radio0 configuration, and if not, reenter them.
Best regards,
Peter

Can you help? Two dialer interfaces with IP SLA for default route failover - issues

I have an issue with a Cisco 2821, it has an ADSL2+ HWIC whose ATM interfaces is linked to dialer 1 and a Gi0/1 interface with a pppoe client which is linked to dialer 2. Both dialer interfaces are up with their respective IP addresses. If the ADSL on dialer 1 fails i want the IP SLA to kick and and replace the default route for dialer 1 with one for dialer 2.
This config works if you manually shut down the dialer 1 interface, it injects the default route for dialer 2 and then when you unshut the interface, the default route for dialer 1 comes back. The problem i have is if you take out the cable for the ATM interface and take it down, it does not take the route out the routing table and the default route for dialer2, which works if you just shut down dialer 1 does not appear.
whats the difference between shutting down dialer1 and it fails over the default route and taking the cable out then it does not?
Here is my config, i'm sure its something simple i'm doing wrong, can anyone help???
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname Router
boot-start-marker
boot-end-marker
logging message-counter syslog
enable secret 5 $1$qOOJ$HV5AH6US/YZMuCGPYp3pP.
no aaa new-model
dot11 syslog
ip source-route
ip cef
ip dhcp excluded-address 192.168.0.1
ip dhcp pool pool1
network 192.168.0.0 255.255.255.0
default-router 192.168.0.1
dns-server 188.92.232.50 188.92.232.100
no ip domain lookup
no ipv6 cef
multilink bundle-name authenticated
voice-card 0
no dspfarm
archive
log config
hidekeys
track 1 ip sla 1 reachability
interface GigabitEthernet0/0
description Gi0/30 Local LAN
ip address 192.168.0.1 255.255.255.0
ip verify unicast reverse-path
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
ip nat inside
ip virtual-reassembly
no ip mroute-cache
duplex auto
speed auto
snmp trap ip verify drop-rate
no mop enabled
interface GigabitEthernet0/1
no ip address
duplex auto
speed auto
pppoe enable group global
pppoe-client dial-pool-number 2
interface ATM0/2/0
description ATM0_DSL
no ip address
no ip redirects
no ip unreachables
no ip proxy-arp
ip flow ingress
logging event atm pvc state
logging event subif-link-status
no atm ilmi-keepalive
dsl operating-mode auto
dsl enable-training-log
pvc 0/38
encapsulation aal5mux ppp dialer
dialer pool-member 1
interface Dialer1
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
ip nat outside
ip virtual-reassembly
encapsulation ppp
dialer pool 1
keepalive 1 3
no cdp enable
ppp lcp predictive
ppp authentication pap chap callin
ppp chap hostname ********@ccsleeds.net
ppp chap password 0 ********
ppp pap sent-username *******@ccsleeds.net password 0 ********
interface Dialer2
ip address negotiated
no ip redirects
no ip unreachables
no ip proxy-arp
ip mtu 1492
encapsulation ppp
dialer pool 2
keepalive 1 3
no cdp enable
ppp lcp predictive
ppp authentication pap chap callin
ppp chap hostname **********@adsllogin.co.uk
ppp chap password 0 *********
ppp pap sent-username *********@adsllogin.co.uk password 0 ***********
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 Dialer1 track 1
ip route 0.0.0.0 0.0.0.0 Dialer1
ip route 0.0.0.0 0.0.0.0 Dialer2 10
no ip http server
no ip http secure-server
ip nat inside source list 1 interface Dialer1 overload
ip sla 1
icmp-echo 8.8.8.8 source-interface di1
timeout 1000
threshold 100
frequency 3
ip sla schedule 1 life forever start-time now
access-list 1 permit 192.168.0.0 0.0.0.255
control-plane
gatekeeper
shutdown
line con 0
line aux 0
line vty 0 4
password test
login
scheduler allocate 20000 1000
end

Sure that EEM can shut/unshut interface...you have "event track" in EEM for monitoring track events...for example:
event manager applet test
event track 1 state down
action 1.0 command "enable"
action 1.1 command "conf t"
action 1.2 command "interfac dialer 1"
action 1.3 command "shut"
action 1.4 syslog "Dialer 1 down!!!"
action 1.5 end
This would be an example from head :)
You would need another EEM similar to this one for unshutting interface with "event track 1 state up" for bringing interface up again.
Again as I said you would need to test this before putting in production and you would maybe need to tweak this a little bit acording to your needs...
BR,
Dragan

ADSL and FR via one router

I am try to configure a 2801 router to access one ISP via two services, Frame Relay and ADSL. I want email traffic to go over FR only and browsing over ADSL. If either of these services fail all traffic should be routed through the active service. The ISP setup FR as the primary route for incoming email traffic. The services are failing over but the problem is: inbound traffic fail to reach a host when the dialer interface is up. From outside I can ping the ethernet interface, the firewall and mail server When I down the dialer interface, but the minute the dialer interface comes up, I cannot ping these anymore including the serial interface. I can only ping the dialer interface. I attached the config. I hope someone can help me.Please review and let me know where the problem is and your solution. Thanks.

Hello,
in addition to Martin´s post, I am not sure if NAT is applicable at all in your situation and configuration. Since you seem to be using pubic IP addresses, and since you do not have inside and outside interfaces configured, you might as well take the lines:
ip nat inside source list 1 interface Dialer0 overload
access-list 1 permit any
out of your configuration alltogether.
As to your (policy) routing, I would make the two default routes equal:
ip route 0.0.0.0 0.0.0.0 Dialer0
ip route 0.0.0.0 0.0.0.0 205.80.76.13
that is, dot not specify an administrative distance; and change the Dialer0 to the nxt-hop address, if you know that address:
ip route 0.0.0.0 0.0.0.0 X.X.X.X
ip route 0.0.0.0 0.0.0.0 205.80.76.13
and change the route map as well:
route-map STATIC permit 20
description allow all other outbound traffic on ADSL
match ip address 130
set ip next-hop X.X.X.X
With CEF enabled, the policy route takes precedence, and only if the next hop specified in the route map is not available, the CEF routing table will be consulted, which should contain one entry only as well in case one of the next hop addresses is unavailable...
Does that make sense ?
Regards,
GP

I cannot send any message, on my Outlook Microsoft: Mac 2011. Thr following message appears. What shall I do? If your IP is a dynamic one (ADSL or dial-up, for instance) please reconfigure your outgoing settings to use your ISP server. (

I cannot send any message, on my Outlook Microsoft: Mac 2011. Thr following message appears. What shall I do?
My connection with Internet is fine, and I can receive messages, only cannot send.
"If your IP is a dynamic one (ADSL or dial-up, for instance) please reconfigure your outgoing settings to use your ISP server."
Best regards

See if your e-mail provider uses any different ports for SMTP, such at 25, 465 or 587.
if you're using Gmail, then port 587 will work with authentication set.

Dialler interface and Isdn interface

Can someone tell me the difference
When bringing up an isdn interface, Am I correct in saying it has to raise the line by calling the isdn number, If so whats the difference between this and a dialler interface ?
thanks
Carl

Hi Carl,
A dialer interface is a parent interface that holds central protocol characteristics for ISDN D channels, which are part of specified dialer rotary groups. Data packets are delivered to dialer interfaces, which in turn initiate dialing for inbound calls. In most cases, D channels get their core protocol intelligence from dialer interfaces.
A dialer interface is user configurable and linked to individual B channels (such as S0:0, S0:1, S0:2), where it delivers data packets to their physical destinations. Dialer interfaces seize physical interfaces to cause packet delivery.
ISDN BRI delivers a total bandwidth of a 144-kbps via three separate channels. Two of the channels, called B (Bearer) channels, operate at 64 kbps and are used to carry voice, video, or data traffic. The third channel, the D (Data) channel, is a 16-kbps signaling channel used to carry instructions which tells the telephone network how to handle each of the B channels. ISDN BRI is often referred to as "2 B+D."
A D channel notifies the central office switch to send the incoming call to particular timeslots on the router. Each one of the bearer or B channels carries data or voice. The D channel carries signaling for the B channels. The D channel also identifies if the call is a digital call or analog call. Analog calls are decoded and then get sent off to the modems. Digital calls are directly relayed off to the ISDN processor in the router.
HTH,
-amit singh

AS5300 RAS and Dial Backup

We have an AS5300 that currently supports 5 RAS dial-in users. I would like to expand the use of the AS5300 to also be a dial backup solution for some of our remote branch routers. These routers will be using a mixture of ISDN (BRI) and Analog (Async wic-1am) for their dial back up. I also need to run EIGRP over the dial backup links to support the remote LAN failover.
I've compiled a proposed configuration that I think might work for this solution. My main question is how will the AS5300 be able to know which Async interface to use when a remote user needing interactive session dials in versus a remote router.
Please take a look at my proposed config and give me some feedback on if you think this will work. Thanks!!

One way I would do this is to define 5 additional Dialer interfaces for the 5 RAS dial-in users and bind them to int Group-Async 1 using dialer-pool 1.
The 5 new dialer interfaces will be configured for async mode interactive.

Routes to dialer interfaces

I am probably supposed to know this already, but I shall swallow my pride and ask anyway:
Suppose I have an ISDN primary rate interface with 30 channels, which provides a dialer pool. I then have several dialer profile interfaces that use that pool. I then make a static route to one of those dialer interfaces, say ip route 192.168.42.0 255.255.255.0 Dialer 6. So far so good ... pretty standard stuff.
I then want to redistribute that static route into, say, OSPF. But I want to arrange it so that if there are no channels in the dialer pool, for example if the ISDN primary rate connection is down, then the route is not redistributed, or even better if it disappears from the access router altogether?
What I am saying is: how can I arrange for a dialer interface to be effectively down whenever the physical interfaces in its dialer pool are down?
N.B. I do not want ODR, because I do not want to receive routes through the dialer, for security reasons. The redistributed routes must be generated as statics in the access router (which is under my control), then redistributed into my OSPF, but depending on the state of the dialer pool.
Thanks in advance.
Kevin Dorrell
Luxembourg

Bump.
Does anyone have an idea how I could do this? I don't think I can do it by tracking a remote object because it is a dialup interface, and it would be too costly to dial every few seconds just to track the PRI availability.
To expand on the architecture, I have two sites: a main site and a backup site. The sites are connected together by a Gig link, so I can run VLANs between the sites. Dialin/dialout services must be assured at all times. My idea was to have a remote access router on each site, connected to the PTSN via a PRI. On the outside, the PRI provider can arrange to redirect the number if the main site is down.
Each remote access router has some static routes pointing to dialer profile interfaces. On the inside, each remote access router must redistribute these static routes into OSPF, with the main site having a lower metric than the backup site. But if the main site PRI goes down, the main site router must stop advertising its routes.
How can I achieve that, bearing in mind that the static routes point to spoof-up dialer interfaces?
Kevin Dorrell
Luxembourg

Remote and local interface on same ejb 3.0 bean instance

Hi,
Is it posible to get remote and local interface on same ejb 3.0 bean instance.
For example get local interface of a bean and than pass it as remote to client.
Both interfaces must operate on same bean instance.
Thanks
Zlaja

yes. You can implement multiple interfaces on a single class, so you can add a local and a remote interface. One trick to avoid duplicate code is to simply make the remote interface extend the local interface; then you only have to add the @Remote annotation and you're done.
For example get local interface of a bean and than pass it as remote to client.You don't pass an instances to a client, a client looks up a remote instance of the bean through JNDI.

The difference between IEEE802.1Q Native VLAN sub-interface and Physical interface?

Hello
I think the following topologies are supported for Cisco Routers
And the Physical interface also can be using as Native VLAN interface right?
Topology 1.
R1 Gi0.1 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
R1 - configuration
interface GigabitEthernet0.1
encapsulation dot1Q 1 native
ip address 10.0.0.1 255.255.255.0
Topology 2.
R1 Gi0 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
interface GigabitEthernet0
ip address 10.0.0.1 255.255.255.0
And is it ok to use the physical interface and sub-interface with dynamic routing such as EIGRP or OSPF etc?
R1 Gi 0 ---- Point to Multipoint EIGRP or OSPF ---- Gi0 R2 / R3
Gi 0.20--- Point to Point EIGRP or OSPF --- Gi0.10 R4 (same VLAN-ID)
R1 - configuration
interface GigabitEthernet0
ip address 10.0.0.1 255.255.255.0
interface GigabitEthernet8.20
encapsulation dot1Q 20
ip address 20.0.0.1 255.255.255.0
Any information is very appreciated. but if there is any CCO document please let me know.
Thank you very much and regards,
Masanobu Hiyoshi

Hello,
The diagram is helpful.
If I am getting you correctly, you have three routers interconnected by a switch, and you want them to operate in a hub-and-spoke fashion even though the switch is capable of allowing direct communication between any of these routers.
Your first scenario is concerned with all three routers being in the same VLAN, and by using neighbor commands, you force these routers to establish targeted EIGRP adjacencies R1-R2 and R1-R3, with R1 being the hub.
Your second scenario is concerned with creating one VLAN per spoke, having subinterfaces for each spoke VLAN created on R1 as the router, and putting each spoke just in its own VLAN.
Your scenarios are not really concerned with the concept of native VLAN or the way it is configured, to be honest. Whether you use a native VLAN in either of your scenarios, or whether you configure the native VLAN on a subinterface or on the physical interface makes no difference. There is simply no difference to using or not using a native VLAN in any of your scenarios, and there is no difference to the native VLAN configuration being placed on a physical interface or a subinterface. It's as plain as that. Both your scenarios will work.
My personal opinion, though, is that forcing routers on a broadcast multi-access segment such as Ethernet to operate in a hub-and-spoke fashion is somewhat artificial. Why would you want to do this? Both scenarios have drawbacks: in the first scenario, you need to add a neighbor statement for each spoke to the hub, limiting the scalability. In the second scenario, you waste VLANs and IP subnets if there are many spokes. The primary question is, though: why would you want an Ethernet segment to operate as a hub-and-spoke network? Sure, these things are done but they are motivated by specific needs so I would like to know if you have any.
Even if you needed your network to operate in a hub-and-spoke mode, there are more efficient means of achieving that: Cisco switches support so-called protected ports that are prevented from talking to each other. By configuring the switch ports to spokes as protected, you will prevent the spokes from seeing each other. You would not need, then, to configure static neighbors in EIGRP, or to waste VLANs for individual spokes. What you would need to do would be deactivating the split horizon on R1's interface, and using the ip next-hop-self eigrp command on R1 to tweak the next hop information to point to R1 so that the spokes do not attempt to route packets to each other directly but rather route them over R1.
I do not believe I have seen any special CCO documents regarding the use of physical interfaces or subinterfaces for native VLAN or for your scenarios.
Best regards,
Peter

What is the diff b/w Abstract class and an interface ?

Hey
I am always confused as with this issue : diff b/w Abstract class and an interface ?
Which is more powerful in what situation.
Regards
Vinay

Hi, Don't worry I am teach you
Abstract class and Interface
An abstract class can have instance methods that implement a default behavior. An Interface can only declare constants and instance methods, but cannot implement default behavior and all methods are implicitly abstract. An interface has all public members and no implementation. An abstract class is a class which may have the usual flavors of class members (private, protected, etc.), but has some abstract methods.
Edited by SASIKUMARA
SIT INNOVATIONS- Chennai
Message was edited by:
sasikumara
Message was edited by:
sasikumara

Remote and Home interface binding to an EJB2.1/3.0 bean.

When deploying a complete ejb bean,
-What associated a bean class, within the container,
with it's home and remote interfaces?
-JBoss Application server requires that the Bean class
directly implement both interfaces.
-Assuming EJB 2.1, is this approached by
interface implementation, a naming convention,
a common location in a package/directory,
or is this put in the deployment descriptor xml file?
What is the standard approach?
Z.

If you have included the HTTP server with your 10.1.3.2 installation you could also setup a proxy/proxy-reverse setup in the portal http server for the /app08 mountpoint and point this to your 10.1.3.2 server....

Remote and Home Interfaces

Why do we need a home interface and remote interface for a ejb.
Must these interfaces be there for each ejb?

Why do we need a home interface and remote interface
for a ejb.The Home interface is like a factory for getting to your beans. The remote interface is what you use to speak "directly" to the bean. It's remote because the bean is usually on a remote server somewhere (not in the same VM as your client code). The same is true for the home interface in terms of it being remote.
The corresponding LocalHome and Local interfaces are for use when the bean in question is not remote.
Must these interfaces be there for each ejb?You need either a Home and Remote or LocalHome and Local interface for all beans except Message Driven Beans.

How to connect to third party using PI for outbound and inbound interfaces

Hello,
I have scenarios where I have data coming in from third party EDI subsystem and sent to SAP. And also from SAP to EDI subsystem. We need to send the XMLs to the EDI subsystema nd also receive XMLs.
Can someone please suggest the ways I can connect to EDI subsytem for both Outbound and Inbound interfaces.
Thanks

Hi Prabhu,
EDI file is different from the normal flat or xml file. Hope you understand the difference.
Now if your EDI subsytem has the capability of converting the xml file to edi file viceversa then create and receive the xml file from the EDI subsystem. For the xml file you may use the file adapter as an option.
If it doesnot have the capability then seeburger adapter needs to be used. This is not an inbuilt adapter. So your company needs to purchase it.
Regards,
---Satish

ADSL and dialer interface

Similar Messages

Maybe you are looking for