[Spce-user] Peering (Source & Pestination) IP addresses

[Marc Storck]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20141106/a998f9c5/attachment-0001.html>