Announcement

Collapse
No announcement yet.

Way2Call Problems

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #31
    Try updating to build 39 of HSP and see if the problem is still there.
    -Rich

    HomeSeer Technologies LLC
    💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

    Comment


      #32
      I seem to be good w/ HSP build 39. Soundcard is selected as playback/recording device and as wav playback device. Audio is being played through the phone and dialing is working. Thanks Rich.

      Henry

      Comment


        #33
        Rich,

        Build 39 seems to fix the problem of external calls also being answered as internal when Options->Modem->Internal Answer is enabled.

        Now, the last problem I seem to be having is that internal calls are always answered regardless of the setting of Options->Modem->Internal Answer. Not much of a problem for me since I do want internal calls answered, but I thought you should know.

        Thanks!

        Comment


          #34
          I think I'm down to one final error. On calls that show as "unknown" or "unavailable" w/ my other CID devices or software. HSP/hi-phone is showing the following in the log.
          7/13/2002 10:28:29 AM: Raw CID data: 80100108303731333130323708014F04014F
          7/13/2002 10:28:29 AM: RAW CID 1 Date/Time: 07131027
          7/13/2002 10:28:29 AM: RAW CID 8 No Name: O
          7/13/2002 10:28:29 AM: RAW CID Unknown: O
          7/13/2002 10:28:29 AM: Handling caller ID
          7/13/2002 10:28:29 AM: So far, no match, call has CID, but is not private or out-of-area, using default handling ...
          7/13/2002 10:28:29 AM: HSP is not set to announce unknown callers
          7/13/2002 10:28:29 AM: Notifying HS of CID available
          7/13/2002 10:28:29 AM: Notifying HS of event type: 4 DTMF:
          7/13/2002 10:28:29 AM: Line_OnError: Line: 1 LINEERR_INVALCALLHANDLE

          Not sure if it's a HSP or a driver error.

          Henry

          Comment


            #35
            What is the problem? The "O" indicates out-of-area and is controlled by the out-of-aread address book entry.

            -Rich

            HomeSeer Technologies LLC
            💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

            Comment


              #36
              The log shows:
              7/12/2002 6:22:24 PM: Raw CID data: 80100108303731323138323108014F04014F
              7/12/2002 6:22:24 PM: RAW CID 1 Date/Time: 07121821
              7/12/2002 6:22:24 PM: RAW CID 8 No Name: O
              7/12/2002 6:22:24 PM: RAW CID Unknown: O

              In the raw CID data, the last two bytes indicate a single charater 01, then 4F "O". The third line of the parsed CID data includes the 01 as part of the number. The log show a square preceding the "O", but the post is dropping it. It fails the CID matching function. I tried adding an entry with "O" in the callerid matching/blocked text field, but the matching won't work for that either. My other CID devices report this type of call as "unknown", or "no name" "no number. My received calls are normally parsed as:

              RAW CID 1 Date/Time: "time"
              RAW CID 7 Name: "name"
              RAW CID 2 Number: "number"

              I'm not certain if HSP is parsing the CID data correctly, or should the number display as:
              RAW CID 2 Number: O instead of
              RAW CID Unknown: 'square'O

              Henry

              Comment


                #37
                I keep getting "excuse me you have an incoming call, press *9...." message when I call into my phone and my outgoing message is being played. Any ideas as to what might be causing this?
                KR

                Comment


                  #38
                  Send me your hsphone.log file that recorded this, and I'll have a look at it. It should only do this if the inhouse handset is off-hook, and an incoming call comes in.

                  -Rich
                  rjh@homeseer.com

                  HomeSeer Technologies LLC
                  💁‍♂️ Support & Customer Service 🙋‍♂️ Sales Questions 🛒 Shop HomeSeer Products

                  Comment


                    #39
                    Hi Rich
                    Attatched is the log file from HSPhone.
                    Strangely, it made the false incoming call alert BEFORE it played the O/G message. Usually it does it during or near the end of the O/G message. Hope you can help.
                    Thanks.
                    KR

                    Comment


                      #40
                      Just an update. Latest build of HSP is parsing "out of area" calls correctly.

                      Henry

                      Comment

                      Working...
                      X