Latency (VoIP)

[BackBrKR]

S8720's are setup at a colocation & there is a point to point between the building & colocation. The phones work but there is latency when dial tone is given. We have a pretty big pipe & only one phone is setup at the moment. Any help would be greatly appreciated.

 

[Mitch672]

yes, and? This is purely a data/routing issue with the amount of time it takes to go round trip from the telephone to the port network and back. Perhaps you should have a media gateway localy, which can supply the dialtone, and also provide some POTS backup lines, and perhaps even an LSP if your data connection/WAN fails. It's never, ever a good idea to count on a LAN/WAN/LAN data connection for all of your connectivty. Do you have QoS setup, to prioritize the voice? Is it dark fiber with Layer 3 switches on both sides? a standard T1 is not going to get you much in the way of IP connectivty, you will not be able to run more than 13 IP phones with G711MU simultaneously.



Mitch

AVAYA Certified Expert

 

[ewaaijenberg]

What if you do a list trace station? Do you see jitter and packet loss? Also with status station you can see information about your network.
Do you have the MedPro's and switches to 100mb/full duplex?

 

[BackBrKR]

This is what I get when I do a list trace (sorry had to xxxx out the number:

LIST TRACE

time data

10:20:58 active station 8483 cid 0x6af
10:20:58 G711MU ssff ps:20 rn:1/1 172.21.17.1:2780 172.20.16.150:3480
10:20:58 xoip: faxT modemT tty:US 172.20.16.150:3480 uid:0x8c91
10:21:01 dial 91619275 route:ARS
10:21:01 term trunk-group 3 cid 0x6af
10:21:04 dial 91619275xxxx route:ARS
10:21:04 route-pattern 3 preference 1 cid 0x6af
10:21:04 seize trunk-group 3 member 70 cid 0x6af
10:21:04 Setup digits 1619275xxxx
10:21:04 Calling Number & Name NO-CPNumber NO-CPName
10:21:04 Proceed trunk-group 3 member 70 cid 0x6af
10:21:05 Alert trunk-group 3 member 70 cid 0x6af
VOIP data from: 172.20.16.150:3480
10:21:10 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:11 WC:1 Avg:0
10:21:10 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0

LIST TRACE

time data
VOIP data from: 172.20.16.150:3480
10:21:18 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:12 WC:1 Avg:0
10:21:18 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
10:21:25 active trunk-group 3 member 70 cid 0x6af
VOIP data from: 172.20.16.150:3480
10:21:28 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:11 WC:1 Avg:0
10:21:28 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 172.20.16.150:3480
10:21:38 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:12 WC:1 Avg:0
10:21:38 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 172.20.16.150:3480
10:21:48 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:11 WC:1 Avg:0
10:21:48 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
10:21:56 idle station 8483 cid 0x6af
10:22:43 TRACE COMPLETE station 8483 cid 0x0

 

[BackBrKR]

Solution - The inspection on H.232 had to be removed (network side) for the phones to work.