METASWITCH to CS1000e issues with PRI

[southerngent2no]

Has anyone switched from ATT to another Dialtone provider that is using a METASWITCH as their front end? We are having some issues since we cutover to the new provider. Issues are card readers not working. If we use the ATT PRI T-1 circuits they work, but if we route that traffic to the new METASWITCH PRI's they do not work. The provider has brought the new PRI's in on FIBER and broke them down to a DS-1 level for each PRI. We have 20 PRI's in this switch.
The second issue has to do with caller ID and it is very interesting. The T-1's are brought in as NI2 protocol. If we forward calls outside ourswitch they are getting too much info on the dchannel, from what we can gather so far. We can cutover traffic to the ATT T-1's and the caller ID info works fine. The ATT PRI's are the same as the other NI2. Not sure what ATT was using either 5ess or some version of it. BUT it works.. Cannot get the two providers to work together.
META is pointing back to us as our problem.
Anyone got any suggestions?? CS1000e release is 5.50J+.

 

[Reusser]

Problem is going to be clocking
If you do a LCNT of T1s you are probably seeing slips.

Solution is to have vendor for Metaswitch set their Router or CSU to clock from you.

 

[southerngent2no]

I wish it was that easy.. Thanks, but already check that.. All spans are clean.

 

[trvlr1]

I think you wil find that if you solve the second problem, the first will go away. My suggestion is to talk to your AT&T rep and see if they can get you a full blown config of your circuits through them and then pass to the new carrier to confirm their specs. If you can get that, and all looks the same, then you will have to look back at your own programming to make sure that your protocols match what they are requesting. If you push hard enough, you should be able to get a switch tech from the new company to work with you to tell you exactly what is coming down the circuit to them, what they expect to see and then determine if it is something that can be adjusted from either side.

Of course, another option would be to keep one of your AT&T PRI's (say its for diversity in case of an outage ....) and send your card reader traffic down it.

Just food for thought ... sorry there's no cut and dried solution in this at this time!

 

[mrquad450]

southerngent2no:

Sorry to hear you are having some issues! Do you mind saying who your service provider is or providing some detail about the service provider that I could use to reach out to them (city they are based in, etc)? I'm a Support Manager with MetaSwitch, and I'd be interested in reaching out to provide some additional support if possible.

 

[pcat200]

We have a CS1000E Rls 7.5 working with Metaswitch PRI's with no issues, CLID or otherwise. We did not switch from ATT though. We have 18 PRI's coming in on copper. We are using a combination of PRI gateways and individual cards. Basic in/outbound traffic. Here is one of the Dchannels on a gateway:
ADAN DCH 214
CTYP MSDL
MG_CARD 004 0 02
PORT 1
DES DCH_LOOP_214
USR PRI
DCHL 214
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID **
RCAP COLP NDS
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO

Maybe it is possible for the Meta switchtech to adjust what the Meta reads from the Dchannel. Is that possible Mrquad450?

 

[southerngent2no]

Thanks for the responses.. I am going to work it out with the dial tone provider.

I checked my programming on the d-channel and it is set up exactly like yours.

Thanks again..

 

[mrquad450]

Different profiles are used for different styles of PRI's. If I had an idea of who the service providers are, we could directly compare the working vs. non-working case.