milosz wrote:
> you can have the patton route the calls directly to the second gateway
> (instead of going through sipx).  not sure if that's what you want.  i
> believe there is an example of it in the smartware manual.
> 

Yes, this is what I've already done, but in a large organization, with 
several traditional pbxs, doing this way could be a nightmare, because 
you have t manage all direct connections between gateways. The goal is 
to have the simplest configuration on the gateway, and use Sipx as a 
glue between traditional pbxs and/or PSTN. This way I could cut down 
costs, eliminating the need for directed connections between pbxs and 
dedicated PRI interfaces to the PSTN.

> the other thing you could do is create a user for the 200 extension in
> sipx and have the 4960 register it (like with an fxs user).  then the
> call routing through sipx will work.  i can send you an example if you
> tell me what release of the firmware you are running.
> 

thanks, but this is not the best way to do that: the gateway is 
connected to pbxs with hundreds of extensions, so it is not confortable 
to create users on the gateway for all of them...

> again, this is stuff you can email supp...@patton.com about, i have
> found them to be very helpful.
> 

I know, but I don't need examples in Smartware configuration: the point 
is to understand why sipx need authentication when it routes call 
between gateways, even if rules in the dial plan are set with no 
particular permission, and if there is a way to bypass/disable 
authentication.


Thanks,

Max


-- 

Massimo Vignone
UniMORE - Servizi Informatici - Reti e Sistemi

Phone: +39.059.2058032  Fax: +39.059.2058034
sip:massimo.vign...@unimore.it  ISN:8032*881


_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to