Dale Worley wrote:
> On Thu, 2009-02-12 at 09:43 -0600, Mitchell, Kenny (Ineos) wrote:
>> Part of my problem appears to be related to registering the gateway with
>> SipX.  The gateway has various options for registering by endpoint or by
>> gateway, but what do I actually set up on the SipX config to get it to
>> register?  Do I need to set anything?  A fake extension with a username
>> and password for each port?  One for the gateway as a whole?  My calls
>> out are hitting the gateway (I can see the call count incrementing in
>> the log) but it is logged under the 'failed due to no routing' section.
> 
> I may be out of date, but the scheme that has worked in the past is
> this:  First, consider the extension numbers (SIP "user part") that the
> gateway will be accepting calls for.  (I expect that there is one
> extension number per port on the FXO, but it's possible you could
> configure them to be ganged or trunked, so calls to a single extension
> number could go out any of the ports, as if the FXO was simulating a
> multi-line phone.)  Configure each of these users on sipX, with a
> password.  Configure the gateway to submit registrations for each of
> these users, paired with the appropriate FXO ports.  Then calls to the
> extensions should be routed to the FXO gateway, which should accept them
> and route them out the appropriate ports.
> 

I am not sure if this is good advice.
sipXecs does not expect that you'd be registering FXO ports. Only FXS ports
need to be registered.

Please read this:
http://sipx-wiki.calivia.com/index.php/HowTo_configure_AudioCodes_SIP_Gateway_with_sipX

And tell us exactly what's not working for you.
D.

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

Reply via email to