The basic logic is that when the proxy receives the INVITE from Callmanager, it believes that the From URI is identifying a user on the sipXecs system. In order to get that user to present credentials, it returns a 407 response. Apparently Callmanager does not have credentials for the realm, so it abandons the call.
There are a number of ways of attacking the problem. To start off with, is the caller really a member of the domain? The From URI is <sip:[email protected]>, is that really a correct identification of the caller? It is possible that the user is better identified as part of some other domain, and Callmanager should be reconfigured to put a different domain in the URI. A second question is whether user 6005 has sipXecs credentials. If 6005 exists *only* on the Callmanager side, just deleting 6005 from the list of defined users in sipXecs will eliminate the 407. You could also look into providing Callmanager with SIP credentials. I expect that there is some way to configure that. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
