Posted by AbleComm on October 7, 2009, 2:59 pm
The minor bit of difficulty I mentioned above related to picking the incoming call up and answering it using either line 1 or line 2, is that because the timing of the outgoing signaling from the PP GS to my phone of an incoming call seems to differ just slightly between the two GS phone ports, I sometimes experience a slight delay in being able to say ‘hello’ once I pickup one of the lines to answer the call. If I just remember to give it a second to catch up before doing so, it works just fine. It also seems to work slightly better if I answer the laggard line, line 2 rather than line 1. I don’t have to wait as long for it to ‘catch-up’.
I have not yet had the chance to answer either line 1 or line 2, have another call come in while on the phone and then see if things still work just as advertised, and/or if the open line then rings at that point. Once this does occur, I will let you know what happens. (I did not have the ringers turned on when it did occur. I was just using the LED indicator lights. I mainly use those, but there are times when it is not practical to do so. With both ringers disabled, other than the slight delay issue/conflict, I have no problem using things.)
There are also two other unrelated issues I am having as well. Even though I have my ‘time zone’ setting set for MST in the web ‘control panel’, I am still getting CST ‘time zone’ data sent with each incoming call. I am guessing that is because I am using a CST ‘Rate center’ #. (The phone displays these settings from incoming call data. I can manually override this after each call, but that is a real pain.)
The non-PP VoIP line (Line 3) has a MST time zone ‘rate center’ # on it, so it is not the source of the problem. Incoming calls to the 3rd line, which is something which only happens if the other company’s customer svc dept calls me or if I call myself from one of the PP lines, will reset the time displayed on the phone to the correct time for my time zone.
The next issue is that I have outgoing CID blocked in the PP web ‘control panel’ settings, as well as disabled via *61, yet when I dial *82, it does NOT remove the outbound CID info block for even that one call.
I thought that this was probably because I have the CID blocking enabled in the ‘control panel’, as opposed to just with *61. So, I tried leaving *61 active and enabling outgoing CID in the web ‘control panel’ so that I could test this theory to find out.
BUT it seems that changes made in that section of the web ‘control panel’ take 3-5 business days (!!) to take effect. You might want to make that info just a wee bit more prominent up front instead of attention being drawn to it by the green feedback info AFTER the ‘save changes’ button is clicked. It will save your back-end people/systems a lot of time and effort if you were to do so.
For instance, if after the change is affected, *61 alone is not sufficient to block my outgoing CID info on several different test recipient’s phones on more than one Telco’s N/W, as soon as the current change to allow outgoing CID info is affected, I will immediately be submitting another change to change it back to not allowing outgoing CID info via the web ‘control panel’. Right after I first test it for sufficient blocking using *61 alone, and then test *82 to see if it ‘unblocks’ for that one call only. Normally, I want the outgoing CID blocked, but there are some times when I either want it selectively enabled for reasons of my own, or because it is simply necessary to have it enabled or the receiving system will simply block the call if outgoing CID is not enabled.
Moreover, if sufficiently blocking the outgoing CID in most circumstances requires using the web ‘control panel’ based enablement, this will also probably result in many more change request being made through the web ‘control panel’ as well, assuming of course that the *82 code doesn’t override it at that point in time either, because there will undoubtedly be those times when it will simply be necessary to make a call or two to a number which will only accept incoming calls with outbound CID enabled. That seems to me like an awful lot of unnecessary ‘turn it on for me’, ‘turn it off for me’, ‘turn it back on for me’ requests to have to be processing.
I know that you are working on something similar to this related to the combination of using outgoing CID blocking and enabling Anonymous Call Rejection simultaneously. I don’t know if this is related to that, but they may be.
Responses: