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

Sat Nov 8 07:43:34 EST 2014

Well ... let's do it from the begging ... 

-How SPCE rate and bill ? ... based on UUID of the call. 
-How SPCE assign UUID to a call?, looking if it's a trusted IP or asking and authenticating the call credentials. 

So based on that 2 premises ... how do you want to bill 2 different entities that share equipments? ... the only answer is telling them to send calls authenticated with user/password ... and do not authenticate them based on IP .... because as fas as the last time I check the templates ... SPCE do no take into account the src_port or the dst_port of a SIP-Request to look for what UUID assing to the call. 

And going futher ... how do you rate and bill ONE entity that sends you traffic for the SAME destination, but whant to use different quality routes ? ... the only answer ... WITH PREFIXES. 

How you undestand the point now ... 

Best regards 

----- Mensaje original -----

De: "Marc Storck" <mstorck at voipgate.com> 
CC: spce-user at lists.sipwise.com 
Enviados: Sábado, 8 de Noviembre 2014 12:06:02 
Asunto: Re: [Spce-user] Peering (Source & Pestination) IP addresses 

OK, now imagine that Peer A and Peer B are 2 different entities that happen to share equipment for some reason. 

Regards, 

Marc 

On 8 nov. 2014, at 12:10, Raúl Alexis Betancor Santana < rabs at dimension-virtual.com > wrote: 

You could do that, without having to mesh with 'new local ports'. 

Do as everyone on this industry does ... Use prefixes for the routes. 

If you have peer A sending you traffic for destination B ... Abd you offer him 2 qualities ... Tell them to prefix the traffic before sending them to you. 

Doing otherwise its overcomplicating things unnecesary. 

Best regards 
El 08/11/2014 10:49, Marc Storck < mstorck at voipgate.com > escribió: 
There are other cases where this doesn't work and you would really need to distinguish 2 peers by the local port they are connecting to. For example both peets could have different rates for the very same destinations, e.g. 

Peer A pays 0.11€ for destination +43780 
Peer B pays 0.2345€ for destination +43780 

Or 

Peer A has access to local destinations only 
Peer B has access to transit 

Regards, 

Marc 

> On 7 nov. 2014, at 17:36, Raúl Alexis Betancor Santana wrote: 
> 
> If I undestood you ... what you whant it's inbound billing based on the pair src_ip:src_port <-> dst_ip:src_port ... JUST because your upstream carrier send all to you from the same IP? 
> 
> Is that wright? ... 
> 
> In any case ... you know the DID you will receive call to, so better apply inbound billing profiles based on the DID, and not based on the peer. Must review the inbound billing features, because we don't use it ... but I think could be done that way much better than trying to open a new dst_ip:dst_port for billing purporses. 
> 
> Best regards 
> 
> ----- Mensaje original ----- 
> De: "Aziz Palmer" 
> Para: "Daniel Grotti" , spce-user at lists.sipwise.com 
> Enviados: Viernes, 7 de Noviembre 2014 16:17:18 
> Asunto: Re: [Spce-user] Peering (Source & Pestination) IP addresses 
> 
> Hi Daniel, 
> When provisioning DIDs from our upstream providers we have Tier 0-2 which is one rate and 3-5 a different rate. they both come from the same IP address. If I can associate the destination IP address along with the source address then i can associate 2 billing profile from one specific source IP address. 
> 
> I rather not be constantly updated the billing profile and unfortunately I don't have an inbound rate desks and - I asked my upstream provider for a inbound rate deck (one of my providers uses zipcodes as a rate deck, making it extremely time intensive converting to DIDs). I think it would be much more simple if i can track the calls not only from the source IP but the destination IP. 
> 
> Tank you for looking into it. 
> 
> ________________________________________ 
> From: Daniel Grotti [ dgrotti at sipwise.com ] 
> Sent: Friday, November 07, 2014 5:39 AM 
> To: Aziz Palmer; spce-user at lists.sipwise.com 
> Subject: Re: [Spce-user] Peering (Source & Pestination) IP addresses 
> 
> Hi, 
> I don't see the reason behind that, why you would need to fetch the 
> extrac_socket on SPCE as well. 
> Currently is not possibly, if the call coming in from the peer IP, that 
> IP is trusted, that's it. 
> 
> Maybe you can be more specific on that and explain what do you want do 
> achieve . 
> 
> Thanks, 
> Daniel 
> 
> 
>> On 11/07/2014 02:16 PM, Aziz Palmer wrote: 
>> 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 > 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 
>> https://lists.sipwise.com/listinfo/spce-user 
>> 
>> 
>> 
>> _______________________________________________ 
>> Spce-user mailing list 
>> Spce-user at lists.sipwise.com 
>> https://lists.sipwise.com/listinfo/spce-user 
> 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 
> _______________________________________________ 
> Spce-user mailing list 
> Spce-user at lists.sipwise.com 
> https://lists.sipwise.com/listinfo/spce-user 

_______________________________________________ 
Spce-user mailing list 
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/mailman/private/spce-user_lists.sipwise.com/attachments/20141108/20e638e4/attachment.html>