Voxalot / SIP Broker Support Forums

Voxalot / SIP Broker Support Forums (https://forum.sipbroker.com/index.php)
-   Voxalot Support (https://forum.sipbroker.com/forumdisplay.php?f=4)
-   -   FUP exceeded after reconfiguration ATA (https://forum.sipbroker.com/showthread.php?t=4077)

amroe 08-16-2009 10:18 AM

I use proxy01.eu1.voxalot.com , it was the only good working with FUP matter , but its Now Bad , please Voxalot fix this problem :(

martin 08-17-2009 09:49 AM

Quote:

Originally Posted by amroe (Post 24647)
I use proxy01.eu1.voxalot.com , it was the only good working with FUP matter , but its Now Bad , please Voxalot fix this problem :(

To date we have had no response from Betamax. The fix must come from them.

g00fy 08-18-2009 09:30 AM

May be you could send them a reminder?

Corbu' 08-18-2009 09:27 PM

I fear the people at Betamax don’t even care about this issue, maybe that’s why they are so slow resolving it.

martin 08-19-2009 09:08 AM

Quote:

Originally Posted by g00fy (Post 24668)
May be you could send them a reminder?

I've already sent 2 follow up emails. Unfortunately they appear to be landing on deaf ears.

jozef 08-20-2009 08:01 AM

Hi,

Quote:

Originally Posted by Corbu' (Post 24646)
Every time I use my Nokia E51 SIP phone and call FREE destinations by connecting directly to US server, the call is free. But if I use a CallThru service from a regular phone (in association with PBXes) I get FUP exceeded....

You can try workaround PBXes --> SipSorcery --> Voxalot --> Betamax

1. Add SipSorcery in PBXes
2. Add Voxalot in SipSorcery, don't forget to set the Custom Header(s) 'P-src-ip: XX.XX.XX.XX'

I tried PBXes CallThru, it works... withoat FUP. I use us.voxalot.com
Quote:

Date Time Number called Duration Amount
2009-08-20 09:32:21 +48814705xxx 00:00:34 FREE!
2009-08-20 08:35:26 +4611393xxx 00:00:38 FREE!
2009-08-20 08:24:49 +4611393xxx 00:00:55 FREE!
Regards
Józef

boatman 08-20-2009 06:57 PM

Quote:

Originally Posted by jozef (Post 24682)
2. Add Voxalot in SipSorcery, don't forget to set the Custom Header(s) 'P-src-ip: XX.XX.XX.XX'

jozef,

How does that change the SIP/SDP packet when it arrives at Betamax? Does Betamax's billing use the IP address from that line in the SIP header, rather than using the actual source IP address of the SIP packet?

I see lots of 'P-hint: outbound' and 'P-hint: usrloc applied' in Voxalot's SIP/SDP packets. Do you think Voxalot might be able to avoid the FUP issue if they inserted 'P-src-ip: XX.XX.XX.XX' as you suggest?

jozef 08-21-2009 07:29 AM

Quote:

Originally Posted by boatman (Post 24688)
jozef,

How does that change the SIP/SDP packet when it arrives at Betamax? Does Betamax's billing use the IP address from that line in the SIP header, rather than using the actual source IP address of the SIP packet?

I see lots of 'P-hint: outbound' and 'P-hint: usrloc applied' in Voxalot's SIP/SDP packets. Do you think Voxalot might be able to avoid the FUP issue if they inserted 'P-src-ip: XX.XX.XX.XX' as you suggest?

boatman,

I don't know VoIP technology. I use it. This means, I am a user not technician. I like to create Dial Plans and do some test. VoIP is my hobby.
I register my ATA to Voxalot, so i I don't have FUP issue if proxy is on Betamax "whitelist". But when I tested Callback from MSS, I got FUP for call started from PBXes --> Voxalot --> Betamax. After workaround PBXes --> MSS --> Voxalot --> Betamax it was FREE. So i think that the "whitelist" and the IP address from the SIP header was solution.

In December 2008 I created workaround FreecoNet-->MSS-->Voxalot-->Betamax. I think this is still working for FreecoNet user without FUP if Voxalot is on Betamax "whitelist".

boatman 08-21-2009 07:57 AM

jozef,

Could you test the 'Custom Header P-src-ip:' solution with a proxy that is not on the Betamax whitelist? Reports are that proxy02.eu1.voxalot.com is not on the whitelist.

If the 'P-src-ip:' solution works for a non-whitelist proxy then Voxalot may be able to fix the whole FUP problem for everyone by inserting the 'P-src-ip:' line into their SIP packets.

jozef 08-21-2009 10:56 AM

Quote:

Originally Posted by boatman (Post 24691)
jozef,

Could you test the 'Custom Header P-src-ip:' solution with a proxy that is not on the Betamax whitelist? Reports are that proxy02.eu1.voxalot.com is not on the whitelist.

If the 'P-src-ip:' solution works for a non-whitelist proxy then Voxalot may be able to fix the whole FUP problem for everyone by inserting the 'P-src-ip:' line into their SIP packets.

Hi boatman,

DONE!!! It looks great
1st Test. Calls start from PBXes-->SS-->Voxalot-->Poivy
proxy02.eu1.voxalot.com, Custom Header(s) 'P-src-ip: XX.XX.XX.XX'

Date Time Number called Duration Amount
2009-08-21 12:38:58 +48814705xxx 00:00:27 FREE!
2009-08-21 12:32:15 +4611393xxx 00:00:34 FREE!
2009-08-21 12:29:47 +4611393xxx 00:00:39 FREE!
2009-08-21 12:24:36 +48814705xxx 00:00:25 FREE!
2009-08-21 12:19:29 +4611393xxx 00:00:34 FREE!
2009-08-21 12:17:17 +4611393xxx 00:00:32 FREE!


2nd Test. Calls start from ATA registered with Sipsorcery-->Voxalot-->Betamax
proxy02.eu1.voxalot.com, Custom Header(s) 'P-src-ip: XX.XX.XX.XX'

Date Time Number called Duration Amount
2009-08-21 16:02:01 +4989721010xxx 00:01:43 FREE!
2009-08-21 15:55:14 +48814705xxx 00:00:55 FREE!
2009-08-21 15:46:33 +4611393xxx 00:00:38 FREE!

My Betamax provider is Poivy. I have SIP Trace from SipSorcery if you need.


All times are GMT. The time now is 06:57 AM.

Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.