[asterisk-gui] problem with new incoming calls feature

[Pari Nannapaneni]

Dorian Gray wrote:
 > what I find strange is that the context from users.conf shows up correctly in
 > 'iax2 show users' and yet incoming calls are rejected.

Jason and I were testing the DID feature last week with two service providers and we ran into
the same issues. Also certain ITSPs use a specified context for sending the incoming calls.

 > workarounds:
 > 1. changing the context of {iaxtel,iaxfwd} in iax.conf to DID_trunk_n fixes
 > this. or, adding the extension directly in default context of extensions.conf
 > fixes this.
 > 2. additionally, adding a block for non-default provider e.g. vitel-inbound
 > and setting its context to DID_trunk_n fixes this.

as you mentioned, I thought of adding a block for the provider and setting its context to DID_trunk_n fixes this,
but this might arise new issues like
A) When deleting a provider, we have to lookup the blocks that are using DID_trunk_n context and delete them
B) we might have to add one more comment field to distinguish user entries from the 'block for the provider'
    in users.conf, which in my opinion might be unnecessary

The way I was planing to fix it was to scrap the 'trunk_n'/'DID_trunk_n' naming convention
and use a user specified [provider_name] in users.conf and point its context to [DID_provider_name]
So when the user deletes the provider we can also delete the associated [DID_provider_name]
(just like it is done now)

I guess even this way we might have to add a comment field which will let us distinguish a trunk
from a user in users.conf. As of now the GUI checks if the context starts with 'trunk_',
if yes, it is a trunk other wise it assumes as a user.

Please feel free to make comments/suggestions/arguments about this.
We need to come up with a proper solution to handle the incoming calls so that it works
with any service provider (I've noticed that some service providers are just dialing 's@')

thanks,
-Pari



Dorian Gray wrote:
> nice to see that we can now configure DIDs, but there seems to be a problem:
> 
> the new incoming calls tab creates contexts in extensions.conf of the form
> [DID_trunk_n]
> exten = m,1,Goto(default|o|1)
> 
> and sets relevant context in users.conf to DID_trunk_n. cool.
> 
> however, incoming calls are rejected. at least in my case. it seems as if
> asterisk is still dependant only on user blocks defined in iax.conf, and not
> those with registeriax=yes in users.conf.
> 
> if it is a provider that happens to already be in iax.conf by default (e.g.
> iaxtel, iaxfwd) then I get rejection errors like "m at default" doesn't exist. if
> it is a custom provider e.g. vitel-inbound that is completely absent from
> iax.conf then the console error is that "m@" doesn't exist.
> 
> what I find strange is that the context from users.conf shows up correctly in
> 'iax2 show users' and yet incoming calls are rejected.
> 
> workarounds:
> 1. changing the context of {iaxtel,iaxfwd} in iax.conf to DID_trunk_n fixes
> this. or, adding the extension directly in default context of extensions.conf
> fixes this.
> 2. additionally, adding a block for non-default provider e.g. vitel-inbound
> and setting its context to DID_trunk_n fixes this.
> 
> however, it would be nice not to have to workaround but do the right thing
> with just the gui settings in users.conf
> 
> but maybe I'm just missing something...
> 
> 
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
> 
> asterisk-gui mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-gui