On Wed, 2008-09-10 at 08:13 +1000, Josh Marshall wrote:
> > Note that the "description" has the 909 prefix, but not the userPattern.
> >
> > The rule you wanted was:
> >
> > <!--Integra-->
> > <description>909</description>
> > <userPattern>909.</userPattern>
> > <permissionMatch>
> > <transform>
> > <user>999{vdigits}</user>
> > <host>10.1.102.2</host>
> > <fieldparams>q=0.9</fieldparams>
> > </transform>
> > </permissionMatch>
> > </userMatch>
>
> I can't believe I did that. Must be from all the fiddling I did. Anyway
> this morning I changed it to:
>
> <!--Integra-->
> <description>test</description>
> <userPattern>909.</userPattern>
> <permissionMatch>
> <transform>
> <user>999{vdigits}</user>
> <host>10.1.102.2</host>
> <fieldparams>q=0.9</fieldparams>
> </transform>
> </permissionMatch>
> </userMatch>
> <userMatch>
>
> I can see in the trace (attached) that it's correctly inviting the
> Gateway on 9991800812393 when I dial 9091800812393
>
> HOWEVER!!
>
> The Epygi Gateway dials 9091800812393 and so sends it out the wrong port
> (in the call statistics on the gateway I see PSTN1-9091800812393 - the
> PSTN1 is the fallback for all calls at the bottom of the gateway
> dialplan)
>
> So looking at the trace I've attached, have I got a problem with my
> sipxecs (3.10.2) or my Epygi Gateway (6FXO firmware 5.0.11)
>From the trace, it looks as though your gateway is making the call based
on the contents of the To header (which, like any correct proxy, the
sipXecs proxy has not modified), rather than the Request URI
(immediately following INVITE on the first line of the request).
This is a bug (and a serious one) in the gateway.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
