One Way Audio IP Phone

[kabudoy]

Hi All,

i have problem on my IP phone's having intermittent one way audio in site B s8300 LSP G350 gateway with 8 analog trunks for incoming my main server are site A (s8300 G700).

we have a router and switch shared with data network. VLan is not activated for voice and data. kindly see trace below. hoping to hear soon on your suggestion.


LIST TRACE

time data

12:58:40 Calling party trunk-group 10 member 3 cid 0x1ab
12:58:40 Calling Number & Name NO-CPNumber NO-CPName
12:58:40 active trunk-group 10 member 3 cid 0x1ab
12:58:42 Category + CPN 00000012345
12:58:42 dial 3278
12:58:42 ring vector 3 cid 0x1ab
12:58:43 active announcement 4321 cid 0x1ab
12:58:43 hear annc board 002V9 ext 4321 cid 0x1ab
12:58:52 dial 997
12:58:52 ring station 997 cid 0x1ab
12:58:52 G711MU ssff ps:20 rn:2/2 192.168.137.205:13214 192.168.137.238:24
12:58:52 xoip: fax:Relay modemff tty:US 192.168.137.238:2084 uid:0x6
12:59:01 active station 6789 cid 0x1ab
VOIP data from: 192.168.137.238:2084
12:59:03 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0

12:59:03 Pkloss:0 0 * * * * * * * *: Oofo:255 WC:0 Avg:0
12:59:06 conf/tran hold station 6789 cid 0x1ab
12:59:06 active station 6789 cid 0x1b1
12:59:06 active announcement 4320 cid 0x1ab
12:59:06 G711MU ssff ps:20 rn:2/2 192.168.137.205:13214 192.168.137.238:24
12:59:06 xoip: fax:Relay modemff tty:US 192.168.137.238:2094 uid:0x6
12:59:07 dial 6999
12:59:07 ring station 6999 cid 0x1b1
12:59:07 G711MU ssff ps:20 rn:2/2 192.168.137.208:42476 192.168.137.238:26
12:59:07 xoip: fax:Relay modemff tty:US 192.168.137.238:2076 uid:0x9
12:59:08 transfer station 6789 cid 0x1b1
12:59:22 no answer station 6999 cid 0x1b1
12:59:22 coverage-path 21 point 1 cid 0x1b1
12:59:22 G729A ssff ps:20 rn:2/1 192.168.137.238:2084 192.168.2.203:2086
12:59:22 xoip: fax:Relay modemff tty:US 192.168.137.238:2084 (igc)
12:59:22 xoip: fax:Relay modemff tty:US 192.168.2.203:2086 (igc)

12:59:22 G729 ssff ps:20 rn:2/1 192.168.137.238:2084 192.168.2.203:2086
12:59:24 active station 6000 cid 0x1b1
VOIP data from: 192.168.137.238:2084
12:59:33 Jitter:0 3 2 1 0 1 1 0 0 2: Buff:30 WC:20 Avg:0
12:59:33 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 192.168.137.238:2084
12:59:43 Jitter:14 4 6 1 1 1 1 2 1 2: Buff:38 WC:100 Avg:2
12:59:43 Pkloss:2 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
12:59:53 Jitter:1 1 2 5 6 4 11 12 14 7: Buff:30 WC:100 Avg:3
12:59:53 Pkloss:0 0 0 0 0 0 0 2 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:00:03 Jitter:1 1 2 0 1 0 0 1 1 1: Buff:30 WC:100 Avg:2
13:00:03 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:00:13 Jitter:5 6 5 5 2 2 1 1 0 0: Buff:30 WC:150 Avg:2

13:00:13 Pkloss:0 0 1 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:00:23 Jitter:1 2 2 3 0 2 1 3 3 3: Buff:30 WC:150 Avg:2
13:00:23 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:00:33 Jitter:1 1 1 1 3 2 2 0 3 4: Buff:30 WC:150 Avg:2
13:00:33 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:00:43 Jitter:3 1 3 1 0 0 1 0 1 0: Buff:30 WC:150 Avg:2
13:00:43 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:00:53 Jitter:1 2 1 3 2 1 5 3 1 0: Buff:30 WC:150 Avg:2
13:00:53 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:01:03 Jitter:2 5 5 3 1 1 0 2 2 3: Buff:30 WC:150 Avg:2
13:01:03 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0

VOIP data from: 192.168.137.238:2084
13:01:13 Jitter:2 0 2 0 2 0 0 2 1 2: Buff:30 WC:150 Avg:2
13:01:13 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:01:23 Jitter:2 1 0 2 1 2 0 1 3 3: Buff:30 WC:150 Avg:2
13:01:23 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:01:33 Jitter:2 1 1 1 1 0 0 1 2 2: Buff:30 WC:150 Avg:2
13:01:33 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:01:43 Jitter:3 1 1 2 1 1 2 2 1 2: Buff:30 WC:150 Avg:2
13:01:43 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:01:53 Jitter:2 1 0 1 1 1 1 2 1 1: Buff:30 WC:150 Avg:1
13:01:53 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084

13:02:03 Jitter:0 1 1 1 2 0 2 2 1 1: Buff:30 WC:150 Avg:1
13:02:03 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:02:13 Jitter:2 0 2 1 1 1 1 4 2 1: Buff:30 WC:150 Avg:1
13:02:13 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:2 Avg:0
VOIP data from: 192.168.137.238:2084
13:02:23 Jitter:3 1 1 1 0 1 2 1 1 2: Buff:30 WC:150 Avg:1

 

[Zowwie438]

Check your switches and various network components for half duplex/full duplex settings.

Most network components leave this at AUTO... Be sure to lock it down to what you want (full duplex). And be sure to lock in your speed as well.

I have only seen this problem on remote sites with T1 probs... But I have seen similar one way data issues (non voip) with half/full duplex switch settings.

Also... Check with your network folks and make sure there are no goofy firewall rules in place that could effect things.

You may also wish to have an audit done to make sure your network can support voip. voip VS data transmission is two diff worlds and amazingly, some networks just can't support it.

Zow

 

[MasterRacker]

We had a similar problem with an outlying site with a 3rd party managed T1. Their remote router had lost a routing statement. Return packets couldn't find their way out resulting in 1-way audio.

I doubt that's your exact problem since it's intermittent, but I agree with Zow. The starting point is to have your network folks do their thing.

_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[Regordmdew]

Another thing to check is network region and codec. I see mixed G711 and G729A codecs in use. What with all the transferring, this may be a red herring, but you should take a look to confirm.

 

[kabudoy]

As per network team switch port conected to the LSP sever is Auto not 100 full duplex.

 

[Mitch672]

kabudoy,ths could very well be your problem. AVAYA recomends that both sides be locked to "100MB FULL", many times if the switchport is set to "auto/auto', it results in a "100/Half" connecion. tell your network team to set the port to "100/FULL"

mitch


AVAYA Certified Specialist

 

[kabudoy]

Thanks guys for support will have it rectified.