Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Connection problems

Status
Not open for further replies.

auskar85

Technical User
Dec 5, 2012
135
LT
Hi,
We have CM 4.0 in S8400 media server. Recently calls from IP phone to IP phone began to drop.
We upgraded MedPro firmware version. Then every third call began to fizzle (one party hears fizzle, other hears nothing). We tried to change MedPro board, upgraded SIPI board firmware, but the problem disappeared after we disabled AES encryption on ip-codec-set.
Strange is that list measurements ip dsp-resource hourly shows In Reg Peg counting after working hours. Seems like MedPro is alocating its resources for something.
Has anybody encountered similar problem?
 
are these phones traversing network reasons or in the same reason , or are they in the same region , there was an issue previously where aes turned off fixed an issue i think on cm3 but that involved firmware upgrades , can you post a list trace of a non working call .....what seems strange is that you are getting degradation rather than it working or not but a list trace between phones would be good to see with AES turned on.






APSS (SME)
ACSS (SME)
ACIS (UC)
 
IP stations are in the same network region, but they are not using direct IP - IP.
Here is trace:


LIST TRACE

time data

13:16:25 Calling party station 2673 cid 0x242
13:16:25 Calling Number & Name 2673 Alvy
13:16:25 dial 2881
13:16:25 ring station 2881 cid 0x242
13:16:25 G711MU ss:eek:n ps:20 rn:1/1 172.30.8.251:24694 172.30.1.236:3820
13:16:31 active station 2881 cid 0x242
VOIP data from: 172.30.1.236:3820
13:16:35 Jitter:2 2 2 2 1 0 0 0 0 0: Buff:13 WC:10 Avg:1
13:16:35 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: 172.30.1.236:3816
13:16:36 Jitter:0 0 1 2 2 2 2 2 2 2: Buff:12 WC:13 Avg:1
13:16:36 Pkloss:* * 0 0 0 0 * 0 0 0: Oofo:0 WC:254 Avg:0
 
Getting some jitter there , wow on network why not try direct ip to ip also mu711 may be causing issues on your codecs , try g729, also the *** on the packet loss meanss that cm can't even read a loss that high , I'm thinking qos and voice and data vlan is your issue ,,,,how about a trace with an actual 30 sec conversation.[pre][/pre]...still think network though

APSS (SME)
ACSS (SME)
ACIS (UC)
 
We didn't try direct IP - IP, because phones are in different networks and these networks may be unreachable directly (no routes defined).
The strange thing is that without encryption there is jitter and packet loss as well.
 
Are the phones using the same medpro ?? if so can you force them to use a different medpro to see if follows the medpro.But this looks like heavy load on the network due to the jitter and packet loss..... and hang on further up you said the phones are in the same region and now you say they are in different network regions??

APSS (SME)
ACSS (SME)
ACIS (UC)
 
We tried different MedPro. The same problem.
Phones are in the same network region, they are using the same MedPro, but phones are in different network subnets, so there can be no direct route to each subnet.
 
ahh i see on that trace i would be worried about the ** packet loss as that means CM cant even read the amount as its too high , also jitter is quite prevalent so i would be looking at qos diffserve and the 802.1p/q settings on your network switches ...as this seems more network related than CM ... just out of interest what are the codec sets used between regions i can see g711mu but are any others available for the sets to use.... but as i say i think this id qos related

APSS (SME)
ACSS (SME)
ACIS (UC)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top