News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

HKBN 2B Obi110 or OBi100 settings

Started by baor, April 09, 2011, 05:50:29 PM

Previous topic - Next topic

baor

This post is intended to collect and share info on how to configure HKBN 2B in the Obi110 or Obi100.

I could get the device to register, but I will get an error message code "500" when I tried to dial out.
There is no ringing on my side when someone is calling me...
My router is Asus RT-N16. It is flashed with Tamagochi. I have forwarded 5060 and RTP ports in my router.

I have tried stun.xten.com and stun01.sipphone.com, stun.voipbuster.com, stun.ideasip.com.

I am using the following dial plan:
([2-9]xxxxxx|011xx.|1[2-9]xx[2-9]xxxxxx|<852:>[236789]xxxxxxxS0|[236789]xxxxxxxS0|1850xS0|188xS0)

My OBi110 is running    1.2.1 (Build: 2103).

Is there anyway we could have debug log for this device?

Could anyone help?
Thank you!

Below shows my settings:








Below shows the log
I tried to call a number as you could see the "OFF HOOK" Line
After dialing, an error message saying it is rejected by the service provider Code "500"
Thank you!!!!!!!!!!


<7> sendto cb505987:5060(842)
   192.168.1.127   10/04 01:40:57.746   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:40:57.746   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:40:57.746   
<7> TCP:Accept OK (HTTPD)
   192.168.1.127   10/04 01:41:02.073   
<145> Reboot is scheduled in 1 seconds
   192.168.1.127   10/04 01:41:02.075   
<7> TCP:Accept OK (HTTPD)
   192.168.1.127   10/04 01:41:02.115   
<7> TCP:Accept OK (HTTPD)
   192.168.1.127   10/04 01:41:02.116   
<0> Reboot checking.....   192.168.1.127   10/04 01:41:03.069   
<143> Compare the version now
   192.168.1.127   10/04 01:41:03.070   
<0> Final Cleanup before reboot....
   192.168.1.127   10/04 01:41:03.070   
<144> Goodbye! Reboot Now. (reason: 9)
   192.168.1.127   10/04 01:41:04.070   
<6> ==== Networking is ready ====
   192.168.1.127   10/04 01:41:10.274   
<0> IP Address= 192.168.1.127    192.168.1.127   10/04 01:41:10.280   
<0> Gateway   = 192.168.1.1    192.168.1.127   10/04 01:41:10.281   
<0> Netmask   = 255.255.255.0    192.168.1.127   10/04 01:41:10.283   
<3> SYSTEM REBOOTED (Reason: 9, lifecycle: 1496)
   192.168.1.127   10/04 01:41:10.284   
<0> SLIC_init ...   192.168.1.127   10/04 01:41:10.329   
<0> Reset SLIC...   192.168.1.127   10/04 01:41:10.331   
<150> Setup Provisioning for system start! 1200
   192.168.1.127   10/04 01:41:10.342   
<0> SLIC & DAA is initialized   192.168.1.127   10/04 01:41:12.000   
<6> Start Main Service Now   192.168.1.127   10/04 01:41:14.052   
<7> Voice Main
   192.168.1.127   10/04 01:41:14.053   
<7> [CPT] --- FXS s/w tone generator (0) ---
   192.168.1.127   10/04 01:41:14.059   
<7> BASESSL:load cert:5
   192.168.1.127   10/04 01:41:14.162   
<7> BASESSL:Load certificate ok
   192.168.1.127   10/04 01:41:14.167   
<7> sendto cb505987:5060(569)
   192.168.1.127   10/04 01:41:14.452   
<7> XMPP:Invalid cfg use for xmpp
   192.168.1.127   10/04 01:41:14.453   
<7> GTT:xmpp not configured
   192.168.1.127   10/04 01:41:14.456   
<7> XMPP:Invalid cfg use for xmpp
   192.168.1.127   10/04 01:41:14.457   
<7> GTT:xmpp not configured
   192.168.1.127   10/04 01:41:14.458   
