Folks, as you see I have become involved in a CP 150 using all four ports and 4 stations (313,314,315 & 316). Sometimes when call comes in and through CCR Tree #1, callers will get "Invalid Number". It seems to be very intermitent but annoying. Ext 313 is programmed in the system as the voice mail port from the 0x32. The question is how should the other stations (314, 315 & 316) be treated: 1) using Busy forward (in the 0x32)to 313 or maybe in a hunt group with the other exts. 2)Or, does the CP 150 exclusively handle the routing of the calls from 313 thru 315? I've tested both the 0x32 exts and checked to be sure the 150 is seeing the stations (all 4 LEDS are lit). What am I looking over please?
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Norstar 0x32 w/ Call Pilot 150 1
- Thread starter ORPG
- Start date
curlycord
Programmer
Best to put the issue in the subject line for future.
Press F985
Note the DN that appears, In your case probably 313 was displayed
Now forget the rest of the DN's you mentioned for the rest of your entire telecom nerdy life....that is s how they should be treated.
The call comes in to the Table first, after the Table greeting is heard (if recorded in AA/Grtg/Grtg) it will then go to the Tree greeting if it is enabled.
"Invalid Number" would mean the caller tried to call a DN that does not exist.
You should describe at exactly what point they get that greeting or if the caller is pressing anything.
ie such as what you might be trying to say?:
Caller calls in and hears Table 1/Greeting 1, then CCR 1/Path 0 greeting and user then hears "Invalid Number" without even entering in a number.
If they are actually pressing a digit then what is the digit they are pressing and what is that digit (Path) programmed to do?
We cannot hear nor see so it would be difficult to answer especially if we do not know how you programmed the Callpilot.
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
Press F985
Note the DN that appears, In your case probably 313 was displayed
Now forget the rest of the DN's you mentioned for the rest of your entire telecom nerdy life....that is s how they should be treated.
The call comes in to the Table first, after the Table greeting is heard (if recorded in AA/Grtg/Grtg) it will then go to the Tree greeting if it is enabled.
"Invalid Number" would mean the caller tried to call a DN that does not exist.
You should describe at exactly what point they get that greeting or if the caller is pressing anything.
ie such as what you might be trying to say?:
Caller calls in and hears Table 1/Greeting 1, then CCR 1/Path 0 greeting and user then hears "Invalid Number" without even entering in a number.
If they are actually pressing a digit then what is the digit they are pressing and what is that digit (Path) programmed to do?
We cannot hear nor see so it would be difficult to answer especially if we do not know how you programmed the Callpilot.
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
- Thread starter
- #3
Curlycord,
Yup. Checked all that before I made the post.
TREE 1
GREETING 1
CCR 1 ENABLED
There is a Path 0 - intro
Path 1 goes to an extension
Path 2 to another
Path 3 to another
Path 4 to another
That's all the paths being used.
Business is open and the operator available.
Ocassionaly when the caller presses either 2 or 3 they will get the "Invalid Number" announcement.
Yup. Checked all that before I made the post.
TREE 1
GREETING 1
CCR 1 ENABLED
There is a Path 0 - intro
Path 1 goes to an extension
Path 2 to another
Path 3 to another
Path 4 to another
That's all the paths being used.
Business is open and the operator available.
Ocassionaly when the caller presses either 2 or 3 they will get the "Invalid Number" announcement.
curlycord
Programmer
Ok good, so now we know the issue is with Path 2 or 3.
Check the Forward Busy on those two DN's and make sure they are not going to a DN that does not exist.....or those ones your supposed to forget about, lol
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
Check the Forward Busy on those two DN's and make sure they are not going to a DN that does not exist.....or those ones your supposed to forget about, lol
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
- Thread starter
- #5
Well, I checked to be sure they were not forwarded to unassigned DN's. They weren't. I did find where they were getting creative with the Operator's sign-in. Not sure what if anything that had to do with the problem. I'm going to watch it for a few days and get back to you.
Thanks Curlycord!
Thanks Curlycord!
- Thread starter
- #7
phoneguy427
Technical User
Do you have problems just dialing extensions through the AA. What software version is the Call Pilot? There where known touch tone issues with older software releases. Just a thought.
curlycord
Programmer
I agree, call those 2 DN's direct a few times.
And that 2.X had DTMF issues.
If it is in fact 3.0 or lower it would be worth borrowing a 3.1 and upgrade the existing card to 3.1 via the front slot.
Check Touch Tone Gate, should be set to None.
Make sure nobody has Answer Keys for any of those 2 DN's too.
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
And that 2.X had DTMF issues.
If it is in fact 3.0 or lower it would be worth borrowing a 3.1 and upgrade the existing card to 3.1 via the front slot.
Check Touch Tone Gate, should be set to None.
Make sure nobody has Answer Keys for any of those 2 DN's too.
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
- Thread starter
- #10
Guys...the latest:
I can call the DN's direct
S/W 3.1
TTG No
The problem is thru the AA; in the CCR Tree 1 Path 2, 3 & 4 sometimes get an "Invalid Number" recording.
The DN for the Call Pilot is 313
314, 315 & 316 are the other DN's on the CP
When I look at 313 in Maintenance it shows Busy all the time.I disabled it and calls are flowing thru the AA fine (so far).
Comments please?
I can call the DN's direct
S/W 3.1
TTG No
The problem is thru the AA; in the CCR Tree 1 Path 2, 3 & 4 sometimes get an "Invalid Number" recording.
The DN for the Call Pilot is 313
314, 315 & 316 are the other DN's on the CP
When I look at 313 in Maintenance it shows Busy all the time.I disabled it and calls are flowing thru the AA fine (so far).
Comments please?
- Thread starter
- #11
- Thread starter
- #12
Folks, upon reading other threads, I find there may be a situation on the trunk cards. They changed from ATT as their POTS supplier and went to Spectrum. Should the trunks be set to short CO or short PBX....maybe? I read that sometimes DTMF can produce a echo and screw up the transfer?
-
1
- #13
curlycord
Programmer
I can call the DN's direct"
We know you can call the DN's, but the post was for you to test those 2 DN's by calling them direct several times to see if you can simulate the issue.
If it work fine then most likely it is not a set issue but rather the Callpilot or the lines.
But to make this even more confusing you now say it's Paths 1, 2, 3 and 4, not just 2 and 3?
I would say also test each line several times and see if you can narrow it down to one line or all.
Ports being busy have nothing to do with the issue, they will busy a lot if you are full time AA....and I hope you re-enabled it back.
F982 Operator status or Call Forward also have nothing to do with the issue, but since you mentioned it if the receptions wants to forward their phone to their backup person then that is a good option.
Other options would be Service Modes or Hunt Groups.
F982 is to tell the caller that when 0 is pressed the operator will not be available, it then dumps the caller back to AA or into the general mailbox (I forget circumstances)
F982 can also tell Callpilot to answer the lines.
"rather than going into F982 and chays fdo ut this way?anging it there? She says she has alw"
Take 2 two low dose aspirins right away and call the doctor.
Try all those CO/PBX settings and test, I might start with CO Long but others might chime in since I have only had to change it once in my time.
![[clown]](/data/assets/smilies/clown.gif "[clown] [clown]")
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
We know you can call the DN's, but the post was for you to test those 2 DN's by calling them direct several times to see if you can simulate the issue.
If it work fine then most likely it is not a set issue but rather the Callpilot or the lines.
But to make this even more confusing you now say it's Paths 1, 2, 3 and 4, not just 2 and 3?
I would say also test each line several times and see if you can narrow it down to one line or all.
Ports being busy have nothing to do with the issue, they will busy a lot if you are full time AA....and I hope you re-enabled it back.
F982 Operator status or Call Forward also have nothing to do with the issue, but since you mentioned it if the receptions wants to forward their phone to their backup person then that is a good option.
Other options would be Service Modes or Hunt Groups.
F982 is to tell the caller that when 0 is pressed the operator will not be available, it then dumps the caller back to AA or into the general mailbox (I forget circumstances)
F982 can also tell Callpilot to answer the lines.
"rather than going into F982 and chays fdo ut this way?anging it there? She says she has alw"
Take 2 two low dose aspirins right away and call the doctor.
Try all those CO/PBX settings and test, I might start with CO Long but others might chime in since I have only had to change it once in my time.
________________________________________
=----(((((((((()----=
Toronto, Canada
Add me to LinkedIN
- Thread starter
- #14
Hey Curlycord! As usual and as in past posts, you always seem to bring a chuckle to readers. I needed it too. I didn't realize I was all thumbs until I read what I had posted. (Old guy thing!)
Anyway, the problem is no longer a problem. After the AA came in over the incoming calls and conversations and the CP DN stayed "busy" in maintenance, I did the ultimate! Reboot! The CP died! I'm replacing it tomorrow. FYI and all, the customer tested their emergency generator earlier this week. (I just received the glad tidings this afternoon.)And as most of us know, emergency generators and their lack of proper bonding/grounding is tough on electronics.
Again THANKS Curlycord and the others to have posted to this thread. I most certainly appreciate it!
ORPG (Ole' Retired Phone Guy)
Anyway, the problem is no longer a problem. After the AA came in over the incoming calls and conversations and the CP DN stayed "busy" in maintenance, I did the ultimate! Reboot! The CP died! I'm replacing it tomorrow. FYI and all, the customer tested their emergency generator earlier this week. (I just received the glad tidings this afternoon.)And as most of us know, emergency generators and their lack of proper bonding/grounding is tough on electronics.
Again THANKS Curlycord and the others to have posted to this thread. I most certainly appreciate it!
ORPG (Ole' Retired Phone Guy)
pccsipoffice
Technical User
Drop the 2 or the 3 and dont use it. It is too close to extension numbers.
Cell phone connections.
Cell phone connections.
- Status
Similar threads