SOLVED with firmware 1.2: OBI110 Not Work with Hong Kong PSTN Line
ronaldng:
Quote from: yhfung on March 19, 2011, 03:09:10 am
Good news! What is your fixed line operator? PCCW, HGC, HKBN or others?
PCCW
yhfung:
Thank you for your information, I am looking for new firmware update.
YH
obi-support2:
pchow,
The caller-id problem should be fixed. Beta f/w has been pushed to your unit by our staff earlier today. Please give it a try.
Regarding problem 2, I believe what you want is to have the OBi answer the PSTN call, then let the caller dial another number to go out on SP1.
Unlike the SPA3102 which is based on prompt tones, OBi uses a built-in auto-attendant (AA or aa; English only at this time). What you need to do is to invoke the aa, then the PSTN caller can continue to dial the target number. Here is an outline:
1. LINE Port inboundCalRoute = {aa}
2. PSTN Call rings, OBi AA answers and announces option 1,2,3,...
3. Caller selects option 2, OBi asks user to dial the number follow by #
4. Caller dials **1 1234 5678 #, OBi says please wait while your call is being connected
5. Called number rings, etc.
For 1, you can allow just a few caller-id numbers like this: {(11112222|33334444):aa}
In this case only if the caller number is either 11112222 or 33334444 the aa will answer and let
you dial further. Other caller numbers are rejected.
AA can be setup with 1-4 PIN so that the caller will need to enter a PIN before
he can use option 2. In that case, OBi will say, Please enter PIN, after you select option 2.
The **1 prefix can be eliminated if your AA is setup to use SP1 as Primary Line (parallel to the
setup of the PHONE Port.
Note that AA option 3 is also very interesting. It may save you some toll charge by calling you back from the OBi. (Not sure if HK cell phone charges differently for incoming and outgoing calls?).
There are many ways you can enhance this. Check out other topics in this forum or take at look at our OBi AdminGuide for more information.
yhfung:
Caller ID problems on Hong Kong and China PSTN have been fixed， our members have tested the firmware of version 1.2 and found no problem in getting the Caller ID from the LINE port.
YH
pchow:
Quote from: obi-support2 on March 19, 2011, 05:16:00 pm
pchow,
The caller-id problem should be fixed. Beta f/w has been pushed to your unit by our staff earlier today. Please give it a try.
Regarding problem 2, I believe what you want is to have the OBi answer the PSTN call, then let the caller dial another number to go out on SP1.
Unlike the SPA3102 which is based on prompt tones, OBi uses a built-in auto-attendant (AA or aa; English only at this time). What you need to do is to invoke the aa, then the PSTN caller can continue to dial the target number. Here is an outline:
1. LINE Port inboundCalRoute = {aa}
2. PSTN Call rings, OBi AA answers and announces option 1,2,3,...
3. Caller selects option 2, OBi asks user to dial the number follow by #
4. Caller dials **1 1234 5678 #, OBi says please wait while your call is being connected
5. Called number rings, etc.
For 1, you can allow just a few caller-id numbers like this: {(11112222|33334444):aa}
In this case only if the caller number is either 11112222 or 33334444 the aa will answer and let
you dial further. Other caller numbers are rejected.
AA can be setup with 1-4 PIN so that the caller will need to enter a PIN before
he can use option 2. In that case, OBi will say, Please enter PIN, after you select option 2.
The **1 prefix can be eliminated if your AA is setup to use SP1 as Primary Line (parallel to the
setup of the PHONE Port.
Note that AA option 3 is also very interesting. It may save you some toll charge by calling you back from the OBi. (Not sure if HK cell phone charges differently for incoming and outgoing calls?).
There are many ways you can enhance this. Check out other topics in this forum or take at look at our OBi AdminGuide for more information.
Thank you for your quick action. HK PSTN line and caller id problems were solved in couples of days.
I knew my question #2 could be solved by using AA but my home oldies (non-english speaking) just could not handle AA well. I was just trying to do PSTN2VOIP like the way SPA3k does. Now I know SP(xx.) is not a correct callroute.
Navigation
[0] Message Index
[#] Next page
[*] Previous page