Defect #1705
closedCallcentric Domain seems blocked
0%
Description
I have a Callcentric DID which I am forwarding to my SIP URI with sip2sip but unfortunately the number does not get forwarded. I believe this issue is on your end because if I forward the DID to another URI (non si2sip) it works fine. I cant even call my SIP URI with Callcentric though other URI's work correctly. The error Callcentric is receiving on their end is 503 Relay Denied. Can you guys fix this issue?
Updated by Adrian Georgescu about 12 years ago
- Status changed from New to Rejected
Updated by Jany Tayeb about 11 years ago
Hi, I have the same.
From a Callcentric DID I set the SIP URI to mynumber@sip2sip.info
Yet, the message received from ip2sip network, “403 Relay denied”, indicates that you are rejecting call attempts from Callcentric.
This issue was previously rejected/closed, but as I do not understand why, can you please explain if this means you do not support incoming calls from Callcentric?
Updated by john jouhn about 11 years ago
I have a Callcentric DID which I am forwarding to my DRINK URI accompanying sip2sip however unfortunately the total does hardly essay writers have forwarded. I imagine this stem is on your closure so if I progressive the DID to different URI (stop si2sip) it processs pleasant. I slang square cry my TASTE URI accompanying Callcentric still else URI's process properly.
Updated by R Mont about 11 years ago
John
Callcentric to sip2sip with SIP URI is indeed not working.
Please wait for answer from forum owner.
(who did your english translation? SIP turns into DRINK and TASTE????)
Updated by Adrian Georgescu about 11 years ago
Can you provide a call id with a failed call?
Updated by Adrian Georgescu about 11 years ago
- Status changed from Rejected to In progress
Updated by R Mont about 11 years ago
Not really, I think with 403 relay denied it does not get into my sip2sip account.
Updated by Adrian Georgescu about 11 years ago
I need meaningful info to find the calls that fail. Something.
Updated by R Mont about 11 years ago
I put the SIP trace into Ticket 8385 at https://mdns.sipthor.net/support.phtml
Updated by Tijmen de Mes about 11 years ago
Please try again. It should work now.
Updated by R Mont about 11 years ago
In fact, it is not working always.
I received this message from Callcentric: We just tested 19....0@sip2sip.info and were unable to connect. Please have sip2sip.info allow our entire subnet as described here: http://www.callcentric.com/faq/9/254
Please let me know when you have done so, we will test again.
thanks
Updated by Tijmen de Mes about 11 years ago
We have nothing blocked from those ip ranges. Can you provide the trace for a call that is failing?
Updated by R Mont about 11 years ago
ok, i have updated Ticket 8385 with a new trace
Updated by Tijmen de Mes about 11 years ago
Please try again. I removed some bogus domain from our proxy which caused the 407.
Updated by R Mont about 11 years ago
It seems to be ok, Callcentric guys have not come back to me. Thanks
Updated by Adrian Georgescu about 11 years ago
- Status changed from In progress to Closed