obi202 behind a EdgeRouter Lite with ObiTalk.com

(1/2) > >>

rokkett:
I am attempting to set up an obi202 behind an EdgeRouter Lite.

The obi202 is running the latest firmware:

    HardwareVersion   1.4
    SoftwareVersion   3.1.0 (Build: 5110)

The EdgeRouter is running version 1.7.0 of the firmware.

The **9 222-222-222 echo test server call works as expected.

When I attempt to add a new device, the ObiTalk site never acknowledges the device registration.

I turned on sysloging and see nothing logged during the registration process.

    Feb  6 16:28:51 obi202  si3226x : Channel 0 : Chip Rev 3
    Feb  6 16:28:51 obi202  si3226x : Channel 1 : Chip Type 28
    Feb  6 16:28:51 obi202  si3226x : Channel 1 : Chip Rev 3
    Feb  6 16:28:51 obi202  PARAM Cache Write Back(256 bytes)
    Feb  6 16:28:51 obi202  ==== Networking is ready ====
    Feb  6 16:28:51 obi202  IP Address= 192.168.1.30
    Feb  6 16:28:51 obi202  Gateway   = 192.168.1.1
    Feb  6 16:28:51 obi202  Netmask   = 255.255.255.0
    Feb  6 16:28:51 obi202  Patch verification passed, and enable patch
    Feb  6 16:28:51 obi202  Patch verification passed, and enable patch
    Feb  6 16:28:52 obi202  VBAT Up = 58.901 v
    Feb  6 16:28:52 obi202  VBAT Up = 58.272 v
    Feb  6 16:28:52 obi202  PARAM Cache Write Back(256 bytes)
    Feb  6 16:28:53 obi202  Starting LB Cal on channel 0
    Feb  6 16:28:53 obi202  Starting LB Cal on channel 1
    Feb  6 16:28:55 obi202  ProSLIC_RingSetup : VBATR_EXPECT (5500000): Clamped to Gen Conf Limit (51eb82a)
    Feb  6 16:28:55 obi202  Si3226x PCMStart
    Feb  6 16:28:55 obi202  ProSLIC_RingSetup : VBATR_EXPECT (5500000): Clamped to Gen Conf Limit (51eb82a)
    Feb  6 16:28:55 obi202  Si3226x PCMStart
    Feb  6 16:28:56 obi202  Random Delay Range: 30
    Feb  6 16:28:56 obi202  Actual Randome Delay: 10
    Feb  6 16:28:56 obi202  Setup Provisioning for system start! 10
    Feb  6 16:28:56 obi202  PROV: Lua update checksum not configured.
    Feb  6 16:28:59 obi202  [BT#0] BT_EVT_BT_DOWN @ 485
    Feb  6 16:28:59 obi202  [BT#1] BT_EVT_BT_DOWN @ 485
    Feb  6 16:28:59 obi202  PROV: SNTP clock is ready
    Feb  6 16:28:59 obi202  PROV: Timers adjusted according to SNTP clock
    Feb  6 16:29:07 obi202  PROV: Starting provisioning process
    Feb  6 16:29:07 obi202  PROV: Start to download files ...
    Feb  6 16:29:07 obi202  PROV: Invalid server name, Skipped
    Feb  6 16:29:07 obi202  PROV: schedule the next provisioning process
    Feb  6 16:47:24 obi202  PARAM Cache Write Back(256 bytes)

I even added 4.2.2.2 as a DNS on the obi202, no change.

On the EdgeRouter, I have disabled the SIP module:

     set system conntrack modules sip disable

I have enabled the upnp service:

    set service upnp listen-on eth0 outbound-interface eth1

At one point, I have even set up port forwarding for the following ports back into my network for the obi202:

    5060
    5061
    10000-20000

But still no success.

Thoughts?

rokkett:
Just a quick update.  I will be returning this device.  I connected it directly to my cable modem with no firewall/router etc blocking any traffic and still unable to register it ObiTalk.com.

Does comcast block these devices from their network?  Nothing on my end that I can control is blocking this device from functioning correctly.

Oh, well. It sounded like a great idea.  Moving on to other devices after more research...

rokkett

Sheffield_Steve:
I have a similar setup: Edgerouter, Comcast, etc and it all works perfectly without any special setup.  Maybe you have a bad obi202?

rokkett:
When you say "no special setup", do you mean you didn't make any SIP or upnp settings?  I started that way and just kept reading and trying settings to resolve my issue.

The echo test always works.

Odd...

Sheffield_Steve:
That's correct!  No SIP or upnp settings, just the basic config via the wizard.

Quote from: rokkett on February 07, 2016, 01:37:23 pm

When you say "no special setup", do you mean you didn't make any SIP or upnp settings?  I started that way and just kept reading and trying settings to resolve my issue.

The echo test always works.

Odd...

Navigation

[0] Message Index

[#] Next page