News:

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

Main Menu

OBI100 - no incoming calls using anveo

Started by sgobi84, June 26, 2014, 02:43:25 PM

Previous topic - Next topic

sgobi84

OBI100 registers and outgoing calls work fine. No inbound calls work. I tried registering both using SIP proxy on the router and without. Status shows:

SP1 Service Status
Parameter Name   Value   
Status   Registered (server=72.9.149.69:5010; expire in 103s)

Inbound calls used to work properly and now they don't.

drgeoff

Quote from: sgobi84 on June 26, 2014, 02:43:25 PM
OBI100 registers and outgoing calls work fine. No inbound calls work. I tried registering both using SIP proxy on the router and without. Status shows:

SP1 Service Status
Parameter Name   Value   
Status   Registered (server=72.9.149.69:5010; expire in 103s)

Inbound calls used to work properly and now they don't.

1.  I don't understand "using SIP proxy on the router".

2.  Why port 5010?

3.  Since the time that incoming calls did work, have you changed ISP or your router or any router settings?

Mango

Port 5010 is correct.

Check that you've set the following:

Voice Services >> SPx Service >> SPx Service:
X_KeepAliveEnable: (Checked)
X_KeepAliveExpires: 15

If you use OBiTALK to configure your device, you may need to enter OBi Expert Configuration to find these options.

If that doesn't work, report (a) what happens when you try to call your Anveo number from your cell phone, and (b) what router you are using.

sgobi84

Did set up the :

X_KeepAliveEnable: (Checked)
X_KeepAliveExpires: 15

same thing with incoming calls. I realized that I can actually get an incoming call, but only if I call immediately after outgoing call... My firewall is pfsense.

drgeoff

#4
If you turn off the firewall do incoming calls ring? I'm not suggesting that as the permanent solution, just a test. If yes, then look to your firewall settings and google for a list of the ports that Obi devices use.

Mango

Quote from: sgobi84 on June 26, 2014, 10:19:42 PMsame thing with incoming calls. I realized that I can actually get an incoming call, but only if I call immediately after outgoing call... My firewall is pfsense.

Okay, that confirms that your router is closing the NAT hole which is causing the problem.  However, I'm a little confused that my suggestion did not work.  In that case, you can change what I suggested back to their defaults.

The next thing to do is to see how you can increase timeouts on your firewall.  Try to set it to around 45 seconds.  Perhaps someone else who uses pfsense will be able to give you more specific instructions.

Good luck and keep us updated.

sgobi84

Quote from: Mango on June 27, 2014, 06:09:39 AM
Quote from: sgobi84 on June 26, 2014, 10:19:42 PMsame thing with incoming calls. I realized that I can actually get an incoming call, but only if I call immediately after outgoing call... My firewall is pfsense.

Okay, that confirms that your router is closing the NAT hole which is causing the problem.  However, I'm a little confused that my suggestion did not work.  In that case, you can change what I suggested back to their defaults.

My assumption is that this is what siproxd is exactly for: so that you don't need to be messing with ports

drgeoff


sgobi84

I ran packet capture on sip.anveo.com (72.9.149.69), and indeed the 15 sec refresh works, I see following packets going back and forth:

   xx.xx.xx.xx.5060 > 72.9.149.69.5010: SIP, length: 732
   SUBSCRIBE sip:xxxxxxxxxx@sip.anveo.com:5010 SIP/2.0

   72.9.149.69.5010 > xx.xx.xx.xx.5060: SIP, length: 559
   SIP/2.0 407 Proxy Authentication Required

   xx.xx.xx.xx.5060 > 72.9.149.69.5010: SIP, length: 860
   REGISTER sip:sip.anveo.com:5010 SIP/2.0

   72.9.149.69.5010 > xx.xx.xx.xx.5060: SIP, length: 548
   SIP/2.0 200 OK

When I call anveo from the cell phone, nothing happens. I see no additional packets sent from 72.9.149.69