 Thread: RE: budgetphone.nl - trunks not connecting to extensions |
|
|
Sorry, I wasn't clear. I am using voip.co.uk as the inbound trunk. With a different SIP account with voip.co.uk which is directly registered, inbound calls work fine.
Your point was a good one: "did I get this before?"
I checked my logs from my last call through www5 and there it was clear as day. So this wasn't the problem.
In the meantime, I suspect some intervention from our good friend diafora (?), as inbound calls now work again.
I did also try my budgetphone.nl trunk, but this also works now, and I have no proof that it didn't work today (no inbound calls)
|
|
| Thread: RE: budgetphone.nl - trunks not connecting to extensions |
|
|
I appear to have a similar issue, although I fork calls to the extension concerned which do get through. Looking through my logs I can see the following, although I don't know if it is relevant:
| Zitat: |
| VERBOSE[14365] chan_sip.c: SIP response 401 to standard invite |
|
Call through a different provider make it through OK.
I have tried doing a dummy change and clicking on the red bar as I know this can sometimes help.
Any ideas, as I have had no calls today (last registered inbound call on my Fritz!Box is yesterday at 10.56 CET
HELP!!!!!
|
|
| Thread: RE: forward to digital receptionist on no reply |
|
|
Thanks for your reply.
Whilst I can see your point that a hunt may be technically simpler to set up, what I want is actually a simple setup from the user's point of view.
The caller may or may not have come through an IVR to get to that extension (depending on the number called), but if nobody answers, the extension they may want to try next will depend on the caller's personal preference. So a "Sorry there is no reply" message should play with the option to leave a voicemail (one of my extensions) or go back to the main menu where other extensions can be selected. These are the only two menus that a caller on these trunks should ever hear.
It is not clear whether your advice is based on technical complexities or "usability" issues. I am happy that the scenario I want to see is user-friendly, but I am unsure from your message what the technical complications may be. Could you elaborate? Why does looping back to a main menu cause issues?
Thanks for your assistance.
|
|
| Thread: RE: forward to digital receptionist on no reply |
|
|
An inbound call comes in on one of my Trunks and lands on an Inbound Route, which directs it to an Extension
Then if there is No Answer, I wish to send the inbound caller to an IVR (DR) menu again.
|
|
| Thread: RE: forward to digital receptionist on no reply |
|
|
I want to set an extension, if no answer, to go back to a digital receptionist menu.
I have created an inbound routing of the form accountname-foo which points to the digital receptionist menu I want to use.
I have put SIP/accountname-foo in the if no answer box, also tried SIP/accountname-foo@pbxes.org.
I also tried doing the same in all calls box instead.
However it goes to a different extension instead, which I would expect when pbxes gives a busy here response
Is there something simple I am missing?
|
|
| Thread: RE: Cancelation of account by mistake |
|
|
Glad you are sorted, but would still urge pbxes to re-consider the policy - it is often the little things that will make people vote with their feet.
|
|
| Thread: RE: Cancelation of account by mistake |
|
|
I agree! I have just got caught in the same situation!
Fair enough, I didn't need to renew again (my cancelled subscription had about a month left) but your customers will vote with their feet if you don't pay attention. I renewed assuming you would play fair...
I don't think anyone is asking for a refund, but adding the time that was cancelled to the new subscription is surely an easy ask???
|
|
| Thread: RE: SIP signalling issues - call ringing |
|
|
Well, after several days of dealing with this problem, I can say the following:
The fault is intermittent. I get no problems when I try it myself (using a mobile) but my callers are often complaining of no ring tone, and the ata does not generate a ringing on the telephone line.
However I configure ring groups, I do not have a reduction in the number of problems, even when only one SIP extension is specified in the ring group.
Routing the calls directly to my ATA from proxy.voip.co.uk does not generate issues.
Issues seem to be reduced when forking from proxy.voip.co.uk to two SIP registrations (one of them my ATA, the other pbxes.com).
In short, PBXes is the only common link at this stage although I have only now tried configuring inbound routing to an extension instead of a ring group.
If you want to take a look at the system logs for a problem call, try looking at my logs from Sep 16 17:31:05. This was a call which the caller complained that they did not receive a ringing tone. Unfortunately, my ATA does not provide detailed logging in it's web interface so I can't check the other side of the communication.
Regarding your comment on no ringback for classical extensions, do you mean the caller will never hear a ringing tone?
|
|
| Thread: RE: SIP signalling issues - call ringing |
|
|
I have a very weird problem, which is that in certain configurations for inbound calls, the calling party does not receive a ringing tone, nor does the phone attached to my ATA ring. However the phone on my SIP extension displays the number of the person and it is possible to answer the phone even though it is not ringing, My setup is as follows:
Provider (voip.co.uk)
--> pbxes trunk
--> ring group (1 x sip extension, 2 x classic extensions - mobile numbers)
--> ATA (Fritz!Box 7270 functioning as router)
--> DECT phone
I had this problem previously with a different provider, and I solved it by changing the order of the extensions in the ring group.
It started doing the same with voip.co.uk when I removed the second routing to a softphone within voip.co.uk configuration, and used pbxes.com to do the routing instead.
It appears that there is some sort of conflict somewhere, but I can't work it out at all! All hep gratefully appreciated!
|
|
|
