 Thread: RE: I accidentally subscribed twice |
|
|
Hello
I recently purchased a premium subscription and accidentally subscribed twice when paying with PayPal (the default option was paying from Bank Account but I wanted to pay with a credit card. I immediately pressed stop, but apparently the first transaction did go through).
I’d like to cancel the Bank Account subscription and get a refund for the 10.95 EURO since I will have the other subscription active, could someone from PBXes help me with that please?
Thank you very much.
Claudiu
|
|
| Thread: RE: CallThru Dial Tone doesn't go away when dialling |
|
|
I am sending them directly from the phone dial-pad, I don't use any application for dialing. And about the codec I really don't know, I guess I use the codec any standard phone would use; in my case I mostly dial from Nokia cell phones.
_____________________________
I still can't see Bobmats replies in this thread. The only thing I can see is there are 4 replies so far, but I can only see mine and Bazmercer's. What is going on with the forum ? Can somebody else do a copy & paste with his replies please?
UPDATE
I have modified the DTMF to rfc2833 and personally I don'y't have any problems on my on phone anymore but it just doesn't work on my sister phone. Using my Nokia E51 it works perfectly now but using my sister's Nokia 2730 classic the dial tone doesn't go away, it doesn't even register a single tone. What is weird is if I call the voicemail or any other service that requires DTMF it works on the Nokia 2730 so the phone is sending the tones, it's just for some reason PBXes is not picking them up.
I am left scratching my head not knowing what to do next and WHY only the Nokia 2730 is left having problems?
Any ideas or suggestions please?
|
|
| Thread: RE: CallThru Dial Tone doesn't go away when dialling |
|
|
Sorry for the empty post, but I received an email with a reply alert from Bobmats but for some reason I can't see his post, only my first.
EDIT: I still can't see Bobmats reply even after this update. Very strange.
|
|
| Thread: RE: CallThru Dial Tone doesn't go away when dialling |
|
|
Hello.
Recently (about 1 to 2 months ago) I started to have problems with the CallThru dial tone: I start punching in the numbers but the dial tone doesn't go away. Sometimes but not always I can bypass this by keeping the first digit pressed for 2 seconds; only then the dial tone goes away and I can dial the rest of the number normally.
I have two providers that are configured for CallThru: a Voxalot trunk that is accessed via SIP Broker numbers and a Localphone DID that is configured for CallThru. Both trunks experience this problem. I have been using CallTrhu with Voxalot for a year now and the Localphone DID for more than 6 months and never had any issues so far so I am thinking something changed (or a BUG popped up) in PBXes setup. Also it is worth mentioning that the problems appear randomly: sometimes everything works fine sometimes it just doesn't but I haven't found any pattern how and why this is happening.
Could someone investigate this issue and maybe find a solution please?
Thank you.
Claudiu
EDIT:
Any news or info, I would really like some feedback in troubleshooting this issue? For instance this morning I couldn't get passed the Dial Tone when dialing from a Nokia 2730 mobile phone but when I tried with a Nokia E51 mobile phone and it worked from the first try. Could it be a phone issue or was it just coincidence?
|
|
| Thread: RE: DID numbers for SUDAN |
|
|
Thanks for your replies. Yeah, it seems I'm looking for something that doesn't exist and I don't have anyone in the country who can help me.
Claudiu.
|
|
| Thread: RE: DID numbers for SUDAN |
|
|
Hello everyone.
Normally I wouldn't open a topic about this (I hope it is permitted by PBXes) but I need all the help & info I can get. I need a DID number for Sudan, but I can't find anything available on the internet. I spent an hour googling for it and I still have nothing. Does anyone have any idea where I can find one?
Thank you.
Claudiu
|
|
| Thread: RE: Account disabled after I have paid > had to pay twice |
|
|
Thank you i-p-tel. So from now on if I go over 2000 minutes, just pay a onetime (monthly) Premium subscription and cancel after that. That should be all good from now on right?
And I am still on the Premium subscription, can I cancel it safely and go back to SoHo.
Claudiu
|
|
| Thread: RE: Account disabled after I have paid > had to pay twice |
|
|
I've been using PBXes and had a SOHO subscription for almost a year now. So far I've never been over 2000 minutes /month, but in June I used 2360 minutes. After that I received an email about going over my quota and having to upgrade which I did.
- On June 30 I paid a monthly fee for a Premium Account that would be good for up to 5000 minutes. I used PayPal and 10.95 Euro were taken out of my Visa. Technically this should cover the overage minutes for the month of June and should be OK for up to 5000 minutes.
- On July 5 I cancelled the subscription for the Premium Account because I don’t need it every month, a SoHo monthly subscription is enough for me; going over 2000 minutes on June was an isolated incident that I paid for on June 30.
- Today on July 11 my account was disabled because “Exceeding minutes quota requires upgrade to Premium or PRO.” But why, I already paid for that on June 30?
There are a few unsolved issues right now:
1. My account was WRONGLY disabled
2. I couldn’t post on the forums and ask for support with the account disabled so I had to pay again 10.95 Euro to have it reactivated
3. I would like to get the money back for the second payment since I already paid once
4. I would like to cancel the Premium subscription and remain on a monthly SoHo subscription without having my account disabled again on the next month
I assume my account was disabled automatically by your system but there must be a BUG somewhere so you might want to look it up.
Thank you.
Claudiu
|
|
| Thread: RE: Different Outbound routes according each Inbound Route |
|
|
The main reason is I want to use different CID according to where the call originates. Right now only one CID is passed when anyone calls via CallThru and sometimes is confusing when people are calling back. I can use different legitimate CID (for each CID I have an outbound trunk) but somehow I have to switch between them.
So the logic was:
Cell phone 1 calls> Trunk / DID 1 > CallThru > dial any number via Outbound route 1 > Send CID XXX
Cell phone 2 calls> Trunk / DID 2 > CallThru > dial any number via Outbound route 2 > Send CID YYY
Also I want to use a different set of outbound providers according to who is calling via CallThru but that is secondary.
|
|
| Thread: RE: Different Outbound routes according each Inbound Route |
|
|
This will only complicate things because the rest of my family uses CallThru and it would be chaos if I tell them to add 20 or 21; they are not that tech friendly, I have to make everything as simple as possible. I thought there would be a simple setting somewhere that would solve my problem.
I can't believe that nobody at PBXes thought of this before, I assume we are not the only ones that would need it.
|
|
| Thread: RE: Different Outbound routes according each Inbound Route |
|
|
Hello.
My problem is apparently simple, I know I am probably missing something, but I don't know how to do it.
I have two different SIP trunks (both from Localphone) with 2 corresponding DIDs. The trunks are configured for CallThru when I call from two different cell phones. Each DID has its corresponding cell phone for CallThru.
I also have two different Outbound routes (Trunks), each is prepared for its corresponding inbound SIP trunk. Outbound trunks are different than Inbound trunks. The problem is I don’t know how to setup an Outbound route according to what trunk is accessed via CallThru. Basically what I need to do is this:
Cell phone 1 calls> Trunk / DID 1 > CallThru > dial any number via Outbound route 1
Cell phone 2 calls> Trunk / DID 2 > CallThru > dial any number via Outbound route 2
I want the selection of the Outbound route to be done not according to number that is called but according to incoming trunk.
Right now only the first selected Outbound route is active and I can’t see any options for selecting incoming trunks, only extensions or numbers.
So how can I do it?
|
|
| Thread: RE: SIPDISCOUNT Fair Use Policy |
|
|
Voxalot is FUP free only for US and AU servers, the EU server seems to have FUP issues with Betamax. Registering Voxalot at PBXes works for calls to North America and you won’t get FUP, but it doesn’t work for other destinations; I am charged for free calls to some European land lines.
|
|
| Thread: RE: Problems with CallThru and Localphone DIDs |
|
|
| Zitat: |
Originally posted by Diafora
Even after having read your lengthy post, I am still not sure where the issue lies. Just to clear something up, what city are your Canadian LocalPhone DIDs from? |
|
Halifax, 902 phone area code. Actually the area code is the same for the whole Nova Scotia province.
| Zitat: |
| I am not sure if I understood correctly what you wrote, but are the LocalPhone SIP IDs provisioned as trunks directly on your PBXes account, or via Voxalot? |
|
Yes, my LocalPhone SIP Ids are trunks in my PBXes account. I mentioned Voxalot because I have some overseas DIDs registered there that use the same outbound termination providers as PBXes, but LocalPhone is PBXes only.
| Zitat: |
| Can you test with X-Lite setup as a PBXes extension, to eliminate completely any Voxalot intermediate step? |
|
OK, I will test with X-Lite as an extension and I will also test with LocalPhone directly registered in X-Lite. But it is difficult to catch the right moment when the numbers present only busy tones...
| Zitat: |
| Regarding Les.Net is not the only game in town, but his DIDs definitely work properly with PBXes. Lately though, he has introduced policies (technical & business related) which don't sit well with a lot of his faithful users. |
|
Les pricing is bad. They charge 8.88 $ / month for an unmetered DID, Localphone charges only 3 $. Other options are Voip.ms 5.95 $ or DIDWW.com with 5 $ / month. I will try and resolve this with Localphone, they've been good with support in the past, maybe they have other solutions.
Diafora please see my previous post regarding the "This call cannot be completed as dialled. Please try your call again later"; is it coming from PBXes?
|
|
| Thread: RE: Problems with CallThru and Localphone DIDs |
|
|
@bobmats
Yes, Localphone is registered as a trunk (actually 2 trunks as I have two DIDs with them) and for each trunk I have two inbound routes: one is for CallThru and the other is for forwarding to a classic extension (mobile phone).
The idea of all this is because from my mobile phone I have unlimited local calling with one local number and this number is a Localphone DID. All my mobile phone calls go thru this DID so that’s why I’m concerned with the DID “reliability”. Everyone that calls me on my mobile phone actually call the DID number, not my real phone number...and they report A LOT of busy tones and it is not good (or it rings, but my mobile phone doesn't ring). Plus I also get a lot of busy tones when I call the DID for CallThru.
@Diafora
Voxalot doesn’t have PSTN termination; I use a Betamax clone for termination to Canadian numbers. I have a few overseas DIDs registered at Voxalot (before I started using PBXes) that are forwarded to Canadian PSTN numbers via Betamax and everything is working perfectly so I have no reason to suspect Betamax. I know Betamax is not everyone’s favourite VoIP company, but it is OK for my needs.
Anyway, I have done what you suggested in order to better troubleshoot the problem, I pointed one DID to a Sip URI, not to the classic extension. The SIP URI was my Voxalot account and I had X-Lite opened and pointing to Voxalot. So in this case Voxalot was out of the equation as an outbound route.
It wasn’t easy to catch the right moment, but I managed to recreate all symptoms that happen with a classic extension: busy tones nonstop for 5 minutes, X-Lite / Voxalot didn’t ring. So I think it is clear that the call never even made to PBXes. The busy tones were instantaneous. CallThru didn’t work either (for the other inbound route), again I was presented with a busy tone. After 5 minutes things magically got back to normal, X-Lite / Voxalot rang so the calls were getting to PBXes.
So, as I suspected, the problem is not PBXes or Voxalot as an outbound route, it is LocalPhone or GT GROUP TELECOM who “owns” the DIDs sold by Localphone.
So any ideas on what I should do next ?
P.S. Diafora can you please change my user name to Claudiu? I don't why I ended up with this nick name. Thank you.
EDIT: I forgot to mention in my first post, but with CallThru I also get this message: “This call cannot be completed as dialled. Please try your call again later”. Is this message coming from PBXes server? It happens only with CallThru (via DID or SIP Broker numbers) and couldn’t figure out what causes it. Sometimes I get it when dialling extensions (100, 200), sometimes when dialling out via an outbound route. I have to keep trying a few times and eventually the call gets through, but not always. The only thing I could notice is that it happens when another line is in use in my PBXes account, but this is not the only case, sometimes it just happens without anyone using any other trunks / accounts.
|
|
| Thread: RE: Problems with CallThru and Localphone DIDs |
|
|
I’m not sure where the problems come from either, that’s why it is tricky to troublshot.
My DIDs are setup for either CallThru or forward to a mobile phone at the same time; it all depends on the incoming Caller ID at that DID.
In my Localphone account I have only 1 Active Device (PBXes) per each SIP ID (I have a SIP ID and password for each DID).
http://img180.imageshack.us/img180/9831/capturehj.jpg
Apparently everything is working OK, but it is not. This morning for example, I called one DID and instantly I got a busy tone. It came so fast that there is a possibility that the called never even made thru the local telephone exchange center. The second try everything was ok, the DID rang and it was forwarded successfully. Usually when a call will be successful it will take a while to connect, if not the busy tone is instant a milisecond after I press the call button.
I strongly suspect the company that owns the DID numbers ( GT GROUP TELECOM ) might have some issues with my assigned DIDs, but I don’t know how to check. And unfortunately Localphone can provide local DID numbers only from GT Group Telecom.
@bobmats
My only outbound route is Voxalot. It is registered as a trunk and all outbound calls are made using the dial plans configured in my Voxalot account. I have no reason to suspect the outbound route; everything has been working perfectly for over 6 months with CallThru if I call from regular phones via SIP Broker numbers. The problems arise only with DID Callthru.
|
|
| Thread: RE: Problems with CallThru and Localphone DIDs |
|
|
Hello everyone.
I have a SOHO account and it has a few “Bugs” that I can’t get rid of.
I have two Canadian DID numbers registered as trunks. The numbers were bought from Localphone.com and the Localphone accounts are registered only at PBXes and nowhere else.
Each DID is configured for two inboud routes:
1. If I call from my mobile phones then I get => CallThru
2. If everyone else calls the DID the call is forwarded to a mobile phone number (that’s is configured as a classic extension)
Basically the DID acts as a gateway depending on Caller ID. I have two separate DIDs that are linked to two separate mobile phone numbers, each mobile phone is tied to an individual DID.
The problem is I have a lot of problems with these DIDs and the routing and I can’t figure out the cause; is it PBXes, is it Localphone? These are the symptoms:
- A LOT of times when people call a DID they instantly get a quick busy tone, but no one is using the DID. Usually the call goes thru with a second or even a third call attempt . In some occasions the busy tone persists until a “reset” the DID by doing a CallThru.
- Another symptom is someone is calling the DID, it rings, but the call is not routed to my mobile phone (the extension). It rings “somewhere” at PBXes probably, but it is not routed accordingly.
- When attempting a CallThru I get a busy tone; sometimes I have to keep trying for 10 minutes until I can get a dial tone. Occasionally I get the message " All circuits are busy" (I don't know if it's from PBXes or another place). I couldn’t find a pattern why this is happening, sometimes everything works fine, and sometimes it just doesn’t work.
- Again when attempting a CallThru it rings, but it keeps ringing and nothing happens, the CallThru is not triggered, I don’t get a dial tone.
I don’t know why all this is happening and I really don’t know where to start to troubleshoot the problem. All I know is that I also use CallThru from regular phones via SIP Broker numbers and it works EVERY time I call. This leads me to believe that all these problems that I have are somehow related with Localphne trunks registered at PBXes....something is not working right. I would change the DID providers but it doesn’t make sense to pay setup fees all over again to discover that it still doesn’t work.
So anybody at PBXes, can you please check the Localphone <> PBXes "connection" and see if you can pinpoint where things are not working? Thank you !
Claudiu
|
|
|