<7> [SLIC] FAX MODE  ---  OFF
   192.168.1.127   10/04 01:41:15.392   
<7> [SLIC]:Slic#0 ON HOOK
   192.168.1.127   10/04 01:41:15.394   
<7> sendto cb505987:5060(569)
   192.168.1.127   10/04 01:41:15.454   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:41:15.456   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:41:15.458   
<7> sendto cb505987:5060(837)
   192.168.1.127   10/04 01:41:15.472   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:41:15.743   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:41:15.761   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:41:15.801   
<7> sendto cb505987:5060(285)
   192.168.1.127   10/04 01:41:15.803   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:41:15.805   
<7> [CPT] --- FXS s/w tone generator (7133) ---
   192.168.1.127   10/04 01:41:21.194   
<147> PROV: Auto Update invalid server name()
   192.168.1.127   10/04 01:41:22.344   
<7> [CPT] tone compression done - 12283 !!
   192.168.1.127   10/04 01:41:26.342   
<7> sendto cb505987:5060(843)
   192.168.1.127   10/04 01:42:15.819   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:42:16.102   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:42:16.108   
<7> [PR] prompt transcoding done!!
   192.168.1.127   10/04 01:43:03.707   
<7> [SLIC]:Slic#0 OFF HOOK
   192.168.1.127   10/04 01:43:10.202   
<7> [CPT] --- FXS SiLab h/w tone generator ---
   192.168.1.127   10/04 01:43:10.203   
<7> sendto cb505987:5060(843)
   192.168.1.127   10/04 01:43:12.123   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:43:12.414   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:43:12.443   
<7> [DSP]: ---- H/W DTMF ON (level:1) : * @ 119320 ms----   192.168.1.127   10/04 01:43:13.373   
<7> [DSP]  ---- H/W DTMF OFF @ 119470 ms ----   192.168.1.127   10/04 01:43:13.522   
<7> [DSP]: ---- H/W DTMF ON (level:1) : * @ 119640 ms----   192.168.1.127   10/04 01:43:13.693   
<7> [DSP]  ---- H/W DTMF OFF @ 119790 ms ----   192.168.1.127   10/04 01:43:13.843   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 120320 ms----   192.168.1.127   10/04 01:43:14.373   
<7> [DSP]  ---- H/W DTMF OFF @ 120470 ms ----   192.168.1.127   10/04 01:43:14.522   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 122660 ms----   192.168.1.127   10/04 01:43:16.712   
<7> [DSP]  ---- H/W DTMF OFF @ 122810 ms ----   192.168.1.127   10/04 01:43:16.862   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 4 @ 123000 ms----   192.168.1.127   10/04 01:43:17.052   
<7> [DSP]  ---- H/W DTMF OFF @ 123150 ms ----   192.168.1.127   10/04 01:43:17.202   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 5 @ 123360 ms----   192.168.1.127   10/04 01:43:17.412   
<7> [DSP]  ---- H/W DTMF OFF @ 123510 ms ----   192.168.1.127   10/04 01:43:17.563   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 5 @ 123720 ms----   192.168.1.127   10/04 01:43:17.772   
<7> [DSP]  ---- H/W DTMF OFF @ 123870 ms ----   192.168.1.127   10/04 01:43:17.922   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 5 @ 124040 ms----   192.168.1.127   10/04 01:43:18.092   
<7> [DSP]  ---- H/W DTMF OFF @ 124190 ms ----   192.168.1.127   10/04 01:43:18.242   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 124360 ms----   192.168.1.127   10/04 01:43:18.412   
<7> [DSP]  ---- H/W DTMF OFF @ 124510 ms ----   192.168.1.127   10/04 01:43:18.562   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 124650 ms----   192.168.1.127   10/04 01:43:18.703   
<7> [DSP]  ---- H/W DTMF OFF @ 124810 ms ----   192.168.1.127   10/04 01:43:18.862   
<7> [DSP]: ---- H/W DTMF ON (level:1) : 6 @ 125040 ms----   192.168.1.127   10/04 01:43:19.092   
<7> [DSP]  ---- H/W DTMF OFF @ 125190 ms ----   192.168.1.127   10/04 01:43:19.243   
<7> [DSP]: ---- H/W DTMF ON (level:3) : # @ 125480 ms----   192.168.1.127   10/04 01:43:19.532   
<7> [DSP]  ---- H/W DTMF OFF @ 125610 ms ----   192.168.1.127   10/04 01:43:19.663   
<142> PARAM Cache Write Back(256 bytes)    192.168.1.127   10/04 01:43:20.084   
<7> STUNC:ERR=TO,mtd=1
   192.168.1.127   10/04 01:43:58.754   
