cut-offs using SPA-2000

[jpadie]

Hi there

i have a number of voip devices in my house, and thes have all co-existed happily for more than a year. Recently I have started getting problems, however.

my sipura SPA 2000 is currently disconnecting calls after precisely 60 seconds. i am finding exactly the same behaviour with the sjlabs softclient which is attached to the same account. both clients are inside the same nat protected network.

any thoughts on what might be happening?

thanks
Justin

 

[ISDNman]

Problem not here"

I can'r prove it, but the fact it does it with both the SPA2000 and the softclient makes it likely the problem is with your carrier.

You should see if you can do a protocol log to see where the teardown request is originating.

Best of luck.

 

[jpadie]

im not so convinced as i have a number of accounts with this provider (voiptalk.org) and they are all in use behind the same firewall. but i'm happy to suspend disbelief if you can tell me how to log the voip output?

 

[ISDNman]

im not so convinced as i have a number of accounts with this provider (voiptalk.org) and they are all in use behind the same firewall. "

But doesn't this confirm my theory? If only one account is effected then it is probably some account "class of service" parameter" that got changed by accident.

Or something stupid like this account is not being billed with your other accounts and is shown as in arears.

Sorry , but I don't know enough about the SPA-2000 to tell you how to do a protcol log (trace) but you might check in the manual or with the manufacturers.

Best of luck.

 

[jpadie]

you might well be right. i've opened a support ticket anyway. Thanks

my theory was that one of the clients was set to re-register every 60 seconds and, in doing so, was causing the firewall/router to re-route port 5060 to it rather than the device that i was using. Pretty flakey, I accept, as i have been unable to find said device!

In the past i was having a similar issue with being disconnected after exaclty 60 minutes. i spent several days working with voiptalk about this. they are adamant that they have no server issues or parameters that would cause this and, to their credit, the problem went away when i changed from using the native ports on the draytek vigor 2600v to the sipura. Somewhat (un-)surprisingly the register expiry parameter of the draytek and the softclient were both 3600 seconds.

thanks for your advice. i'll post back if i get any news from voiptalk.

 

[ISDNman]

Great, good luck.

Just keep digging!

 

[ISDNman]

So what did you find?

 

[jpadie]

apologies for such delay in replying. and thankyou for following up.

in the end I found that downgrading to the last but one firmware fixed the issue.

what i don't know is whether this is a problem with the latest firmware or whether the previous upgrade did not complete perfectly and left me with a buggy box. I know i could check this by upgrading again but ... why change something that works (this is not my usual mantra but telephony is a bit vital to my business!)