[Home]

Summary:ASTERISK-00480: Order of entries in iax.conf causes failures
Reporter:John Todd (jtodd)Labels:
Date Opened:2003-11-04 18:40:43.000-0600Date Closed:2011-06-07 14:10:20
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:It seems that addition of a "host=dynamic" peer placed after statically defined hosts causes inbound call failures.

****** ADDITIONAL INFORMATION ******

The parser for iax.conf seems to be grabbing the peer name "fooorg" and trying to apply it to calls inbound from peer "iax-sproket" - I don't know why.  Putting the "dynamic" peers at the top of the file cures the symptoms, but if I add dynamic peers below the static peers in the config file, things break.  (note: hosts and passwords are ficticious)


This verison of the iax.conf file works fine:

[general]
port=5036

[fooorg]
host=dynamic
type=friend
qualify=500
disallow=all
allow=gsm
auth=md5
secret=g0oxg2e4
context=iax-fooorg-in
amaflags=billing
accountcode=fooorg


[iax-sproket]
host=226.134.176.114
context=iax-sproket-in
type=friend
qualify=500
auth=md5
secret=m3t331q
trunk=yes


[iax-smith]
host=63.262.100.193
context=iax-smith-in
type=friend
qualify=500
auth=md5
secret=lxte3on



------------------------
But this version of the iax.conf file fails when calls are presented from iax-sproket:


[general]
port=5036

[iax-sproket]
host=226.134.176.114
context=iax-sproket-in
type=friend
qualify=500
auth=md5
secret=m3t331q
trunk=yes


[iax-smith]
host=63.262.100.193
context=iax-smith-in
type=friend
qualify=500
auth=md5
secret=lxte3on


[fooorg]
host=dynamic
type=friend
qualify=500
disallow=all
allow=gsm
auth=md5
secret=g0oxg2e4
context=iax-fooorg-in
amaflags=billing
accountcode=fooorg

----------------------

This is the error that happens when an inbound calls is presented from iax-sproket:

pbx*CLI>
Rx-Frame Retry[No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: NEW    
  Timestamp: 00001ms  SCall: 16386  DCall: 00000 [226.134.176.114:4569]
  VERSION         : 2
  CALLED NUMBER   : 5045819896
  CALLING NUMBER  : 2155551212
  LANGUAGE        : en
  FORMAT          : 4
  CAPABILITY      : 65407
  ADSICPE         : 2
  DATE TIME       : 124029991

Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: AUTHREQ
  Timestamp: 00001ms  SCall: 00005  DCall: 16386 [226.134.176.114:4569]
  AUTHMETHODS     : 2
  CHALLENGE       : 186575006
  USERNAME        : fooorg

Rx-Frame Retry[No] -- OSeqno: 001 ISeqno: 001 Type: IAX     Subclass: AUTHREP
  Timestamp: 00012ms  SCall: 16386  DCall: 00005 [226.134.176.114:4569]
  MD5 RESULT      : faf0c6b74a2cf9113f3984a4f6bfa6e8

Tx-Frame Retry[000] -- OSeqno: 001 ISeqno: 002 Type: IAX     Subclass: REJECT
  Timestamp: 00011ms  SCall: 00005  DCall: 16386 [226.134.176.114:4569]
  CAUSE           : No authority found

Tx-Frame Retry[001] -- OSeqno: 001 ISeqno: 002 Type: IAX     Subclass: REJECT
  Timestamp: 00011ms  SCall: 00005  DCall: 16386 [226.134.176.114:4569]
  CAUSE           : No authority found

Comments:By: Brian West (bkw918) 2003-12-14 12:36:15.000-0600

jtodd is this still an issue?  I think this has been fixed.
By: Brian West (bkw918) 2004-01-07 00:05:58.000-0600

is this still an issue?
By: John Todd (jtodd) 2004-01-09 21:16:07.000-0600

This seems to be resolved, at least in my tests when adding dynamic hosts behind static hosts I no longer see failures.