<7> sendto cb505987:5060(952)
   192.168.1.127   10/04 01:43:58.757   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:43:59.038   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:43:59.043   
<7> sendto cb505987:5060(358)
   192.168.1.127   10/04 01:43:59.044   
<7> RTP:Del Channel
   192.168.1.127   10/04 01:43:59.046   
<7> [CPT] --- FXS SiLab h/w tone generator ---
   192.168.1.127   10/04 01:43:59.055   
<7> [CPT] --- FXS s/w tone generator (165005) ---
   192.168.1.127   10/04 01:43:59.056   
<7> sendto cb505987:5060(843)
   192.168.1.127   10/04 01:44:12.460   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:44:12.752   
<7> RxFrom:cb505987:5060
   192.168.1.127   10/04 01:44:12.756   
<7> [SLIC] FAX MODE  ---  OFF
   192.168.1.127   10/04 01:44:17.540   
<7> [SLIC]:Slic#0 ONHOOK
   192.168.1.127   10/04 01:44:17.541   
<7> [SLIC]:Slic#0 OFF HOOK
   192.168.1.127   10/04 01:44:21.740   
<7> [CPT] --- FXS SiLab h/w tone generator ---
   192.168.1.127   10/04 01:44:21.742   


____________________________________________________________
2011-04-11

We finally made some progress after OBIHAI Support suggested to turn off X_InsertRemotePartyID.
I could receive call and dial out. However I got cut off every 10 mins.
Does it have to do with X_KeepAliveExpires or RegistrationPeriod?


obi-support2

baor,

1. What kind of home router you have?
    You can check whether the router has a SIP ALG function.
    If it has, try TURNING OFF the feature and call again.

2. Make sure the number you try to call is acceptable by HKBN.
    Have you tried to call the same number from another
    device or softphone with HKBN? and successful?
   
3. We can also check your device configuration remotely. For privacy you can
   email support@obihai.com and provide your OBi number (printed on the back of the unit),
   and we can provide you further assistance.

OBIHAI Support Staff

RonR

SIP error code 500 is : Internal Server Error.

You have a STUN server configured : stun01.sipphone.com

This STUN server was shut down a couple of weeks ago and will not return.  Unless the current firmware has changed the timeout, you will experience a 40 second delay on each call you attempt with a non-existent STUN server.

yhfung

#3
In fact I am one of HKBN 2b users in Hong Kong. I have been able to install it in my SPA3000, PAP2T and Asterisk server. The settings of HKBN 2b is given by

http://www.hkepc.com/forum/viewthread.php?tid=1141462&page=218#pid18904520

I have already tried several times to register the 2b server with my OBi110 in Shenzhen but still failed. I believe the information provided in the above link should provide a good reference of how to convert the settings in Linksys SPA to OBi devices.

YH
Hong Kong and China OBi Users Group
www.telecom-cafe.com

yhfung

#4
I just reconnected my old Linksys PAP2T ATA with the HKBN 2b settings in LINE 1 tab. The HKBN 2b settings in the PAP2T works very well. It can make HK PSTN outbound call and receive HK PSTN call with caller ID shown on the phone attached to it.

My network configuration is shown as follows:

Interent --> China Telecom --> modem --> Router (Draytek 2200E Plus) --> i) PCs, ii) Asterisk, iii) SPA devices including SPA941, PAP2T, iv) OBi110.

