Jump to content

CobaltFlux

Members
  • Posts

    8
  • Joined

  • Last visited

CobaltFlux's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I installed the audio_en files. You hear the instructions about the voicemail including "After the tone please leave your message." There is no tone, though. Perhaps it is missing the beep file. I'll check for it.
  2. I recently upgraded from an appliance to a linux system. When I did so, I used the back up and restore settings to copy all the setting on to the new system. I am running version 3.4.0.3201 (Linux) I have an issue where if someone calls and wants to leave a message they hear the options, but at the end of the options there isn't a beep to mark when to start recording. It is quite frustrating for callers. The missing beep also shows up when you want to record you name or a personal greeting for your voicemail. Any ideas, on the cause and a possible fix?
  3. I tried the things you suggested except for the FXO signal booster (which I'm not sure exactly what kind of device you mean) and I still do not have Caller ID. I put off trying to fix it for a while as it isn't completely necessary. However, I have some time now and would like to see if we cam figure something out. In my tests lately, I can only get the caller id to work after boot and not again. However, I noticed in the PSTN logging that there is a line about Caller id. After every call hangs up the line "PSTN: enable_callerid 0" comes up. Is this disabling the caller id after every call? If so, it would explain why it works the first time if the default of callerid is enabled. Any ideas?
  4. I have tried playing with the input gains to no avail. I have yet to buy a signal booster. However, while I was playing with the input gains, I noticed that everytime I restarted the system the Caller-ID worked for the first call. After that, it seems that almost every call is missing the Caller-ID. Do you think there may be some other issue going on? I was having some issues with cross-talk that I cleared up almost completely by rerunning a couple of cables but it didn't seem to clear up the Caller-ID problem.
  5. We are the 4th unit in a row of buildings and the junction to the phone company is in the first unit. There is probably about 100 feet from the appliance to junction in our unit then another 200-300 feet to a second junction box and finally another 100-200 feet of cable to the junction where it connects to the phone company's cable. So, I wouldn't be surprised if we have some poor wiring. We had issues getting our T1 line set up and we have had problems with our DSL line and some coss-talking with an unknown line (not one of ours) in the past. Our phone company is Qwest. I set the log to high and I'm not seeing anything about the Caller-ID (unless it receives the caller-ID). I have turned off logging on everything but IVR events, trunk events, and PSTN Gateway events. Here is what the log looks like when the Caller-ID works: [3] 2008/05/26 12:43:32: PSTN: Channel 0 going to RING [5] 2008/05/26 12:43:35: PSTN: eVAPI_CALLER_ID_DETECTED_EVENT [5] 2008/05/26 12:43:35: PSTN: Received on 0: DATE:0526, TIME: 1243 [5] 2008/05/26 12:43:35: PSTN: Received on 0: Caller-ID 801xxxxx52 [5] 2008/05/26 12:43:35: PSTN: Received on 0: Name COBALT FLUX INC [5] 2008/05/26 12:43:35: Identify trunk (IP address/port and domain match) 1 [5] 2008/05/26 12:43:35: PSTN: Response code: 100 [7] 2008/05/26 12:43:35: Received call from cell phone 801xxxxx52 [5] 2008/05/26 12:43:35: PSTN: Response code: 200 [5] 2008/05/26 12:43:35: PSTN: RTP destination=100007f [5] 2008/05/26 12:43:35: PSTN: RTP destination=56052 [5] 2008/05/26 12:43:35: PSTN: RTP OOB codec=101 [6] 2008/05/26 12:43:35: PSTN: Start call on 0 [5] 2008/05/26 12:43:35: PSTN: Channel 0 goes offhook [3] 2008/05/26 12:43:35: PSTN: Channel 0 going to TALKING [5] 2008/05/26 12:43:35: PSTN: Country Code set to 64 [5] 2008/05/26 12:43:35: PSTN: Tone Detection set to 0 [5] 2008/05/26 12:43:35: PSTN: Response code: 200 [5] 2008/05/26 12:43:40: PSTN: Received LoopInterrupt (remote hung up) signal on channel 0 [3] 2008/05/26 12:43:40: PSTN: Channel 0: Hangup [5] 2008/05/26 12:43:40: PSTN: Channel 0 goes onhook [5] 2008/05/26 12:43:40: PSTN: enable_callerid 0 [3] 2008/05/26 12:43:40: PSTN: Channel 0 going to GO_ONHOOK [5] 2008/05/26 12:43:40: PSTN: Response code: 200 [3] 2008/05/26 12:43:41: PSTN: Channel 0 going to IDLE no caller-id: [3] 2008/05/26 12:33:37: PSTN: Channel 0 going to RING [3] 2008/05/26 12:33:42: PSTN: Channel 0 going to NO_RING [3] 2008/05/26 12:33:43: PSTN: Channel 0 going to RING [5] 2008/05/26 12:33:43: Identify trunk (IP address/port and domain match) 1 [5] 2008/05/26 12:33:43: PSTN: Response code: 100 [7] 2008/05/26 12:33:43: Attendant: Goto night service 701 [5] 2008/05/26 12:33:43: PSTN: Response code: 200 [5] 2008/05/26 12:33:43: PSTN: RTP destination=100007f [5] 2008/05/26 12:33:43: PSTN: RTP destination=50492 [5] 2008/05/26 12:33:43: PSTN: RTP OOB codec=101 [6] 2008/05/26 12:33:43: PSTN: Start call on 0 [5] 2008/05/26 12:33:43: PSTN: Channel 0 goes offhook [3] 2008/05/26 12:33:43: PSTN: Channel 0 going to TALKING [5] 2008/05/26 12:33:43: PSTN: Country Code set to 64 [5] 2008/05/26 12:33:43: PSTN: Tone Detection set to 0 [5] 2008/05/26 12:33:43: PSTN: Response code: 200 [5] 2008/05/26 12:33:53: PSTN: Received LoopInterrupt (remote hung up) signal on channel 0 [3] 2008/05/26 12:33:53: PSTN: Channel 0: Hangup [5] 2008/05/26 12:33:53: PSTN: Channel 0 goes onhook [5] 2008/05/26 12:33:53: PSTN: enable_callerid 0 [3] 2008/05/26 12:33:53: PSTN: Channel 0 going to GO_ONHOOK [5] 2008/05/26 12:33:53: PSTN: Response code: 200 [3] 2008/05/26 12:33:54: PSTN: Channel 0 going to IDLE If it is a cable related issue then it will take some time to fix. I can replace the cable inside our building but I will have to ask the landlord about the rest of it. In the mean time, is there a way for a caller to get Direct Inward Access like that provided when it recognizes your cell phone number?
  6. Using the PSTN FXO lines it seems that our CS410 only picks up the Caller ID sometimes. I have been testing it with my cell phone (trying to get the special autoattendant to pick up). I had this issue with 2913 and now I just updated to 2914. It seems that after a reboot it will pick up the Caller ID at least once. Could this be a problem with my analog lines? Or is there some setting I am missing? I apologize. I'm not trying to be a nusance here, just trying to get the most out of the system.
  7. That took care of the issue. It is now pulling times correctly and setting service flags at the right times. Thank you. However, now I have a different issue (though this might not be the right place to post it). When an extension picks up an incoming call, the auto attendant plays during the conversation. My secretary told me that on an incoming call today it started playing a few moments after she answered the phone. I have had it happen to me as well. I answered the phone, the caller was there and it played the auto attendant message. We have a recorded message for the autoattendant I'm thinking that the caller is hitting more keys then they need to but it is difficult to tell. I asked my secratary to let me know if it happens again immediately so I could save the log from the call.
  8. I just purchased the CS410. I updated it to the firmware to the latest version aviable at the time. Currently running 3.0.0.2913. The time on the appliance is always incorrect. I have tried logging in and pinging the NTP server and I don't get a response. (The DNS resolves because my Small Business Service is also our DNS server but no response back). Any suggestions?
×
×
  • Create New...