Hi Paul,
I don't want to add another box.. Neither to let the router do destination
NAT..
So I have played a bit with the ip addresses to see what will work and what
wont..
Here are 3 versions of what didn't worked.. There was always the same
result: the provider didn't send the answer to sipx because the sip packets
were coming from the wrong address.
Example1:
System -> Servers - > NAT -> Public IP address = 89.202.222.55
Devices -> Gateways -> ITSP Account -> "Use public address for call setup" -
checked
Example2:
System -> Servers - > NAT -> Public IP address = 89.202.222.55
Devices -> Gateways -> ITSP Account -> "Use public address for call setup" -
unchecked
Example3:
System -> Servers - > NAT -> Public IP address = 10.160.250.94
Devices -> Gateways -> ITSP Account -> "Use public address for call setup" -
unchecked
The only working solution for the trunk to the provider is this:
System -> Servers - > NAT -> Public IP address = 10.160.250.94
Devices -> Gateways -> ITSP Account -> "Use public address for call setup" -
checked
The bad thing is that the remote worker doesn't work with this
configuration.
So my problem remains.
Is SipX considers to be working with providers which offer private ip
addresses on sip trunks?
In my opinion, this could be solved in two ways:
Because the sip trunk needs the special IP which is on the router, but it's
not a real public IP, there should be a way to put the address direct on the
sipxbridge.
Is there a way to put the IP in the configuration on sipXbridge?
perhaps if I put global-address = 89.202.222.55
external-address = 10.160.250.94
local-address = 10.4.62.2
could this work somehow? what is the "external-address" used for?
The second idea is that I try to put the real ip address of the server into
FENT configuration to make the remote workers to work.. Is it possible?
Is perhaps Internet Calling somehow connected with it so i could use it?
Does anybody have an idea?
Thanks,
Irena
2010/12/9 Paul Scheepens <[email protected]>
> Hi Irena,
>
> If you don't want to add any box then I think your only solution is to do
> it in the router.
> Other option could be to add a gateway (sipX box) to handle Provider1.
>
> Paul
>
> Irena Dolovčak <[email protected]> wrote on 08-12-2010 10:34:05:
>
> > Hi Paul..
> > I tried your idea.. but it didn't helped.. :(
> >
> > to make it more clear.. here is my voip network scheme..
> >
> > http://img573.imageshack.us/img573/999/myscheme.jpg
> >
> > so what happens..
> > the local ip of my server is 10.4.62.2.. the public ip from the
> > router is 89.202.222.55 (dynamic)
> >
> > when the server tries to contact provider2 it has to send the sip
> > invite with 10.160.250.94 address.
> > and when the server contacts remote phone2, it should send the public
> ip..
> >
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
--
Irena Dolovčak
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
