Cisco 3540/RADVision GW2P issue

[nspitzer]

This problem has me totally stumped, hopefully someone around here has seen something similar before.

I have a Cisco 3540 GW2p module SW version 5.0.22, which I understand is a RADVision painted blue. Plugged into the GW I have a PRI ISDN connection from Sprint. The VC unit's could be either Tandberg or Polycom on either end, doesn't matter as I get the same issue. Our standard is 384kb (6 B's) for a VC call.

I can dial out using the GW just fine from an IP VC to an ISDN VC, no issues. However when I dial in from an ISDN VC to an IP VC the first B channel comes up, but the rest do not. Tracing the ISDN VC reveals it is attemting to dial the wrong number to bring up the rest of the B's and the Sprint tech who did a trace and a test call swears that the GW is telling the ISDN VC to dial the wrong number and the circuit is correctly configured.

In Graphical format
H323 VC -> GW -> ISDN VC =Works fine
ISDN VC > Same PRI Line -> ISDN VC =Work fine
ISDN VC 384K->GW -> H323 VC = not work

I have done the following troubleshooting steps:
1) Plugged a real VC into PRI - Works fine
2) Upgraded code on GW
3) Reset GW config (after number 2) to factory defaults and reconfigured
4) Searched GW config, GK config, VC config for bad number, not found
5) RTFM on the GW, leaves much to be desired but nothing found
6) Read release notes from multiple GW code revisions including installed one, nada
7) Called and reconfirmed ISDN switch types and had Sprint run trace - They swear its the GW
8) looked up every acronym in GW config and went through ISDN config section with a fine tooth comb - everything looks right,


Has anyone seen this before or can offer clues PLEASE let me know.

Thanks,
Nathan Spitzer
Lockheed Martin Sr. Network Communications Analyst

[Joe Vallender]

Are you using DID numbers for your IP endpoints? How different are the numbers being sent by the GW in the bonding protocol?

[nspitzer]

Yes, I am using DID numbers.

The invalid numbers are WWWWAAAYYY off in left field.... Totally different and to the best I know not even close to anything we have ever used before.

[Joe Vallender]

Using a DID number that points to your endpoint, then all 6 channels should be using the same number, right? The GW should be sending NULL fields or same digits back in the bonding exchange implying the originating endpoint should dial the same number five times. What does Cisco or your vendor support say? Sounds like something might be corrupted in the bonding setup of the GW.

[david.morin]

If your not already doing so. On the PRI Port 'X" tab select Strip Local area code..

May help - it may not ...