When people call me through a sipgate.co.uk trunk they don't get a ringtone and I see a congestion message in the 'Call Monitor'.
Why is that? Is there something I can do to resolve this?
Apparently, there is a problem with Sipgate and Asterisk when the
"Allow Anonymous inbound SIP calls" is set to "no".
This happens when the sipgate trunk is called from another Cisco PBX which does not send a caller-id. The inbound route works fine from any other phone.
Is it possible to fix this? It is vital for me and very annoying.
[EDIT] Diafora - Sipgate says:
Enclosed the necessary settings to configure to Asterisk for sipgate. (Very important to have the SIP ID at the end of the register command)
So can you add my SIP ID in the register command? Instead of
register=xxxxxxx:xxxxxxx@sipgate.co.uk/sipgate
can you change to
register=xxxxxxx:xxxxxxx@sipgate.co.uk/SIP ID?
Many thanks,
Dimitris.
This post has been edited 1 time(s), it was last edited by drm on 05.11.2009 at 12:35.
the problem remains.
I have named the trunk the same as the DID number sipgate has provided, but still I get a Congestion message if dialling without caller id.
If the Trunk name is the same as your SIPGate SIP-ID, then having the proper Register String in your Trunk configuration, is not the likely cause for the issue at hand. You can inquire with SIPGate whether they currently see your SIP-ID number at the end of the Register string.
Based on your report, the Congestion message shows up, when the caller dialing your SIPGate DID originates the call specifically from a Cisco PBX. Not a regular PSTN line, or a mobile phone.
You can also ask them to set up a trace, and provide you with the SIP message their SIP Proxy gets, when a call originating from the Cisco PBX fails to be delivered to PBXes.
Ευχαριστώ Diafora,
but the problem seems to be specific to PBXes.
The problem dissolves when I use my phone to register directly with sipgate.
I have tried everything, setting up incoming routes, privacy manager etc but nothing works. Sipgate forwards the call to PBXes which issues a congestion message and the calling user is blocked.
Looking into your system log revealed that your endpoint drmitsos-200 answers "406 Not acceptable" for these calls. I suggest that you check your endpoint's settings and logs.