PRI cost increase

[SamThePhoneMan10]

We recently got a notice from our PRI(ISDN) provider that they will hiking the price up 200% in a months time. With that price increase I know will come the ask to move everything to SIP. We are heavily dependent FAX organization due to healthcare. Looking for advise on how to alter our NEC SV9500 environment for SIP Faxing. We have a couple UG-50s but most analog dial tone comes from an old IPX2400 MUX. Well before my time. I believe Verizon IP trunkjng supports T38. We’ve been using G711 with a very high fail rate.

Any advise would be helpful .

SV9500-> V8

 

[gbtac3]

We have been moving our customers over to Audiocodes M800C gateways. No changes needed on the SV9500, (besides swinging cables), and they support T.38.

So far no complaints.

 

[DoubleDriveLine]

If you convert from PRI to SIP trunks you will need.
NEC BX9000 SBC or Audiocodes equivalent.
Virtual MGSIP or physical MGSIP 128.
Since you will have to purchase licensing from NEC I suggest upgrading your software release to V11 or the latest at that time. Provided your hardware supports it.
For the station side you can use UG50 Analog stations or Grandstream ATA units for the analog dial tone.

We use a collection of UG50, Adtran Gateway, and Grandstream ATA depending on density at the site.

We use only g.711 and have not been having any issues. The only time I have an issue is when the far side decides it needs to renegotiate the fax to t.38 to a fax machine that doesn't support it. For that reason I have fax renegotiation turn off in the MG SIP.

Don't let anyone tell you that you can live without the SBC. Trust me you need it and it gives you a lot of troubleshooting power.

 

[OzzieGeorge]

have you considered just getting something like this.....

VoIP - SIP to ISDN converter - CTi Communications Ltd

SIP to ISDN converter / ISDN to SIP converter - use your ISDN phone system on SIP VoIP linternet phone lines from SpliceCom and CTi Communications Ltd.

www.cticom.ms

 

[SamThePhoneMan10]

If you convert from PRI to SIP trunks you will need.
NEC BX9000 SBC or Audiocodes equivalent.
Virtual MGSIP or physical MGSIP 128.
Since you will have to purchase licensing from NEC I suggest upgrading your software release to V11 or the latest at that time. Provided your hardware supports it.
For the station side you can use UG50 Analog stations or Grandstream ATA units for the analog dial tone.

We use a collection of UG50, Adtran Gateway, and Grandstream ATA depending on density at the site.

We use only g.711 and have not been having any issues. The only time I have an issue is when the far side decides it needs to renegotiate the fax to t.38 to a fax machine that doesn't support it. For that reason I have fax renegotiation turn off in the MG SIP.

Don't let anyone tell you that you can live without the SBC. Trust me you need it and it gives you a lot of troubleshooting power.

We are about 70% SIP and 30% PRI. For the lost part we follow the plan you have above. I think ultimately it comes down to Verizon as a SIP carrier and the lack of support for FoIP. The Grandstream handy telephone 802 ATAs are setup with G711 pass through and we get random communication errors when using SIP as a trunk. Could be a misconfiguration on our BX800s because it doesn’t happen when that same ATA uses a PAD card and PRI trunk.

Thank you for the advise

 

[SamThePhoneMan10]

have you considered just getting something like this.....

VoIP - SIP to ISDN converter - CTi Communications Ltd

SIP to ISDN converter / ISDN to SIP converter - use your ISDN phone system on SIP VoIP linternet phone lines from SpliceCom and CTi Communications Ltd.

www.cticom.ms

Doesn’t seem within the cards to keep supporting PRI. It’s nice to have the redundancy in case Verizon nukes their network which they’ve done a couple times but at 6 figure additional price tag because of “tariffs” as they claim. My organization would probably have a better ROI fully adopting a cloud fax SaaS or finding a sip trunk provider that reliable supports FoIP.

 

[DoubleDriveLine]

In my past job, I had a coworker who was the onsite tech at a large school district in Ohio. When they switched from PRI to AT&T IPFlex they had a lot of problems with faxing. The odd thing he noticed is the further away from their location the remote fax was the greater a chance it would fail. Working with AT&T they discovered that down stream there was a provider that was converting the g.711 codec to g.729 for all calls. That of course killed faxing.

BTW at my current job we use the BX800 SBC also. if you want to compare the programing in yours hit me with DM.

 

[CoralTech]

Never had an issue with Adtran IADs. In fact using PRI is SO much easier to troubleshoot QOS issues.

 

[OzzieGeorge]

Doesn’t seem within the cards to keep supporting PRI. It’s nice to have the redundancy in case Verizon nukes their network which they’ve done a couple times but at 6 figure additional price tag because of “tariffs” as they claim. My organization would probably have a better ROI fully adopting a cloud fax SaaS or finding a sip trunk provider that reliable supports FoIP.

But you aren't supporting the Verizon side of the PRI, you are just supporting the NEC PRI the public network would be SIP so it doesn't matter what Verizon subsequently do! I should add that here in Oz I have a number of PRI users using a product called Telstra Business SIP that has an interface that converts SIP to PRI to keep their PRI Pabx working over SIP connections!

 

[SamThePhoneMan10]

But you aren't supporting the Verizon side of the PRI, you are just supporting the NEC PRI the public network would be SIP so it doesn't matter what Verizon subsequently do! I should add that here in Oz I have a number of PRI users using a product called Telstra Business SIP that has an interface that converts SIP to PRI to keep their PRI Pabx working over SIP connections!

Sorry I misunderstood