[Asterisk-Users] Accountcode being ignored?

[Aza]

> -----Original Message-----
> From: asterisk-users-bounces at lists.digium.com 
> [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of 
> Olle E. Johansson
> Sent: 06 June 2005 08:03
> To: Asterisk Users Mailing List - Non-Commercial Discussion
> Subject: Re: [Asterisk-Users] Accountcode being ignored?
> 
> Nabeel Jafferali wrote:
> > I have a sip.conf entry for a customer's PBX (IP based 
> authentication) 
> > that
> > reads:
> > 
> > [customer]        
> > type=friend   
> > context=customer
> > host=x.x.x.x
> > accountcode=10000
> > disallow=all
> > allow=g729
> > 
> > When the customer makes a call to my * server, * recognizes 
> the peer 
> > correctly. However, for some reason, the AccountCode is 
> blank. I have 
> > a
> > NoOp(${ACCOUNTCODE}) and the CLI shows:
> > 
> >     -- Executing NoOp("SIP/x.x.x.x-0821e058", "") in new stack
> > 
> > indicating a blank AccountCode.
> > 
> > I tried username-based authentication and have the exact 
> same issue. 
> > Anyone have any ideas on why this is happening?
> > 
> Are there any other entries with the same IP address in the 
> sip.conf file? When you match on IP, the *last* match in the 
> file is choosen.
> 
> /O

I had a similar problem where some SIP and IAX accounts would not pick up
the specified account code. It seemed to appear when the user agent was
another Asterisk server. It looked to me like that if the client Asterisk
server set its own callerid that it overrode what I was setting on the
server end and that this also caused the accountcode to be ignored. I didn't
spend too much time looking into it so I could be wrong.

My solution was to send the accounts into their own contexts and set the
accountcode and callerid their instead.

Aaron