I'm seeing 407 (Proxy Authentication Required) returned to incoming invites 
from Vitelity.  We have a no-registration (IP authentication) relationship with 
them so it's possible I've missed something in the setup that would allow 
unauthenticated invites from their IP.
 

This is the response sent to sipxbridge:

Time: 2012-07-20T16:48:16.097000Z
Frame: 4 sipxbridge.xml:354
Source: 192.168.X.24:5060
Dest: sipx.domain.com-sipXbridge

SIP/2.0 407 Proxy Authentication Required
Record-Route: <sip:192.168.X.24:5060;lr;sipXecs-CallDest=LD;x-sipX-done>
From: "+15759565979" <sip:[email protected]>;tag=2014970589
To: <sip:[email protected]>;tag=1R5cwk
Call-ID: [email protected]
CSeq: 102 INVITE
Via: SIP/2.0/TCP 
192.168.X.24:5090;branch=z9hG4bK11c84e5a79571525f8a761d6bcaf2a4c393639;sipxecs-id=3164ecee
Proxy-Authenticate: Digest 
realm="sipx.domain.com",nonce="d98c3b153f9c64d522cd72f9a7c28fde50098bd0",qop="auth"
Server: sipXecs/4.4.0 sipXecs/sipXproxy (Linux)
Date: Fri, 20 Jul 2012 16:48:16 GMT
Content-Length: 0

...which sends this to Vitelity:


Time: 2012-07-20T16:48:16.103000Z
Frame: 6 sipxbridge.xml:365
Source: sipx.domain.com-sipXbridge
Dest: 66.241.X.X:5060

SIP/2.0 407 Proxy Authentication required
Via: SIP/2.0/UDP 
66.241.X.X:5060;branch=z9hG4bK17b48c37;rport=5060;received=66.241.X.X
From: "+15759565979" <sip:[email protected]>;tag=as4b214e18
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 102 INVITE
Server: sipXecs/4.4.0 sipXecs/sipxbridge (Linux)
Supported: replaces
Record-Route: <sip:192.168.X.24:5060;lr;sipXecs-CallDest=LD;x-sipX-done>
Proxy-Authenticate: Digest 
realm="sipx.domain.com",nonce="d98c3b153f9c64d522cd72f9a7c28fde50098bd0",qop="auth"
Date: Fri, 20 Jul 2012 16:48:16 GMT
Contact: <sip:70.57.247.39:5080>
Content-Length: 0

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to