Ray Burkholder
2004-Jan-05 17:45 UTC
[Asterisk-Users] Identifying the Originating Cisco SIP Gateway
I have several Cisco SIP gateways sending calls to Asterisk. Because the gateways don't have user-agents, they don't authenticate with Asterisk. And because they don't authenticate, they use the default context in the sip.conf file. Is there a way to either: A) identify the inbound gateway with a variable, in channel info, or the manager interface? If there was a ${SIPDOMAIN} for the originator rather than the destination, that would be cool, or B) make the inbound gateway use the sip.conf file section belonging to it via the host= line in the sip.conf file without user authentication, or C) some other way I have yet to fathom I'm trying to differentiate between legitimate gateways that initiate calls vs other gateways that should get a very limited inbound capability. Ray Burkholder ray@oneunified.net http://www.oneunified.net 704 644 6999 x2002 -- Scanned for viruses and dangerous content at http://www.oneunified.net and is believed to be clean.
Andres
2004-Jan-05 21:28 UTC
[Asterisk-Users] Identifying the Originating Cisco SIP Gateway
On Monday 05 January 2004 19:45, Ray Burkholder wrote:> I have several Cisco SIP gateways sending calls to Asterisk. Because the > gateways don't have user-agents, they don't authenticate with Asterisk. > And because they don't authenticate, they use the default context in the > sip.conf file. > > Is there a way to either: > A) identify the inbound gateway with a variable, in channel info, or the > manager interface? If there was a ${SIPDOMAIN} for the originator rather > than the destination, that would be cool, or > B) make the inbound gateway use the sip.conf file section belonging to it > via the host= line in the sip.conf file without user authentication, orLast time I checked this, it worked as you want only if your SIP Gateways are on port 5060. I was able to differentiate via the host=line, but as soon as I used a Gateway on a port other than 5060, Asterisk was not able to match the sip.conf entry and it used the default. I did not open a bug report as this was not something we needed at the time. Give it a try and let me know if you see the same thing. Regards, Andres http://www.telesip.net> C) some other way I have yet to fathom > > I'm trying to differentiate between legitimate gateways that initiate calls > vs other gateways that should get a very limited inbound capability. > > Ray Burkholder > ray@oneunified.net > http://www.oneunified.net > 704 644 6999 x2002