Based on the information shown in the above post, the PAP2T, configured to connect HKBN 2b server, can make and receive call without any problem encounter. Please note that I do not need to set any UDP ports forwarding (5060 and RTP number range) to my PAP2T.

Also based on my pass experience of using Linksys ATA, the settings for HKBN 2b in PAP2T which can make the SIP client be visible from the WAN port. That's to say that the SIP client looks like sitting in the fornt of the WAN port of the router.

So back to the OBi110 or OBi100, how can we make the internal SIP client (behind router) be in front of the WAN port of the router although it is connected to the LAN port of the router?

YH
Hong Kong and China OBi Users Group
www.telecom-cafe.com

baor

Quote from: obi-support2 on April 09, 2011, 06:52:51 PM
baor,

1. What kind of home router you have?
    You can check whether the router has a SIP ALG function.
    If it has, try TURNING OFF the feature and call again.

2. Make sure the number you try to call is acceptable by HKBN.
    Have you tried to call the same number from another
    device or softphone with HKBN? and successful?
   
3. We can also check your device configuration remotely. For privacy you can
   email support@obihai.com and provide your OBi number (printed on the back of the unit),
   and we can provide you further assistance.



1. My router is Asus RT-N16. It is flashed with Tamagochi.
    I will post some of my router setting. I don't see the "SIP ALG".

2. I tried to call weather report, which should be a valid HK number (1878-200)

3. Nice. Do I have to put a reference number (ticket number) in my email? So I could get your attention and support?

baor

Quote from: RonR on April 09, 2011, 06:59:16 PM
SIP error code 500 is : Internal Server Error.

You have a STUN server configured : stun01.sipphone.com

This STUN server was shut down a couple of weeks ago and will not return.  Unless the current firmware has changed the timeout, you will experience a 40 second delay on each call you attempt with a non-existent STUN server.

I have tried stun01.sipphone.com and stun.xten.com.

I use the # key at the end of dial.
The error code is immediately if I called 1878-200.

Dialing regular phone number will have the 40 seconds delay you talked about. Does it mean stun.xten.com is closed?

baor

#7
Quote from: yhfung on April 09, 2011, 07:01:06 PM
In fact I am one of HKBN 2b users in Hong Kong. I have been able to install it in my SPA3000, PAP2T and Asterisk server. The settings of HKBN 2b is given by

http://www.hkepc.com/forum/viewthread.php?tid=1141462&page=218#pid18904520

I have already tried several times to register the 2b server with my OBi110 in Shenzhen but still failed. I believe the information provided in the above link should provide a good reference of how to convert the settings in Linksys SPA to OBi devices.

YH

I also have a Linksys PAP (original Vonage version, Unprovisioned?) and I could use my PAP fine with HKBN. I also know how to reset the registration as HKBN allows only 1 register.

There were some settings I could not find in the OBi110.


【NAT Settings】Heading
                NAT Mapping Enable: yes    NAT Keep Alive Enable: yes
                NAT Keep Alive Msg: $PING

【RTP Parameters 】Heading
                RTP Packet Size: 0.020
   
【NAT Support Parameters】Heading
                 Handle VIA received: yes          Handle VIA rport: yes  
                 Insert VIA received: yes             Insert VIA rport: yes  
                 Substitute VIA Addr: yes            Send Resp To Src Port: yes

                 STUN Enable: yes                      STUN Test Enable: yes
                 STUN Server:  stun.xten.com

baor

Is there anyway we could have debug log for this device?

RonR

Quote from: baor on April 09, 2011, 08:33:40 PMDialing regular phone number will have the 40 seconds delay you talked about. Does it mean stun.xten.com is closed?
I don't know the status of stun.xten.com, but I've always avoided it as it's often down.  I just know that the OBi has a 40 second timeout on STUN server responses, so if it's not there, you wait 40 seconds before the OBi resumes processing of the call.  I reported the problem to support via email back on 3/22 but got no reply and it was also discussed here in the forum, but apparently no action was taken.

I'm currently using stun.ideasip.com with no problems.

RonR

