I just started service with Broadvoice.com and everything seems to work. However, apparently my understanding of incoming sip contexts is less then what I thought it was. Could someone point me in the right direction? (* on a public address, CVS-HEAD-07/12/04, C7960 phones) In my sip.conf I have: [general] port = 5060 bindaddr = 0.0.0.0 allow=ulaw tos=0x18 ;sets ip tos bits (=lowdelay and throughput) context = bogon-calls ; Send SIP callers that we don't know about here context=from-broadvoice register=3035391111:secret@sip.broadvoice.com/5391111 <snip> [broadvoice] ;this is referenced for outgoing calls to Broadvoice.com type=peer username=3035391111 <snip> The problem I'm having with understanding this is for incoming calls from broadvoice. If I remove the "context=from-broadvoice" from the above, incoming calls from broadvoice are dropped into the bogon-calls context (no service available message). I've tried several different approaches to define another context with type=user, but can never get test calls from broadvoice to be handled in anything other then the bogon-calls context. What am I missing? Rich
> The problem I'm having with understanding this is for incoming calls > from broadvoice. If I remove the "context=from-broadvoice" from the > above, incoming calls from broadvoice are dropped into the bogon-calls > context (no service available message).just add the context = from-broadvoice to the [broadvoice] section like this: [general] ... context = bogon-calls ; Send SIP callers that we don't know about here ... [broadvoice] type=friend username=3035391111 host=... context=from-broadvoice i also have a fromuser (value equals username), fromdomain (value equals host) and insecure=very entry in that section to direct incoming calls from sipgate to the right context. as there is no way (other than the originating host) to identify such calls the we context used there should be quite limited.> I've tried several different approaches to define another context > with type=user, but can never get test calls from broadvoice to be > handled in anything other then the bogon-calls context.i use type=friend to handle incoming and outgoing connections in the same section, but you can also define one with type=peer and one with type=user. hope that helps, stefan
On Sun, 25 Jul 2004, Rich Adamson wrote:> I just started service with Broadvoice.com and everything seems to work. > However, apparently my understanding of incoming sip contexts is less > then what I thought it was. Could someone point me in the right > direction? (* on a public address, CVS-HEAD-07/12/04, C7960 phones) > > In my sip.conf I have: > [general] > port = 5060 > bindaddr = 0.0.0.0 > allow=ulaw > tos=0x18 ;sets ip tos bits (=lowdelay and throughput) > context = bogon-calls ; Send SIP callers that we don't know about here > context=from-broadvoice > register=3035391111:secret@sip.broadvoice.com/5391111 > <snip> > [broadvoice] ;this is referenced for outgoing calls to Broadvoice.com > type=peer > username=3035391111 > <snip>this doesn't address your question (I think the other post did) but it anticipates your next question.. Add dtmfmode=general to BOTH the general and broadvoice contexts in sip.conf. Asterisk seems to make an incorrect assumption about dtmf with broadvoice (on calls inbound to your box, that is) unless you set it in the general section as well. Greg