Search found 4651 matches
- Mon Jan 13, 2020 8:51 am
- Forum: Technical Support
- Topic: Multiple dialplans
- Replies: 8
- Views: 9981
Re: Multiple dialplans
From what I can tell you are already using the number field to hold multiple values delimited by the ';' character. You could do the same thing to pass in a dialplan name variable and then use an if/else to choose different dialplan logic. Perhaps something like: sys.Log("webcallback dialplan starti...
- Fri Jan 10, 2020 9:30 am
- Forum: Technical Support
- Topic: Multiple dialplans
- Replies: 8
- Views: 9981
Re: Multiple dialplans
Which of the web callback mechanisms are you using? If it the call manager service and you are initiating calls using something like the URL below then it's a little bit tricky because the dialplan must be name webcallback and you can't have different ones for each company. How do you differentiate ...
- Thu Jan 09, 2020 8:41 am
- Forum: Technical Support
- Topic: currently unavailable, please try again later
- Replies: 3
- Views: 4975
Re: currently unavailable, please try again later
Are those times specified as AEDT? IF so there is only one call within that timeframe that the sipsorcery server returned a "480 Temporarily Unavailable" response for and that wasn't on your account.
I can check some other logs if you send me your username and the timezone to aaron@sipsorcery.com.
I can check some other logs if you send me your username and the timezone to aaron@sipsorcery.com.
- Wed Jan 08, 2020 8:17 am
- Forum: Technical Support
- Topic: currently unavailable, please try again later
- Replies: 3
- Views: 4975
Re: currently unavailable, please try again later
The most likely cause is the sipsorcery server not having any registrations for your SIP devices. The reason for that could be something like a network problem but I'm only guessing. If you check the Call Detail Records for the period in question on your sipsorcery account the failure reason may pro...
- Tue Jan 07, 2020 9:40 am
- Forum: Report a bug
- Topic: Cross-Origin Request Blocked
- Replies: 6
- Views: 12917
Re: Cross-Origin Request Blocked
Webcallback's are working ok for me so there is no issue with the ports.
If you open the `Console` with a filter of `event 53` in another browser tab and then try your web callback you should get some useful log messages.
If you open the `Console` with a filter of `event 53` in another browser tab and then try your web callback you should get some useful log messages.
- Thu Jan 02, 2020 10:17 am
- Forum: Dial Plan Wizards (Telis & Simple)
- Topic: Selecting chars from ${EXTEN} variable in Simple Wizard
- Replies: 10
- Views: 24374
- Thu Dec 12, 2019 8:27 am
- Forum: Report a bug
- Topic: Video - Memory Leak?
- Replies: 2
- Views: 9147
Re: Video - Memory Leak?
Hi Brian, The GitHub Issues is a better place for this discussion. It's more actively monitored than this forum. Video is broken in the current softphone sample. I aim to get back working on it once I've cleared the current list of outstanding requests. There's also been a refactor of the softphone ...
- Sat Oct 19, 2019 7:16 pm
- Forum: Technical Support
- Topic: FreePhoneLine problems
- Replies: 6
- Views: 8499
Re: FreePhoneLine problems
I overlooked the fact that the registration agent and the proxy do their DNS lookups separately. The registration agent has also now been restarted to get the new DNS settings and is back resolving correctly.
- Sat Oct 19, 2019 8:51 am
- Forum: Report a bug
- Topic: [SOLVED] DNS Issues ?
- Replies: 1
- Views: 9483
Re: DNS Issues ?
It should be fine now. A user emailed me about the same problem last night. The SIP Proxy had switched to the secondary DNS server due to the time out on a different lookup. The problem was the secondary DNS server is flakey and was regularly failing to resolve good domains. I've now replaced the se...
- Sat Oct 19, 2019 8:50 am
- Forum: Technical Support
- Topic: FreePhoneLine problems
- Replies: 6
- Views: 8499
Re: FreePhoneLine problems
It should be fine now. A user emailed me about the same problem last night. The SIP Proxy had switched to the secondary DNS server due to the time out on a different lookup. The problem was the secondary DNS server is flakey and was regularly failing to resolve good domains. I've now replaced the se...