Quote from: baor on April 09, 2011, 08:43:12 PM
Is there anyway we could have debug log for this device?
There is SYSLOG capability at:

System Management -> Device Admin

obi-support2

You can run a syslog server on your PC.

On the OBi, under SP1/SP2 Service, enable X_SipDebugOption.
Under Device Admin, point Debug Server and port to the IP address and
port of the PC where you run your syslog server.

This could be a SIP Interop issue. May be HKBN does not like our INVITE request.
Please email your capture log file to support@obihai.com and we should be able
to figure it out and do something about it.

To help you remotely trouble shoot the problem, all we need is your 9-digit OBI number;
and you must add your device to OBiTALK if you haven't done so yet.

Thank you.
OBIHAI Support Staff

baor

Quote from: RonR on April 09, 2011, 08:46:58 PM
Quote from: baor on April 09, 2011, 08:33:40 PMDialing regular phone number will have the 40 seconds delay you talked about. Does it mean stun.xten.com is closed?
I don't know the status of stun.xten.com, but I've always avoided it as it's often down.  I just know that the OBi has a 40 second timeout on STUN server responses, so if it's not there, you wait 40 seconds before the OBi resumes processing of the call.  I reported the problem to support via email back on 3/22 but got no reply and it was also discussed here in the forum, but apparently no action was taken.

I'm currently using stun.ideasip.com with no problems.

I have tried stun.xten.com and stun01.sipphone.com, stun.voipbuster.com, stun.ideasip.com.
Still could not dial out.

baor

#13
Quote from: obi-support2 on April 09, 2011, 08:51:01 PM
You can run a syslog server on your PC.

On the OBi, under SP1/SP2 Service, enable X_SipDebugOption.
Under Device Admin, point Debug Server and port to the IP address and
port of the PC where you run your syslog server.

This could be a SIP Interop issue. May be HKBN does not like our INVITE request.
Please email your capture log file to support@obihai.com and we should be able
to figure it out and do something about it.

To help you remotely trouble shoot the problem, all we need is your 9-digit OBI number;
and you must add your device to OBiTALK if you haven't done so yet.

Thank you.


IF I added the device, it will erase all of my settings.
I tried to use the portal in the very beginning. However, it would not register.

I could get it to register using manual settings......


I have no experience with syslog server. Any easy tutorial?

QBZappy

baor,

Hi

Here are 2 free Windows syslog servers I have used in the past. They are easy to use.


http://tftpd32.jounin.net/
http://kin.klever.net/pumpkin
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

baor

Quote from: obi-support2 on April 09, 2011, 08:51:01 PM
You can run a syslog server on your PC.

On the OBi, under SP1/SP2 Service, enable X_SipDebugOption.
Under Device Admin, point Debug Server and port to the IP address and
port of the PC where you run your syslog server.

This could be a SIP Interop issue. May be HKBN does not like our INVITE request.
Please email your capture log file to support@obihai.com and we should be able
to figure it out and do something about it.

To help you remotely trouble shoot the problem, all we need is your 9-digit OBI number;
and you must add your device to OBiTALK if you haven't done so yet.

Thank you.


I made the settings and reboot.
I tried the TFTPD software, nothing is going on???





What should I do now?

QBZappy

baor,

Hi

You may need to port forward port 514 in your router to the IP of the server. I just made a test on my computer. You should see activity that the OBi is generating.
<See Image>

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

baor

Quote from: QBZappy on April 09, 2011, 10:27:47 PM
baor,

Hi

You may need to port forward port 514 in your router to the IP of the server. I just made a test on my computer. You should see activity that the OBi is generating.
<See Image>



Could you how you set the software? Do I have to set the DHCP server? How?

QBZappy

#18
baor,

What is your router model name and number?

EDIT: Can you log on the the web page of your router?
Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.

baor

Quote from: QBZappy on April 09, 2011, 10:30:58 PM
baor,

What is your router model name and number?

My router is Asus RT-N16. It is flashed with Tamagochi.
Do you have MSN or other Instant messeger?

It is all internal, why do I have to forward port????