Hi Brian, Take a look at the UAC module - it can do user auth - http://www.opensips.org/html/docs/modules/devel/uac.html
you can use the attr field in the drouting module to store the username and password required by that GW and dynamically inject them into UAC. Regards, Bogdan [email protected] wrote: > Hello list, > > Has anyone had this problem of wanting to forward a INVITE to a PSTN > gateway, and not being able to authenticate? > > The UAC (A) sends the INVITE to a OpenSIPS proxy (B) who replies 401 > Unauthorized. A sends B a new INVITE with A's credentials and B's > realm and nonce. > > B forwards this INVITE to a gateway (C) who replies 401 Unauthorized. > At this point the OpenSIPS proxy must somehow (like a B2BUA?) > provide the gateway with authentication credentials. > > The gw module is useful for this but fails to provide any means of > authenticating with the new gateway C. > > I believe the dispatch module does something similar, but it's > unclear just what the docs mean by 'hashing' in this case. Where > is the dispatcher module taking the username and password from? > > Is carrierroute really what should be used in this case, or some > combination of modules... maybe uac for the authentication? > > Regards, > Brian > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
