r422 SIPgate incoming calls no longer work

[simondale]

Hi,

All of my incoming calls have stopped with the latest snapshot. My VoIPtalk.org account still works fine. I have tried changing the NAT settings for my SIPgate provider but I still get the problem.  The log shows this:

-- Executing [3502025@.co.uk-incoming:1] Goto("SIP/1456206-08514000", "SIPGATE-incoming|s|1") in new stack
-- Goto (SIPGATE-incoming,s,1)
pbx.c:2470 in __ast_pbx_run: Channel 'SIP/1456206-08514000' sent into invalid extension 's' in context 'SIPGATE-incoming', but no invalid handler

Do I have something setup wrong?

Thanks a lot

Simon

[simondale]

Just a quick update, I have now tried reverting to pb13 and my incoming calls work fine again.

Thanks

Simon

[Michael]

Do you have multiple accounts at sipgate? Do you have multiple incoming extensions mapped for any of those accounts? If so, try only mapping a single incoming extension and see if your calls return.

The new changes to allow multiple accounts from the same provider aren't intelligent enough to also handle multiple extensions per account under the assumption that that is the reason you have multiple accounts.

[simondale]

Hi Michael,

Yes that sounds like it then.  I have 3 providers set up from SIPgate and they all go to a call group called "All phones" which does what you would expect.

So can I only have one extension per provider?  If thats the case it won't really work for me, it also makes the incoming Caller ID a bit pointless doesn't it?  If I've got to have 3 phones on my desk I may as well just put labels on them! Hehe!

I'll test it with one extension per provider tomorrow to confirm that that was the problem.

Is there any prospect of this being changed in future releases? 

Thanks

Simon

[Michael]

I don't think I was being very clear. What's currently not possible is to have multiple incoming routings per account with multiple accounts on a single host. What you're describing (one incoming route per account with multiple accounts on a single host) should work and will allow you to set a per account incoming caller id override.

[simondale]

Hi Michael,

I've tried setting my 3 different SIPgate "providers" to each go to one phone (extension 1).

This sitll gives me the same problems.  No incoming calls on any of the SIPgate accounts.

I have also tried having an extension each - Sipgate 1 goes to extension 1, sipgate 2 goes to extension 123, sipgate 3 goes to extension 124, etc.  The same problem occurs.

I've reveted back to pb13 for now.

Thanks

Simon

[Michael]

Are those incoming extensions specified with a pattern or number? They should be blank for the current system to work. If they are blank, could you please send me (via e-mail) a censored version of your extensions.conf file?

- open exec.php
- download: /usr/local/etc/asterisk/extensions.conf

[simondale]

Hi Michael,

Yes I was using an "X." pattern which seems to be pointless anyhow, I can just leave it blank.

I've left the pattern box blank and then added each of my phones in on their own line below.  I've then done the same for my two other SIPGate accounts.

It seems to be working perfectly this way round and prepends the CallerID as required.  Excellent!

It does seem to lose the incoming callerID setting if I change anything else on the provider screen in IE, but I think that has already been mentioned?

Thanks a lot for your help

Simon