01-25-2012 10:37 AM - edited 03-21-2019 05:15 AM
I have opened a TAC case for this, but wanted to see if anyone has seen this before.
UC520 with a NexVortex SIP trunk. Out of nowhere, external calls into the system cannot leave voicemail messages. The AA and VM greetings all work fine, you get the beep to record your message, record, then hangup just like normal. The issue is that the message never actually saves to the mailbox, and the user never gets the message. Internal calls work fine, it's just external calls that can't leave a voicemail.
I am wondering if it's a change or issue at NexVortex's end, since nothing changed on my end. Troubleshooting this issue i have already updated to the latest support pack, RMA'd the entire UC520, and reconfigured CUE from scratch. So it doesn't appear to be a hardware issue. The only thing that hasn't changed is my CME config, but again, it's been stable for a year or so.
I am attaching part of the CUE messages.log, it seems to have lots of errors.
01-25-2012 04:13 PM
Hi MR "C"
You know there always seems to be an issue with NexVortex, the amount of posts I see on here that relates to them is crazy, makes me wonder if they have a poorly configured Asterix box being used as their SBC ???
Anyway, I wonder if it is a Codec related issue... So would you be so kind as to make a slight modification to your SIP trunk please? I would like you to change the Codec to G.711u and do some tests... If it works then it is the same problem as all the other issues raised, no Codec re-negotiations taking place midway through the stream as I have noticed this can change straight after the greeting if you watch the debugs
Please let us know how you go...
Cheers,
David.
01-25-2012 04:43 PM
G711 is already my highest preference.. would taking g729 out completely make a difference?
voice class codec 1
codec preference 1 g711ulaw
codec preference 2 g729r8
dial-peer voice 3000 voip
description 1209XXXXXXX
translation-profile incoming 1209XXXXXXX-BG_Called_4
session protocol sipv2
session target sip-server
incoming called-number 1209XXXXXXX
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
dtmf-relay rtp-nte
ip qos dscp cs5 media
ip qos dscp cs4 signaling
no vad
dial-peer voice 1025 voip
corlist outgoing call-national
description **CCA*North American*Long Distance**
translation-profile outgoing PSTN_Outgoing
preference 1
destination-pattern 91[2-9]..[2-9]......
session protocol sipv2
session target sip-server
voice-class codec 1
voice-class sip dtmf-relay force rtp-nte
dtmf-relay rtp-nte
ip qos dscp cs5 media
ip qos dscp cs4 signaling
no vad
01-25-2012 04:51 PM
Just for the sake of testing.. Yes
But put it back straight away
Cheers,
David.
01-25-2012 04:58 PM
no change.
01-25-2012 05:07 PM
ARGH!!!! CR*P
Ok Question time
I'll have to work on this basis to get my bearings on your system... Something is for sure a miss with the configuration if you have even replaced the unit.
If you can post both the CLI capture of the CME and CUE that would be awesome, please post them as an attachment and with sensitive info removed.
Cheers,
David.
01-25-2012 05:52 PM
It's on the newest now, I upgraded after the troubles began to see if it would fix. 8.2.0? I was on something like 7.0.2 prior.
It was initially setup a few years ago, so it's probably a mixture of CLI and CCA. Since the re-config, I let CCA take over some of the config, so the DIDs, hunt-group, etc. is all redone by CCA now.
01-25-2012 06:11 PM
OK...Thanks
I wont be able to do much untill I get in front of my computer, too much trouble to try and do it on the tablet.
Will get back to you later on
Cheers,
David.
01-26-2012 08:43 PM
Looks like it was Nexvotex after all. I deleted and re-added my trunk, and it appears to be working now. As I mentioned, nothing had changed in my config in months (or even years). They must have changed or updated 'something' on their end, who knows.
Anyway, here is the resolution:
1. Add the nexvortex sip trunk template XML into CCA and configure the trunk (https://supportforums.cisco.com/docs/DOC-21472)
2. remove the voice source-group commands (nexvortex does not work with the default CCA source-group commands)
config t
no voice source-group CCA_SIP_SOURCE_GROUP_CUE_CME
no voice source-group CCA_SIP_SOURCE_GROUP_EXTERNAL
3. reconfigure your incoming DIDs/AA#s
01-26-2012 08:45 PM
For some reason I cannot mark my own post as the correct answer? so I put [Solved] in the thread title.
Thanks for your help David.
01-26-2012 09:15 PM
Hi Champ,
I did have a look at your configuration at about 5am this morning, but I have been flat out today with back-2-back meetings and only just got back into the office.
I was going to say there was nothing wrong with the configuration of the system outside of some unusual CLI configuration, but they are working so I was not too worried about looking further at them (And not related to the SIP either).
I am glad it is solved for you... And yes you cannot mark your own post as Solved but you can make someone else's as "Answer" but that would mean you would have to mark one of mine as answered and I am not about to blow my own trumpet because I didn't get an answer right LOL.
Cheers,
David.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide