On 11/05/2007 10:23, Eugene Prokopiev wrote: >>> I use this in sip.conf: >>> >>> [general] >>> ... >>> register => login:[EMAIL PROTECTED] >>> ... >>> Why callweaver use sipnet-in as host name? >> >> Your register=> line is incorrect. >> >> From your sipnet-in entry it looks like you should use: >> >> register => login:[EMAIL PROTECTED] >> > Example in sip.conf looks like: > > ;register => 2345:[EMAIL PROTECTED]/1234 > ; > ; Register 2345 at sip provider 'sip_proxy'. Calls from this provider > ; connect to local extension 1234 in extensions.conf, default context, > ; unless you configure a [sip_proxy] section below, and configure a > ; context. > ; Tip 1: Avoid assigning hostname to a sip.conf section like > [provider.com] > ; Tip 2: Use separate type=peer and type=user sections for SIP providers > ; (instead of type=friend) if you have calls in both directions > > So, using hostname is not recommended. Another reason to not use it is > ability to setup context in [sipnet-in] section - I can't do it with > register :( >
Eugene, I'm pretty sure that you need to specify the hostname in the register. It should still use the context in the peer entry with the matching host line. All the example is saying is avoid using the hostname as the section name. That's the way mine was set up and was working. Hope that helps, Paul _______________________________________________ Callweaver-users mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-users
