Outbound Proxy settings breaks incoming calls

Hi,using Asterisk 1.6.2.8 . I have set up a Sipgate Trunk registration in sip.conf which works fine for incoming calls
as soon as i use an outboundproxy (which happens to be OpenSIPS) i get the following error message

Call from ‘’ to extension ‘100000’ rejected because extension not found

Registration is working fine with the proxy and the INVITE is arrving at Asterisk on the inbound route but the matching seems
to be broken and i can’t understand why

sip.conf:

[general]
bindport=5062
bindaddr=192.168.0.20
context=default
//outboundproxy=192.168.0.20
//outboundproxyport=5060

register => 100000:123456@sipgate.co.uk/100000

[100000]
type=friend
context=100000
username=100000
secret=123456
host=sipgate.co.uk
host=dynamic
fromdomain=sipgate.co.uk
insecure=port,invite
nat=yes
disallow=all
allow=alaw
canreinvite=no

extensions.conf :

[100000]
exten => 100000,1,Dial(SIP/2000)

Hi, got a little bit further with investigation. It seems that when outboundproxy is set in the general section the inbound calls
go to the context set in the general section rather than the context specified by the peer, this is why i was not getting a match.
Now i need a different context depending on the peer so its no good to me.

I’ve now moved the outboundproxy setting to the peer (ie no longer in the general section). However its not using the outboundproxy. Does it only work in the general section. This post from last year suggests its available on a peer basis

spinics.net/lists/asterisk/msg108267.html

I’ve set it up in my sip.conf like this now,

[100000]
type=friend
context=100000
username=100000
secret=123456
host=sipgate.co.uk
host=dynamic
fromdomain=sipgate.co.uk
insecure=port,invite
nat=yes
disallow=all
allow=alaw
canreinvite=no
outboundproxy=192.168.0.20:5060

Can someone confirm whether it works in the peer section. If not and i have to use it in the general section then how can i redirect the incoming calls from the default context in general to a more a specific peer context (which would also be a solution for me as my outboundproxy will not vary by peer)

Thanks