Hi Elliott,

We were able to reproduce the issue last week and then unable to reproduce once 
the issue was identified and resolved. For this reason, along with customer 
feedback, we are confident the original issue had been fixed. The fix was to 
replace a faulty module in a gateway device.

We are looking into this issue and have engaged our voice engineering team for 
further investigation, it is being treated as a real and serious issue.

The impact to your customer base is understood and we are working on 
identifying and resolving asap.


Regards,

Roger Lienert | Manager Customer Assurance - Wholesale

M: +61 404 079 779   D: +61 2 8999 8226   E: 
roger.lien...@vocus.com.au<mailto:roger.lien...@vocus.com.au>
Support:: 1300 855 845 or +61 2 8117 5909  W: 
vocus.com.au<http://www.vocus.com.au/>
A: Level 12, 60 Miller Street, North Sydney, NSW 2060, Australia

[ite]<http://www.vocus.com.au/>




From: AusNOG [mailto:ausnog-boun...@lists.ausnog.net] On Behalf Of Elliott 
Willink
Sent: Wednesday, 30 January 2019 3:00 PM
To: ausnog@lists.ausnog.net
Subject: [AusNOG] New voice payload issues? Vocus QLD


Hi All,



After incident #20495093 
(http://status.vocus.com.au/view-incident.aspx?IncidentID=475) was resolved 
last week we have had consistent reports from multiple customers of one way 
audio for inbound calls to QLD DIDs on Vocus CTS.



One way audio is always the same (inbound call, customer reports they can't 
hear calling party but calling party can hear the customer. Calling party calls 
back and the audio stream is fine). At a guess 5 to 10% of calls are impacted.



Vocus NOC initially blamed 'mobile networks not being reliable' as our example 
calls were not land-line, then packet loss in our network after we provided 
land-line examples. I captured a faulting call at an edge switch facing them 
and Vocus is sending us an empty RTP stream (payload entirely made up of 0x54 
(g711.a idle?). The faulting calls behave the same from Vocus's Melbourne and 
Sydney SBC's and are isolated just to QLD in-dials so I'm somewhat convinced 
this is some sort of flow on effect of the incident last week.



In the interests of expediting a resolution has anyone else had similar issues? 
I've had a ticket open since Friday and Vocus are telling me nobody else has 
reported anything... It's slow progress.



Thanks,



Elliott
_______________________________________________
AusNOG mailing list
AusNOG@lists.ausnog.net
http://lists.ausnog.net/mailman/listinfo/ausnog

Reply via email to