I'm not receiving incoming calls. Outgoing seems ok. I don't see anything in the console except for this, which might not be related.
BindingExpired 21:03:36:866 sip1(1952): Expired binding deleted for xxx
Search found 26 matches
- Mon Apr 24, 2023 9:14 pm
- Forum: Report a bug
- Topic: No incoming calls
- Replies: 0
- Views: 87813
- Tue Oct 26, 2021 6:10 pm
- Forum: Report a bug
- Topic: TLS issue?
- Replies: 4
- Views: 44162
Re: TLS issue?
Thanks Aaron. It's working again.
- Mon Oct 25, 2021 2:40 pm
- Forum: Report a bug
- Topic: TLS issue?
- Replies: 4
- Views: 44162
TLS issue?
My Obi uses TLS, but I'm having an issue: Register Failed: No Response From Server (server=67.222.131.147:9712; retry in 3s) I couldn't seem to register from my Groundwire app either, however, I switched to UDP and that seemed to work fine. Switching the Obi to UDP also works. Is there a problem wit...
- Wed Nov 16, 2016 4:50 pm
- Forum: Technical Support
- Topic: Notification of registration failure
- Replies: 1
- Views: 1886
Notification of registration failure
Is there a way to send a notification (email, Google Voice SMS) if a provider (or possibly a specific SIP accounts) registration fails for a certain amount of time? Could this be done using the dialplan?
- Mon Oct 31, 2016 2:17 pm
- Forum: Technical Support
- Topic: Google voice call back and incoming calls
- Replies: 8
- Views: 4842
Re: Google voice call back and incoming calls
That was it. I changed it to "*" when I was trying to debug this issue. Changing it back fixed the problem. Thanks Aaron.
- Sun Oct 30, 2016 9:48 pm
- Forum: Technical Support
- Topic: Google voice call back and incoming calls
- Replies: 8
- Views: 4842
Re: Google voice call back and incoming calls
Thanks! Adding the "+" definitely worked for the call back. But, now I'm having a new problem. Instead of recognizing the call back, it seems Sipsorcery is processing the call as a normal incoming call. In the log below, you can see a dial attempt to the device I'm using to call. In my dial plan, I ...
- Wed Oct 26, 2016 3:08 pm
- Forum: Technical Support
- Topic: Google voice call back and incoming calls
- Replies: 8
- Views: 4842
Re: Google voice call back and incoming calls
Yes, incoming calls do work fine and get routed to the desired SIP account: DialPlan 15:03:47:115 sip1(10028): Using dialplan default for In call to sip:trunk.ssuser@sip.sipsorcery.com. NewCall 15:03:47:130 sip1(10028): Executing script dial plan for call to trunk.ssuser. DialPlan 15:03:47:271 sip1(...
- Mon Oct 24, 2016 9:19 pm
- Forum: Technical Support
- Topic: Google voice call back and incoming calls
- Replies: 8
- Views: 4842
Re: Google voice call back and incoming calls
For some reason, the call back is not being recognized: DialPlan 21:10:43:892 sip1(8364): New call from tcp:24.114.91.40:44627 successfully authenticated by digest. DialPlan 21:10:43:939 sip1(8364): Using dialplan Main for Out call to sip:6317918378@sipsorcery.com. NewCall 21:10:43:970 sip1(8364): E...
- Fri Oct 21, 2016 2:38 pm
- Forum: Technical Support
- Topic: Google voice call back and incoming calls
- Replies: 8
- Views: 4842
Google voice call back and incoming calls
If I use a DID pointing to Sipsorcery for the GV call back number, can I still use the same DID for regular incoming calls? That is, will the dialplan be ignored for GV call backs, but used normally at other times? I don't think there are any more free DID options that can be used with GV so I want ...
- Tue Mar 24, 2015 2:06 pm
- Forum: Technical Support
- Topic: In dial plan forwarding causing infinite loop
- Replies: 3
- Views: 2019
Re: In dial plan forwarding causing infinite loop
Acrobits replied that a bug was found in Groundwire which causes the 410 Gone response with some servers. They are sending me a beta version with a fix so hopefully that will resolve it.