[VoiceOps] using a T1 to extend PRI service and involuntary fax over sip

[Alex Balashov]

Chuck Norris would put an STM-1's worth of jitter-free calls on one  
copper strand without a ground.  Your gateway would gain DSP density  
when he talks.

--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/

On Jan 24, 2011, at 4:46 PM, Beth Johnson <bethjohnson5060 at gmail.com>  
wrote:

> "A year ago", "September", "November"... looks like there is no  
> solid time domain event correlation to be had.
>
>  What would Chuck Norris do?  Bash in everyone's head at the same  
> time, knowing that one of them must be the bad guy.
>
>
> -B
>
>
>
>
>
> On Mon, Jan 24, 2011 at 10:24 AM, Mark Kent  
> <mark at noc.mainstreet.net> wrote:
> I stumbled across a situation where a fax-to-email service gets
> inbound calls, from Carrier X, over a PRI into a cisco 5350 which then
> relays the calls, via an x-conn PRI, to a directly-attached linux box.
> This has worked for years.
>
> About a year ago, it was revealed that the above-mentioned PRI
> connects to the edge of Carrier X's SIP infrastructure.  That is,
> calls start from some PSTN-connected fax machine, somewhere in the
> USA, go through a PSTN-to-SIP gateway, travel as SIP to the building
> where this cisco 5350 is, and then go through Carrier X's SIP-to-TDM
> equipment for delivery over the PRI to the cisco 5350.
>
> This led to some concern, since we all know that fax over SIP can be
> problematic.   But everything was working, hundreds of faxes a day
> were pulsing through the system.
>
> Up until September the cisco 5350 was in the same building as Carrier
> X's TDM equipment.  In late September, a point-to-point, B8ZS/ESF T1
> was used to extend the in-building cross-connect between Carrier X
> and the cisco 5350.  The cisco 5350, and related servers, are now
> eight miles away (both endpoints in Manhattan, using VerizonBusiness
> for the T1, both endpoints "on-net", no ILEC involved).
>
> Since November, maybe half a percent of the faxes fail to work.
> They get a communication error at the start, at the modem negotiation.
> The T1 circuit is clean.
>
> Some people think that failures may not have been reported/noticed in
> October, but they occured nevertheless.  This would suggest that the
> previous set-up was a very delicately balanced system and the moving
> of the cisco5350 eight miles away, necessitating the use of a T1 to
> carry the PRI to the new location, may be the root cause of the
> failures.  Occam's razor reasoning supports this.
>
> The grassy knoll people believe that, in November, Carrier X started
> an effort to wring more out of their SIP network. Perhaps they started
> using different peers in various parts of the country.  Maybe their
> PSTN-to-SIP gateways were tuned to use less bandwidth.  When asked,
> Carrier X answered a different question, in a fashion similar to a
> politician.
>
> I'm wondering whether any experts here have an opinion to offer?
>
> Thanks,
> -mark
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110124/75673ccf/attachment.html>