Just as a followup, you need to be a bit careful and test this out if
you make any changes to your Broadvoice account. I added a second
virtual number and they switched the number that was previously
specifying a distinctive ring of Bellcore-dr3 to Bellcore-dr4. The last
number added now
I have a single Broadvoice account with more than one number. I am
trying to distinguish between the numbers on an inbound call. I have
already tried using different incoming extensions that match each number
but it always defaults to the primary. Someone earlier mentioned
SIPGetHeader as a
There was a patch for chan_sip a while back that broke out what
context a call rang into based on the distinctive ring information
that was sent by the peer. This is what I use to distinguish different
dialed numbers from them.
On 11/21/05, Mark Hulber [EMAIL PROTECTED] wrote:
I have a single
Mark,
1. Make sure that SIPGetHeader application is registered
CLI show application SIPGetHeader
if it is registered you'll get
-= Info about application 'SIPGetHeader' =-
[Synopsis]
Get a SIP header from an incoming call
[Description]
SIPGetHeader(var=headername):
Sets a channel variable to
Ok, your solution does work but in looking at my console output I saw that
SIPGetHeader was deprecated for the new dialplan function SIP_HEADER. Below is
my modification. You don't need a priority+101.
exten = 212999,1,Set(Var_Alert=${SIP_HEADER(Alert-Info)})
exten =
