Greetings again,
First off, I'm new to this forum thingy (as well as to IP 'phones)and can't see how to respond to
replies individually, so I'll try to do it all at once, it'll be a long post.. please bear with me.

People say they have no problems, but the trouble only affects some incoming calls (using the
'phone number, I can't try the URI and none of my callers would use it anyway). To my untutored eye
it looks as if the effective maximum "lifetime" of the SIP registration is 30s, but the registrar
server isn't signalling that in it's reply to the register method.

The RFC is a long document and I may be taking bits out of context, but the relevant parts seem to
be 10.2.1.1. and 10.3.1-8.

Thanks for the settings, they generally correspond with mine, which have worked and continue to
work properly via the old NAT proxy, although the new proxy does appear to get me to a different
registrar server - which requires authentication, of which more later.

I don't think that proxy fallback is relevant, my box only knows one NAT proxy and one SIP proxy,
I'm not using DNS SRV. This time has been at the default of 3600 throughout.

I've had another look at the logs and things aren't exactly as I described earlier. My ATA isn't
ignoring the expiration time set by the server, the server is (usually) setting (in the "OK" reply)
the same time that my ATA sends (in the "REGISTER" message), and the ATA uses it. This happens for
times greater than 60s. For shorter times the server replies 60s. My ATA then uses its time value
since this is the shorter. Since the server seems to actually use a maximum value of 30s (like the
old arrangement) there appears to be a period from 30s after one registration until the next
registration, when the registration has expired but the ATA thinks it still valid. I'm not sure of
the exact times here, I can't see what's going on in real time, only by continually refreshing the
ATA status page (to see how far into the registration cycle the thing is), calling into it via a
cellphone and then checking the log, so there are bound to be errors, but you can see what I'm
getting at.

