Cynjut
Member
- Joined
- Jul 15, 2009
- Messages
- 68
- Reaction score
- 11
I started experimenting with some inbound IAX phone connections. They worked fine - but now the inbound trunk (also IAX2) with my main office number rings busy. Here are some of the log entries that I believe are pertinent:
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == Binding IAX2 to default address 0.0.0.0:4569
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: -- Seeding '534' at 192.168.3.231:4569 for 60
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == Registered channel type 'IAX2' (Inter Asterisk eXchange Driver (Ver 2))
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == 10 helper threaads started
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == IAX Ready and Listening
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == Loaded firmware 'iaxy.bin'
[2009-10-21 15:42:24] NOTICE[3344] iax2-provision.c: No IAX provisioning configuration found, IAX provisioning disabled.
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: chan_iax2.so => (Inter Asterisk eXchange (Ver 2))
...skipping
[2009-10-21 15:43:11] VERBOSE[3373] logger.c: -- Format for call is ulaw
[2009-10-21 15:43:11] VERBOSE[3565] logger.c: -- IAX2/VoipStreet-13260 is ringing
[2009-10-21 15:43:11] NOTICE[3366] chan_iax2.c: Host 64.136.174.24 failed to authenticate as 534
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: -- IAX2/VoipStreet-13260 stopped sounds
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: -- IAX2/VoipStreet-13260 is busy
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: -- Hungup 'IAX2/VoipStreet-13260'
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: == Everyone is busy/congested at this time (1:1/0/0)
Why on earth would my inbound IAX trunk be expected to try to authenticate as extension 534?
As soon as I removed the IAX2 extensions, the inbound trunk worked just fine. This performs completely outside of my expectations. Any suggestions?
I'm running PIAF with the most up-to-date software.
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == Binding IAX2 to default address 0.0.0.0:4569
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: -- Seeding '534' at 192.168.3.231:4569 for 60
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == Registered channel type 'IAX2' (Inter Asterisk eXchange Driver (Ver 2))
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == 10 helper threaads started
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == IAX Ready and Listening
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: == Loaded firmware 'iaxy.bin'
[2009-10-21 15:42:24] NOTICE[3344] iax2-provision.c: No IAX provisioning configuration found, IAX provisioning disabled.
[2009-10-21 15:42:24] VERBOSE[3344] logger.c: chan_iax2.so => (Inter Asterisk eXchange (Ver 2))
...skipping
[2009-10-21 15:43:11] VERBOSE[3373] logger.c: -- Format for call is ulaw
[2009-10-21 15:43:11] VERBOSE[3565] logger.c: -- IAX2/VoipStreet-13260 is ringing
[2009-10-21 15:43:11] NOTICE[3366] chan_iax2.c: Host 64.136.174.24 failed to authenticate as 534
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: -- IAX2/VoipStreet-13260 stopped sounds
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: -- IAX2/VoipStreet-13260 is busy
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: -- Hungup 'IAX2/VoipStreet-13260'
[2009-10-21 15:43:12] VERBOSE[3565] logger.c: == Everyone is busy/congested at this time (1:1/0/0)
Why on earth would my inbound IAX trunk be expected to try to authenticate as extension 534?
As soon as I removed the IAX2 extensions, the inbound trunk worked just fine. This performs completely outside of my expectations. Any suggestions?
I'm running PIAF with the most up-to-date software.