Hi,

I would like to know how to configure an outbound proxy for outgoing
SIP INVITE messages in Zap v0.2.3's GUI. I've checked that the Service
Route URIs of a Service can to be used to enforce the REGISTER
messages to flow through an outbound-proxy. However, I can't make an
outgoing SIP INVITE message go through the outbound proxy (they always
go directly to the registrar of the B party). As far as I understand,
if the gruu and the outbound proxy are supported by the SIP servers
during the registration (i.e. info about that received in SIP response
of REGISTER), then the outgoing INVITE messages will later flow
through the outbound proxy. Can somebody confirm this? If yes, which
versions of the gruu and outbound drafts are implemented by Zap?

Thanks,
Xavier

Hi Xavier,

On Tue, 2007-08-07 at 09:45 +0200, Xavier Marjou wrote:[...]

Yes, INVITES should traverse the outbound route (unless the registration
yielded a different service route; see RFC3608). This should work
whether or not your server supports gruu.

Are you sure that a) you are registered (as indicated by a green halo
around the identity in the left UI pane), and b) you have selected the
registered identity for the call (from the drop down on the right side
of the menu bar)? If the drop down shows the dummy identity
(sip:thisis(at)anonymous) then zap will try to make the call by directly
contacting the other registrar. 

I know that having to do b) is not intuitive, given that most people
only have one identity :-(
[...]

Zap implements draft-ietf-sip-outbound-01 and draft-ietf-sip-gruu-05, as
well as RFC3608 (Service-Route).


Cheers,
Alex
[...]

Hi Alex

b) was indeed my mistake.

Thanks a lot,
Xavier

[...]