This doesn't affect outgoing calls. However an incoming call received during this time doesn't get
connected, the caller hears nothing and the 'phone doesn't ring. When the next registration occurs,
the caller (if they're still waiting) hears ring tone and the 'phone rings. I suspect, although I
haven't tried it, that there is a maximum timeout for this and that if the call isn't connected for
a certain time, some announcement or tone is returned. If the ATA is set to the factory default
time of 3600s, there is a long time when incoming calls don't get through, whilst if the time is
set to 30s, they all do.

Now for authentication, for those who know about SIP, there may be a clue here. The new NAT server
gets me to a registrar that requires authentication whereas the old one didn't. It replies to my
REGISTER message with an "authentication required" reply 407. If I've set a registration expires
time of more than 30s, this reply includes a "stale" parameter which is set to "true". Otherwise
this parameter is missing. It may be that there is some other setting which is only relevant when
authentication is needed and which is wrong. For example I'm not using the "Auth. ID" setting
whatever that is. This may now be important although it doesn't stop registration. Maybe it
confuses the server. I'm sure the SIP experts here will know.

I think that the need for authentication will have increased the amount of "overhead" data traffic
significantly. That is extra load on the network and extra load on my monthly allowance, so I would
like to have the registration interval as long as possible without causing problems, 60s would be
nice. I seem to remember questions about this in this forum in the past.

There are a couple of things I've still to try, more out of curiosity than expectation, putting
something (SIP id?) into the Auth. ID field and checking to see what state the ATA is in when a
call is actually in the "not connected" state in case something does actually make it to the ATA.

Thanks for the replies so far.

John.

Hi Tp

Can you list the info your phone is requesting so we can fill in the settings?


puddy

It does look like from what you describe that the OB proxy is using a 30sec timeout. I'm confused by your saying later on that you are NOW receiving a 407 Authentication reqd whereas you weren't before. In SIP traces that I've seen before the OB proxy has always requested authentication. I suggest you try setting the 'Auth ID' as my guess is that your registration isnt quite correct.

Hi, yall. As they say.

I haven't yet tried tried the changes I mentioned. The system is presently working,
apparently OK, via the new NAT server with the registration expires time set to 30s.

In reply to puddy. I'm not sure what you mean by the "info the 'phone is requesting".
 The ATA sends a normal "register" message. To show what's going on, and to  illustrate
 the authentication difference for MisterW, here are extracts of the logs. Hopefully my
 notes are helpful, they are to me.

This forum won't let me attach them as a text file, so it's another mammoth
post and you'll have to try to sort out the long lines and the wrong formatting in some places,
(some proxy-authorization and proxy-authenticate header fields are split over two lines, I can't get this
 to come out right here, it's OK in Notepad) I'm afraid. It really needs a fixed width font for the notes to
 look right.

Thanks all.
John.


Registration via the old NAT server
------------------------------------

Shows the default registration expiry time, 3600s, on the ATA; the server reply with it's time
of 30s and no authentication requirement. Everything works, all sweetness and light.

**My annotations are like this**

syslog server(port:514) started on Fri Jan 29 21:39:04 2010  **
RSE_DEBUG: reference domain:legacy-nat.plus.net              **  These messages are

• ->194.165.60.134:5082                                     **  not part of SIP.
• ->194.165.60.134:5082                                     **

**This is the register request from my ATA**

REGISTER sip:sip.plus.net SIP/2.0
Via: SIP/2.0/UDP 192.168.100.4:5060;branch=z9hG4bK-10f58fc3
From: Anon <sip:nnnnnnn@sip.plus.net>;tag=b7ced3d32bab9beo0
To: Anon <sip:nnnnnnn@sip.plus.net>
Call-ID: b6bf3e73-e8b44ef3@192.168.100.4
CSeq: 36530 REGISTER
Max-Forwards: 70
Proxy-Authorization: Digest username="nnnnnnn",realm="newsip",nonce="4b63549e000129d0a9be922f13a9872b5f444cded893fe50",uri="sip:sip.plus.net",algorithm=MD5,response="c4d367576f7283d00239ea6b3673755b",qop=auth,nc=0000000d,cnonce="cdc939d7"
Contact: Anon <sip:nnnnnnn@192.168.100.4:5060>;expires=3600  ** This is the default set on the ATA
User-Agent: Linksys/SPA3102-3.2.6(GWa)
Content-Length: 0Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFERSupported: x-sipura

• <<194.165.60.134:5082(329)       ** Not part of SIP.
• <<194.165.60.134:5082(329)       **

**This is the reply from the registrar server - successful registration, valid for 30s**

SIP/2.0 200 OK
To: Anon<sip:nnnnnnn@sip.plus.net>;tag=63bd6513
From: Anon<sip:nnnnnnn@sip.plus.net>;tag=b7ced3d32bab9beo0
Via: SIP/2.0/UDP 192.168.100.4:5060;branch=z9hG4bK-10f58fc3
Call-ID: b6bf3e73-e8b44ef3@192.168.100.4
CSeq: 36530 REGISTER
Contact: Anon<sip:nnnnnnn@192.168.100.4:5060>;expires=30    ** This is the registrar server time,
Content-Length: 0                                                the ATA uses this**

• RegOK. NextReg in 28 (1)                            **    More debug & helpful stuff, not

RSE_DEBUG: unref domain, legacy-nat.plus.net           **     part of SIP. Shows the ATA will
RSE_DEBUG: last unref for domain legacy-nat.plus.net   **   register again in 28s. Just what we want.


====================================================================================================

Registration via the new NAT server
-----------------------------------

This time the ATA was set for 120s, the server replies with the same value, but incoming calls
 will only connect for the first 30s (or so, see my previous caveat). Authentication is now used.
The "stale" parameter in the Proxy-Authorization header field of the 407 message seems to be
present only if the "expires" time is longer than 30s.

syslog server(port:514) started on Sat Jan 30 00:17:38 2010  **
RSE_DEBUG: reference domain:nat.plus.net                     **    Not SIP mesages.

• ->79.135.125.160:5082                                     **
• ->79.135.125.160:5082                                     **

**The register request**

REGISTER sip:sip.plus.net SIP/2.0Via: SIP/2.0/UDP 192.168.100.4:5060;branch=z9hG4bK-a8aa0698
From: Anon <sip:nnnnnnn@sip.plus.net>;tag=663a2ed481a573o0
To: Anon <sip:nnnnnnn@sip.plus.net>Call-ID: b6bf3e73-e8b44ef3@192.168.100.4
CSeq: 37105 REGISTERMax-Forwards: 70
Proxy-Authorization: Digest username="nnnnnnn",realm="newsip",nonce="4b637abd00002d81e3f9835345585889af8d9ae178eedb94",uri="sip:sip.plus.net",algorithm=MD5,response="cadf5375e50301a5c1f4c4d31ea4fffa",qop=auth,nc=00000002,cnonce="eba66a51"
Contact: Anon <sip:nnnnnnn@192.168.100.4:5060>;expires=120   ** My ATA set to 120s**
User-Agent: Linksys/SPA3102-3.2.6(GWa)
Content-Length: 0Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura

• <<79.135.125.160:5082(531)    **  Not part of
• <<79.135.125.160:5082(531)    **    SIP

SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 192.168.100.4:5060;rport=5060;received=87.115.43.31;branch=z9hG4bK-a8aa0698
From: Anon <sip:nnnnnnn@sip.plus.net>;tag=663a2ed481a573o0
To: Anon <sip:nnnnnnn@sip.plus.net>;tag=14594fa2c5ed7a6c6e0806b484dcbe6b-0d31
Call-ID: b6bf3e73-e8b44ef3@192.168.100.4CSeq: 37105 REGISTER
Proxy-Authenticate: Digest realm="newsip", nonce="4b637b3300003fb5b32a22b6d44a77d3fc39e3a54121851b", qop="auth", stale=true   **The stale parameter**
Server: OpenSIPS (1.5.3-notls (i386/linux))Content-Length: 0

RSE_DEBUG: reference domain:nat.plus.net   **   Not part of

• ->79.135.125.160:5082                   **     SIP
• ->79.135.125.160:5082                   **

REGISTER sip:sip.plus.net SIP/2.0Via: SIP/2.0/UDP 192.168.100.4:5060;branch=z9hG4bK-dfa6b95d
From: Anon <sip:nnnnnnn@sip.plus.net>;tag=663a2ed481a573o0
To: Anon <sip:nnnnnnn@sip.plus.net>
Call-ID: b6bf3e73-e8b44ef3@192.168.100.4
CSeq: 37106 REGISTER
Max-Forwards: 70
Proxy-Authorization: Digest username="nnnnnnn",realm="newsip",nonce="4b637b3300003fb5b32a22b6d44a77d3fc39e3a54121851b",uri="sip:sip.plus.net",algorithm=MD5,response="0730eb7891b8aa220ac34d75f6071a13",qop=auth,nc=00000001,cnonce="a6554c5d"
Contact: Anon <sip:nnnnnnn@192.168.100.4:5060>;expires=120
User-Agent: Linksys/SPA3102-3.2.6(GWa)
Content-Length: 0Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura

• <<79.135.125.160:5082(434)   **   Not part of
• <<79.135.125.160:5082(434)   **      SIP

**The reply from the registrar, successful registration, valid for 120s!!**

SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.4:5060;rport=5060;received=87.115.43.31;branch=z9hG4bK-dfa6b95d
From: Anon <sip:nnnnnnn@sip.plus.net>;tag=663a2ed481a573o0
To: Anon <sip:nnnnnnn@sip.plus.net>;tag=14594fa2c5ed7a6c6e0806b484dcbe6b-c724
Call-ID: b6bf3e73-e8b44ef3@192.168.100.4CSeq: 37106 REGISTER
Contact: <sip:nnnnnnn @192.168.100.4:5060>;expires=120     ** The server returns the same value as the original request, 60s minimum**
Server: OpenSIPS (1.5.3-notls (i386/linux))
Content-Length: 0

• RegOK. NextReg in 118 (1) ** Not a SIP message, but shows that the ATA won't register again

                                  for 118s. Not what we want. It appears that incoming calls won't
                                  be connected for the last 88s of this. If the ATA is set to 3600,
                                  they wait 59m30s... maybe**
====================================================================================================

Hi

Spotted a setting you should not be using I think

Proxy-Authenticate: Digest realm="newsip", nonce="4b637b3300003fb5b32a22b6d44a77d3fc39e3a54121851b", qop="auth", stale=true   **The stale parameter

I had thought newsip was only to be used with nokia mobile phone

Can I have your thoughts on this please misterW?

Puddy

No, its fine puddy. The realm is actually correct as newsip. Strictly speaking an authentication id and password is associated with a realm. So when a SIP client tries to authenticate with a registrar it sends the authentication id/pw corresponding to the realm requested by the registrar in the '407 authentication required' response.
Most SIP clients assume that  any authentication id/pw with which they have been configured is valid for ANY realm and therefore when the 'newsip' realm is sent by the registrar they just reply with the id/password irrespective of any realm they might have been configured with. The Nokia SIP client is, however, very picky ( but technically correct ) in that if you don't set its realm to 'newsip' then when it gets an authentication required for the realm 'newsip' it refuses to authenticate on the basis that it doesn't have an id/pw for that realm. Bottom line is that most clients you can put anything ( including newsip ) in the realm and it will work BUT the Nokia client MUST have the realm correctly configured as 'newsip'.

I thought you reject my thoughts when I said you can put anything in (biker) with is mobile phone problems?

My next idea  changed to the new sip.plus.net  and delete legacy sip.plus.net

 i cannot see natproxy.plus.net anywere but can you change the ip number address to natproxy.plus.net:5082 instead do you think it should work?

Puddy|

But he was trying to use a Nokia E65 IIRC. We did discover during his problems that you appear to be able to put anything in the 'registrar server' on the Nokia client, as long as you are using the Outbound proxy. That may be true of all clients, but I've not tried it. 

I think 'tp' has removed some details from the trace, leaving just the SIP messages.
These look like the addresses for the natproxy, so it must be in the configuration somewhere.

Have a look on this sitehttp://www.callcentric.co...rt/device/linksys/spa3102 to see if you can config the setting with my plusnet settings good luck!!!

I have checked the setting needed and they state the only setting you need are the same as the pap2adapter settings  listed nothing else should be changed so you should think about reseting your linksys device then make sure your router should allow  DHCP setup that way you dont need to enter dns submast ip address dns 1 or dns 2 it works that out itself which is why you should reset your spa 3102

Your linksys spa 3102 should show the settings in the same boxes as the pap2
and input these settings only and in the same format

Line Enable:  yes
sip port :5060 try 5062 for line 2
proxy :sip.plus.net                  Register: Yes
Make Call Without Reg: No       Register Expires: 3600
Ans Call Without Reg  :  No

Display Name: sip  id number    User ID: sip id number
Password: sip password           Use Auth ID: Yes
Auth ID: sip id number

Audio Configuration

Preferred Codec:G7LLu            Silence Supp Enable: no
Use Pref Codec Only:No           FAX CED Detect Enable:No
DTMF Tx Method: INFO

Line 1  Advance Settings

Proxy and Registration  

Outbound Proxy:nat.plus.net:5082 or try natproxy.plus.net:5082

save settings

United Kingdom Regional Settings

Dial tone: 350@-19,440@-22;10(*/0/1+2)
Ring back: 400@-20,450@-20;*(.4/.2/1+2,.4/2/1+2)
Busy tone: 400@-20;10(.375/.375/1)
Reorder tone: 400@-20;10(*/0/1)
SIT 1 tone: 950@-16,1400@-16,1800@-16;20(.330/0/1,.330/0/2,.330/0/3,0/1/0)
MWI dial tone: 350@-19,440@-22;10(.75/.75/1+2)
CWT1 cadence: 30(.1/2)
CWT2 cadence: 30(.25/.25,.25/.25,.25/5)
CWT frequency: 400@-10
Ring 1 cadence: 60(.4/.2,.4/2)
Ring 2 cadence (BT Call Sign): 60(1/2)
Ring 3 cadence (BT Ring Back): 60(.25/.25,.25/.25,.25/1.75)
Ring 4 cadence: 60(.4/ .8)
Ring 5 cadence: 60(2/4)
Time Zone: GMT
FXS Port Impedance: 370+620||310nF
Caller ID Method: ETSI FSK With PR(UK)
Daylight Saving Rule: start=3/-1/7/2:0:0;end=10/-1/7/2:0:0;save=1:0:

UK dial plan
this will change problems when dialing number

( *x. | **x. | 0xxx xxx xxx. | 186 xxx xxxx | [1-8]xx | [1-8]xxx | [1-9]xx xxxx | 00 xxxxx x. | 141 0 x. | 1470 0 x. )

If you get this problem

Applied al lthe settings that were listed by Puddy but couldn't receive incoming calls.
The "Use Outbound Proxy" box  has to be set to Yes

 


 

Hello,

It looks as though my imperfect explanations have caused some confusion. The formatting of the logs
went awry in a few places, but it's all there.

 Puddy wrote "I have checked the setting needed and they state the only setting you need are the
same as the pap2adapter settings  listed nothing else should be changed so you should think about
reseting your linksys device then make sure your router should allow  DHCP setup that way you dont
need to enter dns submast ip address dns 1 or dns 2 it works that out itself which is why you
should reset your spa 3102"

I don't have any problem setting up the SPA, indeed it's worked well for months using the old NAT
proxy and still does. I'm using fixed IPs on the LAN here. In the past I have temporarily used the
SPA as a router as well as an ATA but at present it sits behind a separate router-cum-firewall box
which is it's normal configuration.

You can see from the logs that, using the old NAT proxy (legacy-nat.plus.net) all works as it
should. The default registration expiry time; 3600s, the same as in Puddy's settings for the PAP2,
is "overwritten", as it were, by the correct value, 30s, sent by the registrar in the "Contact"
header field of the "200 OK" reply like this:-
 "Contact: Anon<sip:nnnnnnn@192.168.100.4:5060>;expires=30"
The ATA will then next register in 28s.

If I change the NAT proxy to the new one (nat.plus.net, I'm not setting IP addresses), the
registrar (I suspect it's now a different one) replies with the same value as the ATA expires value
(although it has a 60s minimum). Like this:-
 "Contact: Anon <sip:nnnnnnn@192.168.100.4:5060>;expires=3600"

Note that the example in the log that I posted uses 120s, but you can see the principle.

The ATA will then not register again for 3558s, just before it thinks the previous registration
expires. The trouble is (I think) that the registration actually expires after 30s. After that,
incoming calls aren't connected. The caller doesn't hear anything. When the next registration is
made (the longest I've actually tried is 120s), the caller suddenly hears ring tone and the
telephone rings.

Note that outgoing calls aren't affected at all by this, they work properly throughout, so unless a
caller complains or you set up a test yourself, you don't know.

If anyone else is using a 3102 or similar device (I think a PAP2 would do) with the default 3600
expiry time set, perhaps they could set up a syslog server (will the PAP2 send syslog messages?)
and see what happens when registering via the old and the new NAT proxies. Actually trying incoming
calls is a bit awkward, because you need to set a longish (say 120s) expiry time, wait until it's
about half way through (the 3102 info page tells you how long is left, you need to keep refreshing
it though) then make a call to the IP line 'phone number (I'm using a cellphone to do this, I've
not tried the URL). You should not hear anything, and the 'phone connected to the ATA won't ring,
until the 120s has expired, then - voila, ring tone appears and the 'phone rings. At least, that's
how mine behaves.

Following the suggestion by MisterW "I suggest you try setting the 'Auth ID' as my guess is that
your registration isnt quite correct." I've now put my SIP ID in there, but nothing seems to have
changed. I've not run any more syslogs but the system is still behaving in the same way. I've also
set up a call in the "not connected" state, if you see what I mean, and there is no sign of it on
the SPA - it continues to show the line as "idle".

Maybe I'll have a go with a ticket to PN to see what transpires there. Although I've decided that I can
live with it as it is, I'd like to know what's going on.

Best wishes,
John.

Hi John,
As I understand the registration mechanism when using the outbound proxy, its as follows:-
Your ATA sends the register request to the OB proxy, it then registers on your behalf with the registrar server with the normal 3600 secs timeout.
It then signals a shorter expiry back to your ATA to ensure that a connection is maintained through any NAT mapping in your router. As to where the OB proxy gets the registrar address is doubtful, you would expect that it uses the details in the register request BUT we did discover some time ago that ( certainly with some Nokia SIP clients ) you can put anything in the registrar details and it still registers. My guess is that since both the OB proxy and registar are Gradwell's, the OB proxy KNOWS what the registrar is and therefore ignores what is sent in the register request. 
From what you have described it does look a bit odd. It does look like the OB proxy is 'lying' to you about what its registration timeout is actually set at. I'd have an experiment myself with X-Lite ( since its got pretty good logging and my C475IP hasn't ) but I'm not sure I could reproduce the problem. Normally I don't use the nat proxy, my router is a 2700hgv which has a working SIP ALG ( Application layer gateway ). This removes the need to use the outbound proxy for NAT traversal since the SIP ALG does it. Therefore my registration is with sip.plus.net directly ( and with the normal 3600 secs expiry ) rather than via natproxy.plus.net. I'm not sure what will happen if I configure X-Lite to use the proxy, the SIP ALG might still get in the way intercept the traffic. I can't even try it in the office since we have a 2700 there as well!!.
Nevertheless if I've got some time at the weekend I might just have a play with X-Lite and natproxy and see what happens...

Regards,
Ian

Apologies if I missed it.... but have you tried doing a factory reset, and then re-enter all the info from scratch?

It almost certainly won't make any difference, but equally, it is probably worth ruling out so you know it isn't based upon a dodgy setting somewhere that is reporting one thing, but is acting upon a different setting. Whilst rare, it isn't un-heard of...

As I say, if you've already tried this, then ignore me.

Hi, Ian.

You wrote .."Your ATA sends the register request to the OB proxy, it then registers on your behalf
with the registrar server with the normal 3600 secs timeout. It then signals a shorter expiry back
to your ATA to ensure that a connection is maintained through any NAT mapping in your router."

That's what I thought, too, but I can't remember where from. Although I don't know about the 3600
value.

 "...My guess is that since both the OB proxy and registar are Gradwell's, the OB proxy KNOWS what
the registrar is and therefore ignores what is sent in the register request. "

I suppose they could even be the same piece of kit. If it's a full blown SBC it could do anything.
I've just tried quickly altering the registrar address (to sip9.plus.net) which doesn't exist (at
least a DNS check here fails). The SPA shows "registration failed". I'm not sure if this is a valid
test of your guess. If you can work a better one out, I'll try it.

"From what you have described it does look a bit odd. It does look like the OB proxy is 'lying' to
you about what its registration timeout is actually set at."

That is an excellent way of putting it - wish I'd thought of it ... I'll use it in PN's ticket
(which I've not done yet, but will keep you posted here).

Note that it's only the "new" OB proxy which behaves like this. The old one worked "properly" and
still does.

"I don't use the nat proxy, my router is a 2700hgv which has a working SIP ALG..."

My router is a Netgear FVS114, which I'm pretty sure doesn't know what SIP is.

Now, to xp

Hello,

"...but have you tried doing a factory reset, and then re-enter all the info from scratch?"

No, you didn't miss it, 'cos no I haven't done it. You are right, of course. But to be honest I'm
reluctant to re-enter all that stuff. There's a great deal of it, especially dial plans and
suchlike, which I'm bound to get wrong somewhere... so, at the moment I'm using the fact that the
"old" proxy works properly to indicate that my settings are usable, and so give me an excuse to
avoid having to re-enter it all. It really would need to be a "service affecting" problem to make
me do that. Plus I'll never get to know....  but I know strange things can happen....  all that
typing.... no... please... no... I keep the settings backup as the usual htm file so I suppose I could try that if I get desperate. Trouble is I don't do backups as often as perhaps I should so there would be more tweaking to do.

Many thanks to you both,
John.

I don't blame you..... I am NEVER in a hurry to go through that sort of process myself when troubleshooting... especially when it seems to be unlikely to make a difference (but even if it might be the cause, I will often look for other ways to solve it first! Using factory defaults as the very last recourse!)

Sorry, I don't know the units in question, but do you configure them using a web browser? If so, you might find ScrapBook plugin for Firefox useful.

You can point it to a page and tell it to capture all linked pages to a depth of x deep by following all links. If you set it to only capture from that domain (eg the devices IP address I assume), then it won't hop out onto capturing the whole web (eg it will ignore any links out to the manufacturers webpage etc).

When I was having problems with my Billion VOIP router, I was able to leave it for a while spidering my config pages, which left with with an archived set of all the config pages settings in a fixed but browsable form (quicker and simpler than taking a screen shot of every page, and you can still copy & paste the resulting archived text!). I was then able to have the archive open in one tab, and the now blank router config pages open in another. It was then just a case of copy and pasting each field over. For complex pages like dial plans etc you would want to make sure it had captured all the info correctly before doing the factory reset... but I never saw any problems with my router & dial plans

But even if you aren't going to do a factory reset, looking into Scrapbook to capture all your setting whilst it is working could be a good way of getting a backup now for peace of mind purposes anyway! (You can use it on all your web configured devices!).

The settings that worked for me, tend to be...
Visit main page of device and click on "Capture page" in ScrapBook menu. Set to run about 7, 8 or 9 deep (follow your nose on other settings)
Set it running the capture, but immediately click "pause" button. Then choose the "filter" link, and select "restrict to domain". Now click "start" again... and leave it to capture the lot.

The tool is designed to capture any webpage intact (so like a bookmark that grabs the whole page in it's current form!). This is great for other uses too, where the info on the page might change or be deleted, and you want to keep a local copy. I don't use it a lot, but for the times it is useful, it is VERY useful...

Hope you get to the bottom of the problem....

Mike

The other area worth checking is whether your device is running the latest firmware version. Again it might make no difference, or there might not be a newer firmware available, but if there is, it might be worth investigating what it fixes... and maybe consider trying the firmware upgrade at the same time as running a restore to factory defaults...

To be honest, I expect the investigations you are already doing are most likely to yield the answer or a work-around... but thought I'd mention all the options...

Mike

John,
I've just gone back over the thread where registering with the wrong registrar seemed to work, It's here  http://community.plus.net....php/topic,78851.144.html , pages 10 & 11 are the interesting ones. It looks from there as though it was only the Nokia SIP client that managed to resister, apparently I tried it then with Twinkle softphone and it wouldn't, so that concurs with your recent tests. So maybe I'm wrong about the proxy knowing the server URL.

I'm still hopeful of having time this weekend to run some tests myself with either Twinkle or X-Lite and see if I can get some logs. I might even go and dig out my old BT Voyager 10v ATA but I'm not sure how good its logging is.

Ian