No ringback tone when X-port covers to CAG.

[1Jumbo]

Customer has an Aura CM 6.2, S8300D in a G450. One of the main numbers routes in as a DID to an X-port station 2887. Station 2887 has coverage path 8 with the first coverage point as Cover Answer Group 1 set to 3 rings, second point is CMM (hunt 99). When calls ring in, the CAG members phones ring but the callING party does not hear any ringback.

I've been checking anything and everything I can think of and we still hear silence. Any ideas?

Thanks

 

[AvayaTier3]

are you calling station xxxx to station 2887 in the same g450?
Command: list trace station xxxx
Post results here

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

39 years Bell, AT&T, Lucent, Avaya
Tier 3 for 29 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[1Jumbo]

Hi Brett,

This is a stand alone system and the incoming call is a DID to X-port 2887 which immediately routes to cover path 8. The CAG is the first point and all you get is silence. Eventually, the CMM picks up. Here is the list trace:

LIST TRACE

time data

10:58:01 TRACE STARTED 09/14/2012 CM Release String cold-02.0.823.0-19721
10:58:08 Calling party trunk-group 1 member 23 cid 0x69c
10:58:08 Calling Number & Name 1xxxxxxxxxx NO-CPName
10:58:08 dial 2887
10:58:08 term station 2887 cid 0x69c
10:58:08 Alert cid 0x69c
10:58:08 Alert cid 0x69c
10:58:08 Alert cid 0x69c
10:58:08 G711MU ssff ps:20
rgn:1 [10.2.23.100]:59942
rgn:1 [172.25.1.1]:2052
10:58:08 G711MU ssff ps:20
rgn:1 [10.2.23.96]:40370
rgn:1 [172.25.1.1]:2050
VOIP data from: [172.25.1.1]:2050
10:58:19 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:12 WC:13 Avg:0
10:58:19 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [172.25.1.1]:2052
10:58:20 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:13 WC:5 Avg:0
10:58:20 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
10:58:28 no answer cid 0x69c
10:58:28 coverage-path 8 point 2 cid 0x69c
10:58:28 call-forwarding 7914
10:58:28 term trunk-group 99 cid 0x69c
10:58:28 call-forwarding 79141
10:58:28 route-pattern 99 preference 1 location ALL cid 0x69c
10:58:28 seize trunk-group 99 member 25 cid 0x69c
10:58:28 Calling Number & Name NO-CPNumber NO-CPName
10:58:28 Setup digits 9141
10:58:28 Calling Number & Name xxxxxxxxxx NO-CPName
10:58:28 Proceed trunk-group 99 member 25 cid 0x69c
10:58:28 Calling Number & Name NO-CPNumber NO-CPName
10:58:28 Setup digits 9141
10:58:28 Calling Number & Name 6052411234 NO-CPName
10:58:28 Proceed trunk-group 99 member 25 cid 0x69c
10:58:28 Alert trunk-group 99 member 25 cid 0x69c
10:58:28 active trunk-group 99 member 25 cid 0x69c
10:58:28 G711MU ssff ps:20
rgn:1 [172.25.1.2]:8000
rgn:1 [172.25.1.1]:2064
10:58:28 xoip options: fax:T38 modemff tty:US uid:0x50019
xoip ip: [172.25.1.1]:2064
10:58:34 idle trunk-group 1 member 23 cid 0x69c
10:58:36 TRACE COMPLETE station 2887 cid 0x0

Good hearing from you,

Lauri L

 

[osheros]

Looking at your trace, is the calling phone an IP phone? Can it otherwise get audio if you call a real station on that G450? It sounds like it's a talk-path issue but there's a lot of places to look. I'd first just call one of the people in the CAG and make sure you can hear each other. If that works, I'd explore firmware one the phone (esp if it's a 96x1), firmware on the G450 and service packs for CM 6.2 (now at SP3). In this case, I believe the G450 should be providing the ringback, assuming the calling IP endpoint is H.323 and not SIP. If the calling party is connected via a SIP trunk, even more reason to look at firmware the phone and gateway as some of the earlier releases of gateway firmware didn't support early media properly and thus no ringback.

Sorry I can't be more specific.

-Sam

 

[1Jumbo]

Thanks Sam.

The incoming call is a DID going to a digital station as an X port so no internal station is involved. We did try both an IP station and digital station (both as an X port) with the same result. The stations in the CAG all ring, anyone can pick up the call and there is good 2 way transmission once it is answered. The only thing that seems to be missing is the ringback to the calling party. After the rings to coverage point 1 time out, the voicemail answers.

The individual extensions in the CAG can be called directly on site or as DID numbers and there is ringback to the callING party.

I set up a remote access number and used that to dial the x-port station. Same result. I also set up a vector to ring the x-port, same result.

The trunking is ISDN PRI so SIP trunking should not be a factor here.

I will need to get back into the switch to see what the firmware is in the gateway and the modules. This was installed within the last few months so it likely is new firmware.

Thanks for the ideas.

 

[eltorodeoro]

Hi 1Jumbo... I am finding the exact same condition on a site I just turned up.

Did you ever find a resolution to this?

 

[1Jumbo]

Avaya has it as an escalation. They have been doing traces but we have not heard back from them for a while.

If I get a fix, I will post it here.

Thanks,

LL

 

[eltorodeoro]

are you running sp3? the core for this customer has not been patched yet, so just wondering if it's still buggy with the latest code.

 

[1Jumbo]

We have patch 19721

 

[hari2578]

Try this one!!!

Check if the option is set to "y" for Activate Answer Detection (Preserves SBA) On Final CCRON Cvg Point? y




display system-parameters coverage-forwarding Page 2 of 2
SYSTEM PARAMETERS CALL COVERAGE / CALL FORWARDING

COVERAGE OF CALLS REDIRECTED OFF-NET (CCRON)

Coverage Of Calls Redirected Off-Net Enabled? y
Activate Answer Detection (Preserves SBA) On Final CCRON Cvg Point? y
Ignore Network Answer Supervision? n
Disable call classifier for CCRON over ISDN trunks? n
Disable call classifier for CCRON over SIP trunks? n

 

[McVoIPin]

I have had a similar problem on an Avaya CM 6.0. We weren't getting ring back when a call was being transfered from a voicemail system at another site over SIP. I had to change a parameter on the SIP trunk-group (page 4) "Convert 180 to 183 for Early Media?" to yes to get it to work properly. Hope this helps. Drove me nuts for months!

 

[1Jumbo]

Thank you hari2578 and McVoIPin for your suggestions. I would not have thought of either one.

However, this particular customer has neither CCRON activated nor SIP trunking. (VM is via H.323.)

Avaya still has this as an escalation and has not come up with a solution so far.

Thanks again. LL

 

[1Jumbo]

Update: Avaya responded that it is a known issue that will be fixed in the February 2013 service pack for 6.x.

Thanks for all of your input.