On Wed, Jun 10, 2015 at 11:30 PM, James Cloos cl...@jhcloos.com wrote:
RM == Richard Mudgett rmudg...@digium.com writes:
RM You can specify the dialplan context incoming calls go to when defining
RM the endpoint.
Obviously I've done that. The issue is that the CHAN_START cel event
does not
On Wed, Jun 10, 2015 at 6:22 PM, James Cloos cl...@jhcloos.com wrote:
I've finally gotten a box setup with pjsip.
I see that the CHAN_START cel event logs exten='s', context='default'
instead of the INVITEd extension and the endpoint's context.
All of the rest of the events log the expected
I've finally gotten a box setup with pjsip.
I see that the CHAN_START cel event logs exten='s', context='default'
instead of the INVITEd extension and the endpoint's context.
All of the rest of the events log the expected data.
This is unlike chan_sip.
Is this a bug? Or an expected behavorial
RM == Richard Mudgett rmudg...@digium.com writes:
RM You can specify the dialplan context incoming calls go to when defining
RM the endpoint.
Obviously I've done that. The issue is that the CHAN_START cel event
does not reflect the specified context and the INVITE's ruri like
chan_sip's
