I agree this transition was badly executed. All my incoming and outgoing calls are cut off without any warning. Aaron should have given us at least a week's notice to modify our providers and dialplans or upgrade.
How do you pick which provider and dialplan as non-read-only?
Search found 10 matches
- Thu Aug 04, 2011 4:09 am
- Forum: News
- Topic: Call rejected for read only dialplan main. Upgrade to a Prem
- Replies: 9
- Views: 15226
- Sun Jun 26, 2011 7:19 am
- Forum: Report a bug
- Topic: SIP Provider Realm Parameter
- Replies: 3
- Views: 1214
Re: SIP Provider Realm Parameter
Thank you for the information! What I am trying to do is to send a different Caller ID to Unlimitel by changing the From header. Suppose my Unlimitel username is 123 and I would like to send 456 as the caller ID. I tried this using a Linksys PAP2 (without SIP Sorcery in between) successfully by chan...
- Wed Jun 08, 2011 3:35 am
- Forum: Report a bug
- Topic: SIP Provider Realm Parameter
- Replies: 3
- Views: 1214
SIP Provider Realm Parameter
For one of my SIP providers, the server address is "sip.unlimitel.ca" During a digest proxy-authentication, this is sent: Proxy-Authorization: Digest username="1234567890",realm="unlimitel.ca",nonce="0a13e289",uri="sip:1234567890@sip.unlimitel.ca",response="06d7d9c03833081f5d488a2472dc84ca",algorith...
- Fri Oct 01, 2010 6:04 am
- Forum: Report a bug
- Topic: sys.Dial( "local" ) does not ring all accounts
- Replies: 3
- Views: 1271
Re: sys.Dial( "local" ) does not ring all accounts
I just experimented a bit more and it seems like the sys.Dial() command throws the "No SIP clients registered" error log message whenever there are no SIP clients registered to the "owner" SIP Sorcery account. Once a SIP client has registered to the "owner" SIP Sorcery account, the sys.Dial() comman...
- Fri Oct 01, 2010 5:46 am
- Forum: Report a bug
- Topic: sys.Dial( "local" ) does not ring all accounts
- Replies: 3
- Views: 1271
Re: sys.Dial( "local" ) does not ring all accounts
Thank you for the quick reply! Sorry, I guess my memory is going. I replaced sys.Dial("local") with sys.Dial(" sipusername @local") but still receive the "No SIP clients registered" error log message... The sipusername account is correctly registered to SIP Sorcery and shows up under the SIP Binding...
- Fri Oct 01, 2010 4:07 am
- Forum: Report a bug
- Topic: sys.Dial( "local" ) does not ring all accounts
- Replies: 3
- Views: 1271
sys.Dial( "local" ) does not ring all accounts
I remembered a time when sys.Dial( "local" ) would ring all of the SIP clients registered to the SIP Sorcery account simultaneously. Now, however, it only rings the clients registered to "main" (owner) SIP Sorcery account. When there are no clients registered to the "main" SIP Sorcery account, and o...
- Thu Jan 14, 2010 8:24 am
- Forum: Technical Support
- Topic: Dialling another SIP Sorcery URI now fails
- Replies: 6
- Views: 1645
- Mon Jan 11, 2010 3:57 am
- Forum: Technical Support
- Topic: Dialling another SIP Sorcery URI now fails
- Replies: 6
- Views: 1645
Attached is the event * trace. I have replaced my IP address and the called user. DialPlan 03:42:20:927: New call from udp:MY_IP:5060 successfully authenticated by digest. DialPlan 03:42:20:958: Using dialplan out for Out call to sip:CALLEE@sipsorcery.com. NewCall 03:42:20:974: Executing script dial...
- Mon Jan 11, 2010 3:01 am
- Forum: Technical Support
- Topic: Dialling another SIP Sorcery URI now fails
- Replies: 6
- Views: 1645
Dialling another SIP Sorcery URI now fails
I believe this change happened yesterday. I used to be able to dial another SIP Sorcery URI using sys.Dial("callee@sipsorcery.com"). This would trigger the IN dialplan of callee 's SIP Sorcery account. Starting yesterday, however, the same command would trigger the OUT dialplan of the caller 's SIP ...
- Wed Oct 07, 2009 6:56 pm
- Forum: Technical Support
- Topic: no outgoing voice?
- Replies: 78
- Views: 26194
I am experiencing the same problem with inbound calls to a PAP2 and SPA-2102 registered to sipsorcery.com as of yesterday. However, my calls consistently disconnect at 5 to 6 seconds. Those with disconnection times of around 30 seconds may have set a longer disconnection timeout for their SIP adapte...