|
|
dub
Registration Date: 01.01.1970
Posts:
|
|
|
21.02.2008 15:26 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
|
21.02.2008 17:42 |
|
ren
Grünschnabel
Registration Date: 14.09.2006
Posts: 15
|
|
|
29.02.2008 04:51 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
If you follow all the threads mentioned in the Betamax thread https://forum.voipbuster.com/viewtopic.php?p=58645 (their forum became publicly viewable today) you will notice that any solution will have to involve the help of Betamax's engineers.
This is especially evident in the Voxalot thread which demonstrates their efforts to get it right, since even if the "P-src-ip" header is inserted in the SIP packets, it will have to be recognized (parsed) by their SIP Proxies, so they can individualize the calls from every user, even if they originate from the same PBXes IP.
So it is not as simple as it seems. For the proper implementation of the proposed solution the full support of Betamax's engineers is an absolute requirement.
The way you can help towards this goal, is for all users of Betamax clones to register and post in the above mentioned forum, so our request remains high in their priorities. The number of Betamax trunks mentioned in my post, was the actual number registered across all PBXes servers, on the day I posted my request in their forum.
As you can clearly see the issue remains unresolved, since no Betamax engineer has contacted Pascal so far, to discuss and resolve the widely reported issue. As such it is now up to every affected PBXes and Betamax user to contact Betamax through that thread in their forum, and ask for their cooperation to resolve the issue with Pascal.
If it important to you please report it, so it can hopefully be resolved soon.
|
|
29.02.2008 05:55 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
Again, not as easy as you think |
|
Thanks for your post on the Betamax forum. That is exactly what is needed to get this issue resolved.
Regarding your comment: "Seems to me that BettaMax and Voxalot worked together indeed, but the result seems to be something that doesn't only work for Voxalot, but also for Mysipswitch. As they mention on their forum, it seems to be an universal header, not one that is dependant of any proxies. But who am I to try understanding this and make you try anything anyways."
If you look at the 7th and 8th posts in the 3rd page of the MySIPSwitch forum at www.mysipswitch.com/forum/viewtopic.php?...er=asc&start=20 you will find the following comment from em:
Zitat: |
In my opinion, the Betamax services check both peer's IP address and content of the P-src-ip header, and increment the minutes counters for both of them. If one of them exceeds the FUP limit, charges are applied. However, Voxalot seems to have gained an exemption from Betamax, so in their case only the P-src-ip header is considered. Perhaps, MySIPSwitch could try to talk to Betamax and ask for a similar treatment, on the grounds that like Voxalot it's a forwarding service and follows exactly the same practice of reporting the caller's IP address in the P-src-ip header. |
|
To which Aaron's reply was:
Zitat: |
We (or more correctly I) did try and contact Betamax, there is a whole separate thread detailing the efforts. I even emailed Voxalot asking how they did it but there was no response from anyone.
Possibly if this was persisted with we'd get somewhere but currently there are only two of us running the sipswitch and both have day jobs. We run the sipswitch for fun and while we like helping out where we can chasing Betamax is not really in the fun category. |
|
As you can clearly see, their issue was not resolved to their satisfaction, even after they inserted the "P-src-ip" header in all their SIP packets. The above comments indicate that in order for the issue to be resolved, Betamax and PBXes will have to come to a formal agreement, and implement the required changes in the proper manner. That is exactly the reason I started the process back in the middle of November 2007.
|
|
29.02.2008 22:31 |
|
Dia
Premium Account
Registration Date: 03.03.2006
Posts: 1443
|
|
Update on the P-src-ip header |
|
As of today, the P-src-ip header is present across all of the PBXes servers, for every trunk irrespective of provider.
So whatever PBXes could do to indicate the unique IP of a SIP User Agent to any trunk used for an outgoing call, including all of Betamax's SIP Proxies, has been implemented across all the servers.
As a result of this change, it is now completely up to Betamax to revise their FUP calculation, not to include the peer's IP as well as the P-src-ip header in it. PBXes is looking for an exception from Betamax similar to Voxalot's, for which the FUP calculation is solely based on the P-src-ip header.
This information, was also posted in the relevant Betamax thread, in which everyone who is affected by the FUP usage should post a message, if we want the FUP calculation to change vis-a-vis the PBXes servers.
|
|
19.03.2008 06:16 |
|
i-p
Super Moderator
Registration Date: 14.01.2006
Posts: 4775
|
|
|
03.04.2008 00:46 |
|
|
|
|
|
|
|