[Spce-user] Peering (Source & Pestination) IP addresses
Aziz Palmer
Aziz.Palmer at AirFIBER.com
Fri Nov 7 08:16:26 EST 2014
Hi SPCE Team
Is this possible if so how do I go about accomplishing it
Currently when an inbound calls comes from a sip peer it matches the source ip address of the sip peer. I have setup multiple alias IP addresses and would like to match up not only the ip address of the peer but the alias ip address it is listening on?
Thank you!
________________________________________
From: Spce-user [spce-user-bounces at lists.sipwise.com] on behalf of Daniel Grotti [dgrotti at sipwise.com]
Sent: Friday, November 07, 2014 1:21 AM
To: spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Peering (Source & Pestination) IP addresses
Hi,
I'm not sure if I understood correctly, but in general what you can do is to create 2 Peering, let's see with the same IP:port:
Peering A
Remote_IP:Remote_Port <-> Local_IP:5060
Peering B
Remote_IP:Remote_Port <-> Local_IP:5566
In this way remote Peering A should connecto to your port 5060 and remote peer B should configure itself to connect to you to port 5566.
Now, they expect you to send them packet via the same ports, so from 5060 to peer A, from 5566 to peer B.
What you need to do is to set up the peer preferences 'outbound_socket' on peer A, selecting Local_IP:5060 and on peer B the other socket Local_IP:5566.
Is it what you were looking for ?
Daniel
On 11/06/2014 09:35 PM, Marc Storck wrote:
I'm interested by this featute as well.
In my case a peering could be setup between an remote ip:port tuple and an alternative local port. I don' necessarily need to use an alias Local IP.
In the end this should provide the following:
Peering A
Remote_IP:Remote_Port <-> Local_IP:5060
Peering B
Remote_IP:Remote_Port <-> Local_IP:5566
Where for Peering A and B the remote_ip and remote_port are identical, e.g. In both cases 203.0.113.1:5060.
While on the SPCE side Peering A would use 198.51.100.1:5060 and Peering B would use 198.51.100.1:5566, alternatively Peering A uses 198.51.100.1:5060 and Peering B uses 198.51.100.2:5060.
Of course SPCE would have to comply with this as well for outbound calls to Peering A and Peering B respectively.
Regards,
Marc
On 6 nov. 2014, at 20:38, Aziz Palmer <Aziz.Palmer at AirFIBER.com<mailto:Aziz.Palmer at AirFIBER.com>> wrote:
Good Afternoon,
Not sure if this is possible but here is what i'm hoping for:
Currently when an inbound calls comes from a sip peer it matches the source ip address of the sip peer. I have setup multiple alias IP addresses and would like to match up not only the ip address of the peer but the alias ip address it is listening on?
Thank you again for all your help SPCE Team has been providing us!
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>
https://lists.sipwise.com/listinfo/spce-user
_______________________________________________
Spce-user mailing list
Spce-user at lists.sipwise.com<mailto:Spce-user at lists.sipwise.com>
https://lists.sipwise.com/listinfo/spce-user
More information about the Spce-user
mailing list