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!

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

No audible ringback from PRI using call forward unconditional

Status
Not open for further replies.
mjroam

mjroam

Vendor
Jan 16, 2004
48
US
Recently upgraded a 406V2 to 5.0.

They have no Twinning/Mobility licenses but they have multiple virtual users who's extensions are simply call forwarded unconditionally to their cell phones.

Seemed to work fine with 3.2(69).
Now no matter how the call is originated, DID, internal or transfer there is no audible ringback from the CO.
There is only silence until the cell phone user answers or
their mobile voicemail answers.

Settings and attempted fixes.

-Turned off MOH
-Used multiple destination numbers to eliminate carriers.
-No Answer time is set for 30.
-Users VM disabled
-If you call cell # directly from IPO the ringback tone is present.

Interesting enough if I turn on User\Announcements using only 1st announcement and Post Announcement Tone set to ringing it works great except the default 1st queing announcement is not approriate. Ironicly if I set up Queued start point for the user in VM pro it will not work.

I know someone will be unable to refrain from telling me that this is what Mobility Licenses are for. But please don't waste you're time. The customer has already been informed and quoted even though they have a valid point. "If it worked before the upgrade it should work now"

Please reply if you have run into this.

Thanks
Mike
 
Sort by date Sort by votes
Why did they upgrade and what version is it upgraded too.
Ringback has nothing to do with twinning.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
Better try 5.0.22

CQ104476|No Ringback tone is heard when receiving Alerting from Cisco Switch on H323 trunk|5.0.20|SP_RELEASE_4Q10_5.0|3-Available|5.0.203104

CQ40098|No ringback on calls on SIP trunks when account code entered|5.0.8|SP_RELEASE_3Q10_5.0|4-Proven|5.0.087203

CQ44984|No ringback indication if a user fwds their calls off prem|5.0.20|SP_RELEASE_3Q10_5.0|3-Available|5.0.202603

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Upvote 0 Downvote
TLpeter Why do you respond to a post if you have nothing to offer.
 
Upvote 0 Downvote
Bas1234
Thanks for the reference. It looks like the last one specifically applies. I'll look into it and post any results.

Thanks

Mike
 
Upvote 0 Downvote
>Why do you respond to a post if you have nothing to offer.

He actually asked a very pertinent question - which you didn't answer.

He also confirmed that this issue is nothing to do with twinning.

It seems to me that you need to show some appreciation for the help that you receive from this site - something that you haven't done in last 6 years.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Upvote 0 Downvote
look at tlpeter's stats and see how many stars he has been given for being helpful and the amount of replies he has and how many stars you have given out for receiving help in case you have any questions what Matt means

But maybe we are a bit to sensitive an this sunny Monday.
Cheers


Joe W.

FHandw., ACSS

insanity is just a state of mind
 
Upvote 0 Downvote
I will ask again :)

Why did they upgrade from 3.2 to 5.0 ?
There must be a reason for that.

Also bas1234 shows you a CQ with your problem in it.
So that is why i asked which version did they upgrade to ?

I also confirmed you that mobility license will not solve the problem.

So hopefully you will answer my questions :)
( i am in a good mood, i am having a holiday on a nice island with a nice beach)

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.
 
Upvote 0 Downvote
I'm also having my holiday, and still hanging around on here...:)

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Upvote 0 Downvote
you guys are sick
I was on holidays the last 3 weeks and I was barely here but you are here more than usual it seems.
Get a hobby and I don't mean a new motorcycle bas :p

Joe W.

FHandw., ACSS

insanity is just a state of mind
 
Upvote 0 Downvote
My apologies to you tlpeter. My response was unfair.

I am aware of your longstanding support and contributions to this and other forums.

Also consider me sufficiently humbled by the posts from your supporters.

To answer your questions they upgraded from 3.1 to 5.0(20) enable support for new 5610 phones along with other new features they wish to explore. In addition to this being the last core release that didn't require new licenses.

After confirming CQ44984 in the caveats I have scheduled an upgrade to 5.0 (22), which appears to have the fix. I will post the results.



 
Upvote 0 Downvote
It appears after checking TB 122 CQ44984 is not covered in the resolved issues even though it was targeted to be resolved in 5.0 3Q release.

Following from KB\Caveats

CQ44984

No ringback indication if a user fwds their calls off prem

5.0.20

SP_RELEASE_3Q10_5.0


3-Available

5.0.202603

I take this means it was not resolved and I'll have to wait or use a Private Build?
 
Upvote 0 Downvote
I'm wondering if this is the same issue worded differently?CQ99790
No ringing tone heard when calling a User who has forwarding Off switch via external ISDN when alerting.

It is resolved in 5.0(22)
 
Upvote 0 Downvote
>No ringback indication if a user fwds their calls off prem

>No ringing tone heard when calling a User who has forwarding Off switch via external ISDN when alerting

It is possible that the same issue has multiple CQ numbers (it has been known), but I suspect in this case they are different - as one mentions ISDN, which suggests that this is an ISDN messaging / interetation issue.

of course, I am only reading between the lines....

Good luck with the upgrade - it might be worth your while getting the private build from your distributor too and holding that in reserve....

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Upvote 0 Downvote
FYI Upgrade to 5.0(22) had no effect.
Still no ring back from PRI.
Did notice the intermittant appearance of the following service alarm
[Attempt to use a feature for which no license is intalled.
License Type: IP500 Universal PRI (Additional Channels)]

Looks like I'll have to go for a private build.
 
Upvote 0 Downvote
I just put in 2 new systems each IP500V2 6.0.14 and it looks like this issue still exists (or has come back).

 
Upvote 0 Downvote
Thanks for the post Baldwincl. Going to 6.0 was one of the recommended solutions from dealer support.

We are still working on getting the private build.

In the mean time I created a temporary half a!!!d solution using Announcements.
I was able to do this only because they don't use queueing or announcements anywhere else since it changes the standard
"I am afraid all the operators are busy at the moment but please hold and you will be transferred when somebody becomes available" message.

The DID or transfered caller hears 8 seconds of silence, 1 ring, "Please hold while we try to connect you". and silence until the far end answers. Ussually within 6 secs.
It seems to keep them from disconnecting.


In Manager
1.) Enabled Announcements for the external callforwarded Users.
2.) Set 1st Announcement delay to 8 secs.
3.)Unchecked second announcement and repeat last announcement.


The following was done in
C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\WAVS\en

2.)Temporarily changed the default 1st Announcment by renaming svm_18.wav to svm_18bak.wav
3.)Copied and pasted aa_04.wav and renamed the copy to svm_18.wav

FYI Neither the Ringing or MOH option in the User/Announcement tab made any difference on this particular system.

I know this is real Rube Goldberg stuff but the customer is satisfied with it for the time being while we wait for a new build.





 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

smartedge1
  • Locked
  • Question
lnbound calls from pri showing as External call on AVAYA phone
Replies
5
Views
529
smartedge1
smartedge1
DiscLight
  • Locked
  • Question
9.1 PRI Forwarding group calls to a cell 3
Replies
2
Views
791
Menniss
Menniss
Avaya_Enjoyer
  • Locked
  • Question
Using a virtual station to record a call?
Replies
2
Views
285
Avaya_Enjoyer
Avaya_Enjoyer
sbankscharles
  • Question
Scheduled Call Forwarding Cancelling Out
Replies
1
Views
116
bason
bason
rsv23
  • Locked
  • Question
using a pin code to transfer a call in VMpro
Replies
6
Views
312
Menniss
Menniss

Part and Inventory Search

Sponsor

Back
Top