Inbound - Can't Hear Customer but They Can Here Us

[tommyinnn]

We have recently upgraded to T1 lines, and have added a couple servers and several seats. Ever since, all outbound is running great, however inbound is a different story!
On 70% of inbound calls, we can not hear the customer, but the customer can hear us.

We are running 3 servers, our main (database) server, we have used for months with no problems - this problem happens regardless what server a agent is on.. so I'm fairly confident it is not a server issue.

WILLIAM, I know you were talking to Rob about this, I do believe it is as you said, a network issue as we just upgraded both our connection and router settings - I just can't pinpoint what the problem is.
It seems very odd that some of the calls are fine.

And also, our router is in need of a upgrade - can you guys recommend the best type to get - we plan on having about 100 seats in upcomming months - thanks for any help you can give!

[williamconley]

T1?

Have you been able to reproduce the issue reliably at all?

the only server you "upgrade" would be mysql/web ... the others are merely cloned (just keep adding more, and remove web/mysql from them so the web/mysql servers are dedicated and powerful and the dialers just keep getting added to the system).

[tommyinnn]

Yes - we have 2 T1 lines - Brighthouse would not run service here so we had to go with Century Link - they are BlAzInG FAST!

Reproduce it - yes, we have incoming calls all day, the customers can rarely hear a agent.

No, the only upgrades on the servers are in the Vicidial now instructions... found on this page
http://vicidialnow.blogspot.com/

Our original server has not been touched in months - this only started a couple weeks ago with the network upgrade.

[williamconley]

are these T1s "bonded"? if so ... the issue could be the route taken confusing asterisk or your router.

[tommyinnn]

Yes, they are bonded - very interesting William - what could I do to verify this is the problem, and how to correct it.

[williamconley]

i would expect the sip debug to "wait" and then timeout when the packet never arrives (but only on calls that fail). it could be that multicasting is not supported but turned on.