Couple of questions:
1. Are the PM3s hunted together with the same tel number? if
not, in the BitSurFr string, try atdtxxxxxx&yyyyyyy where x
is the first number and y is the second number.
2. Are you assigning Static IPs for the connection -either
via RADIUS, etc? I'm not sure it works with Dynamic IP
assignment but I could be wrong.
We have it working successfully *except* on occasion when an MCPPP
call is terminated, the "virtual" port stays open and the PM3 continues
to broadcast the route via OSPF. Very annoying when the user reconnects
to another PM3 as the routes won't work. We've spoken with Livingston
and they've acknownledged it but they say wait until the next release.
Kinda of sounds like Ascend :-)
Carl
carlc@shore.net
Network Operations group
==>
==> Hi all,
==>
==> We are just getting around to providing multilink PPP access for the
==> first time. It works great wherever we have only a single PM3, but
==> in locations where we have multiple units it only works if both
==> channels happen to land on the same physical unit (which is rare
==> since the PRI's are on a random hunt).
==>
==> Now, I *do* have the endpoint descriminator set to the same 12-digit
==> hex number on all units within a group and I have rebooted the PM3's
==> since setting this value. A "show mcpp" command indicates that it
==> is aware of the other units in it's group.
==>
==> When we dial, the first channel connects and all is fine for a few
==> seconds, then the second channel kicks in and both go dead. A single
==> channel link with the exact same hardware works flawlessly, as does
==> a two channel link to the same PM3.
==>
==> What am I missing?
==>
==> Mark
==> -
==> To unsubscribe, email 'majordomo@livingston.com' with
==> 'unsubscribe portmaster-users' in the body of the message.
==>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.