well, i spoke too soon yet AGAIN!
the problem started occurring again this morning. we are reverting back to the digium hardware, even though we are going to have to deal with stability issues again…
i am just fed up with this whole god-forsaken mess, and would happily drop kick the entire heap off a cliff if i thought it would do any good.
i’m open to suggestions if anyone has any.
it’s weird, but a client of mine using the Sangoma A200 card reported a problem this morning. crackly screeching sound that started on one trunk then quickly spread to the rest.
a reload of zaptel, wanrouter and asterisk sorted it, but it’s a repeat of a problem that seems to build up with call volume since zaptel 1.2.6
could it be the WanPipe or Zaptel ?? time to maybe go back to 1.2.5 and see.
it’s not 1.2.5, because that’s what we’re running…
i don’t remember when we moved from 1.2.4 to 1.2.5, but i remember we did so because of the fix for the NMI issue (which didn’t help the stability at all, for us)
Talking about QoS/ToS, I have SIP port 5060 prioritized, but I am rethinking that instead of prioritizing SIP that only carries minimal connection info why not instead prioritize RTP port 8000 or thereabout that carries the actual voice packets back and forth, or is it logical to prioritize both?
both is good, but you are correct, the RTP ports are the ones that really need priority to ensure good voice quality