[Home]

Summary:ASTERISK-08840: Incoming calls rejected
Reporter:Danny Desbiens (newtekcc)Labels:
Date Opened:2007-02-19 10:08:28.000-0600Date Closed:2007-04-03 11:30:05
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Core/General
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) AsteriskNOW.pdf
Description:I obtain the following message when calls is sent to me by my iax provider.

Notice[2875]: chan_iax2.c:6754 socket_process: Rejected connect attempt from 64.26.157.230, who was trying to reach '4168487537@'

I've configured the incoming rules to send any unmatched calls from this provider to a phone.
Comments:By: Danny Desbiens (newtekcc) 2007-02-20 21:56:33.000-0600

I'd like to add that I am able to make outgoing calls via my provider.  Only the incoming calls are not being handled.
By: Serge Vecher (serge-v) 2007-02-21 09:10:25.000-0600

what makes you believe this is an Asterisk NOW problem? Please read bug guidelines and post relevant debugging information, as well as respective config for the iax channel.
By: Danny Desbiens (newtekcc) 2007-02-22 09:29:00.000-0600

I feel that this is an AsteriskNOW issue as I've configured everything using the gui interface.

I'm able to make outgoing calls without an issue, however incoming calls are being rejected as per the asterisk CLI.

I will post screenshots of my config.
By: Danny Desbiens (newtekcc) 2007-02-22 09:54:58.000-0600

config has been posted..
If you require any additional, please do not hesitate to ask.
By: Justin Farrelly (vercet) 2007-02-22 21:09:24.000-0600

I have has the same issue - exactly it seems - with Teliax asa provider. the IAX circuit is seen and registered, but incoming calls fail in exactly the manner you describe here. I have tried setting specific routing on incoming numbers, the "catchall" routing, and changed my providers sending method from "auth" to no auth, but the same issue - the call arrives at the AsteriskNOW box and odes not get routed. I have Three SIP phones and a minimal setup.
By: Serge Vecher (serge-v) 2007-02-23 09:17:13.000-0600

what does extensions.conf look like?
By: Danny Desbiens (newtekcc) 2007-02-23 15:32:53.000-0600

include => voicemenu-custom-1

[voicemenu-custom-1]
comment = mainmenu
exten = s,1,Answer
exten = s,2,Background(thank-you-for-calling)
exten = s,3,Background(if-u-know-ext-dial)
exten = s,4,Background(otherwise)
exten = s,5,Background(pls-hold-while-try)
exten = s,6,Background(to-reach-operator)
include = default

[asterisk_guitools]
exten = executecommand,1,System(${command})
exten = executecommand,n,Hangup()
exten = record_vmenu,1,Answer
exten = record_vmenu,n,Playback(vm-intro)
exten = record_vmenu,n,Record(${var1})
exten = record_vmenu,n,Playback(vm-saved)
exten = record_vmenu,n,Playback(vm-goodbye)
exten = record_vmenu,n,Hangup
exten = play_file,1,Answer
exten = play_file,n,Playback(${var1})
exten = play_file,n,Hangup
hasbeensetup = N

[DID_trunk_1]
include = default
exten = _X.,1,Goto(default|601|1)
exten = s,1,Goto(default|601|1)
exten = _4168487537,1,Goto(default|601|1)

[numberplan-custom-2]
plancomment = UnlimitelOUT
include = default
exten = _905XXXXXXX,1,Macro(trunkdial,${trunk_1}/${EXTEN:0})
comment = _905XXXXXXX,1,905Local,standard
exten = _416XXXXXXX,1,Macro(trunkdial,${trunk_1}/${EXTEN:0})
comment = _416XXXXXXX,1,416Local,standard
exten = _647XXXXXXX,1,Macro(trunkdial,${trunk_1}/${EXTEN:0})
comment = _647XXXXXXX,1,647Local,standard
exten = _289XXXXXXX,1,Macro(trunkdial,${trunk_1}/${EXTEN:0})
comment = _289XXXXXXX,1,289Local,standard
exten = _1XXXXXXXXXX,1,Macro(trunkdial,${trunk_1}/${EXTEN:1})
comment = _1XXXXXXXXXX,1,Long Distance,standard
exten = _911,1,Macro(trunkdial,${trunk_1}/${EXTEN:0})
comment = _911,1,911,standard
By: James Lyons (james) 2007-02-23 16:15:15.000-0600

The reason you're incoming calls are not being 'handled' is due to your provider not having a dialplan context configured.

Can you paste your users.conf?
By: Danny Desbiens (newtekcc) 2007-02-23 16:26:44.000-0600

callwaiting = yes
threewaycalling = yes
callwaitingcallerid = yes
transfer = yes
canpark = yes
cancallforward = yes
callreturn = yes
callgroup = 1
pickupgroup = 1
host = dynamic
localextenlength = 3
allow_aliasextns = yes

[trunk_1]
secret = ******
provider =
trunkstyle = customvoip
username = 4168487537
trunkname = Custom - Unlimitel
callerid =
hasexten = no
hassip = no
hasiax = yes
registeriax = yes
By: James Lyons (james) 2007-02-23 16:30:20.000-0600

does adding 'context = DID_trunk_1' to the [trunk_1] context of your users.conf fix your issue?

you will need to reload/restart asterisk for your changes to take affect
By: Danny Desbiens (newtekcc) 2007-02-23 22:27:34.000-0600

I apologize..  I was missing details in my users.conf

here is the full version:
[trunk_1]
secret = *****
provider =
trunkstyle = customvoip
username = 4168487537
trunkname = Custom - Unlimitel
callerid =
hasexten = no
hassip = no
hasiax = yes
registeriax = yes
registersip = no
host = iax01.unlimitel.ca
dialformat = ${EXTEN:1}
context = DID_trunk_1
group =
insecure =
fromuser =
fromdomain =


By: James Lyons (james) 2007-02-26 11:13:26.000-0600

Please post console output with 'iax2 set debug' as the call comes in.
By: Danny Desbiens (newtekcc) 2007-02-28 07:55:59.000-0600

Tx-Frame Retry[-01] -- OSeqno: 002 ISeqno: 002 Type: IAX     Subclass: ACK
  Timestamp: 00025ms  SCall: 00004  DCall: 00058 [206.191.37.138:4569]
Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: NEW
  Timestamp: 00019ms  SCall: 00171  DCall: 00000 [206.191.37.138:4569]
  VERSION         : 2
  CALLED NUMBER   : 4168487537
  CODEC_PREFS     : (ulaw|gsm)
  CALLING NUMBER  : 6472339600
  CALLING PRESNTN : 0
  CALLING TYPEOFN : 0
  CALLING TRANSIT : 0
  LANGUAGE        : en
  USERNAME        : 4168487537
  FORMAT          : 4
  CAPABILITY      : 63494
  ADSICPE         : 2
  DATE TIME       : 2007-02-28  08:54:48

[Feb 28 08:54:50] NOTICE[2340]: chan_iax2.c:6754 socket_process: Rejected connec                                                                             t attempt from 206.191.37.138, who was trying to reach '4168487537@'
Tx-Frame Retry[-01] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: ACK
  Timestamp: 00019ms  SCall: 00002  DCall: 00171 [206.191.37.138:4569]
Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: REJECT
  Timestamp: 00003ms  SCall: 00002  DCall: 00171 [206.191.37.138:4569]
  CAUSE           : No authority found
  CAUSE CODE      : 50

Rx-Frame Retry[ No] -- OSeqno: 001 ISeqno: 001 Type: IAX     Subclass: ACK
  Timestamp: 00003ms  SCall: 00171  DCall: 00002 [206.191.37.138:4569]
By: Justin Farrelly (vercet) 2007-02-28 09:12:06.000-0600

I managed to capture the IAX2 debug message for my issue: Here is (I think) the relevent bit.

steel*CLI>
   -- Registered IAX2 to '207.xxx.xxx.3', who sees us as 71.xxx.xxx.34:4569 with no messages waiting

Tx-Frame Retry[-01] -- OSeqno: 002 ISeqno: 002 Type: IAX     Subclass: ACK    
  Timestamp: 00082ms  SCall: 00001  DCall: 00357 [207.174.202.3:4569]
 == Parsing '/etc/asterisk/users.conf': Found
 == Parsing '/etc/asterisk/extensions.conf': Found
Rx-Frame Retry[ No] -- OSeqno: 000 ISeqno: 000 Type: IAX     Subclass: NEW    
  Timestamp: 00015ms  SCall: 00361  DCall: 00000 [207.xxx.xxx.3:4569]
  VERSION         : 2
  CALLED NUMBER   : 2812010018
  CODEC_PREFS     : (gsm)
  CALLING NUMBER  : 8323xxx627
  CALLING PRESNTN : 0
  CALLING TYPEOFN : 0
  CALLING TRANSIT : 0
  CALLING NAME    : 8323xxx627
  LANGUAGE        : en
  FORMAT          : 2
  CAPABILITY      : 63490
  ADSICPE         : 2
  DATE TIME       : 2007-02-28  09:01:02
steel*CLI>
[Feb 28 09:02:20] NOTICE[3479]: chan_iax2.c:6771 socket_process: Rejected connect attempt from 207.xxx.xxx.3, request '2812010018@default' does not exist
Tx-Frame Retry[000] -- OSeqno: 000 ISeqno: 001 Type: IAX     Subclass: REJECT
  Timestamp: 00013ms  SCall: 00002  DCall: 00361 [207.xxx.xxx.3:4569]
  CAUSE           : No such context/extension
  CAUSE CODE      : 3
By: Justin Farrelly (vercet) 2007-02-28 09:13:52.000-0600

So for me, it would appear I have not correctly configured AsteriskNOW via the GUI. What bit did I miss?
By: Justin Farrelly (vercet) 2007-03-02 11:15:39.000-0600

Ok, I have done some further investigation. If you have the iax channel coming in with a stanza for the iax.conf, such as (in my case) teliax, the call fails as it did for newtek - Cause 50, No Authority. If it comes in as the default, it fails as mine did - no connect/extension, cause 3. I have pushed, pulled and twiddled every GUI knob I can find and cant get it to accept calls either with or without my providers "stanza". I think I am back to this being a bug, and not my knowledge of the GUI.
By: Danny Desbiens (newtekcc) 2007-03-05 14:27:34.000-0600

any news on this item?
I've been without incoming calls since Feb 20.

I can provide any information required.
By: James Lyons (james) 2007-03-05 14:35:41.000-0600

newtekcc, If you add an iax user to iax.conf does this resolve the issue?

[4168487537]
secret = *****
callerid =
host = iax01.unlimitel.ca
context = DID_trunk_1
type=user
By: Danny Desbiens (newtekcc) 2007-03-05 15:27:28.000-0600

That did the trick.  Everything is now functional.


Is *NOW supposed to add that entry upon setup of an IAX provider?
Maybe I missed a step?
By: James Lyons (james) 2007-03-05 15:42:01.000-0600

No, this is a bug having to do with the iax username setting in users.conf not being passed to chan_iax2.
By: James Lyons (james) 2007-03-05 15:44:02.000-0600

Assigning to Pari as this is a bug within users.conf/GUI implementation.


Pari, it appears as though the username and/or context variables are not being picked up by chan_iax2. After user added respective values to iax.conf, Asterisk began receiving calls again as normal.
By: Danny Desbiens (newtekcc) 2007-03-05 15:54:31.000-0600

Thanks for the help guys..  Keep up the great work.
I'll advise of any additional issues, however everything else thus far seems very good.

Very impressed with the solution.


By: Pari Nannapaneni (pari) 2007-03-13 22:18:45

James, is this going to be fixed in asterisk or do we
need to come up with a work around for this in the GUI ?
By: Pari Nannapaneni (pari) 2007-03-29 00:58:59

Russell - please look at james note - 0060363
and let me know how this should be handled.

thanks
Pari
By: Russell Bryant (russell) 2007-04-03 11:24:40

This is not actually a bug, but just a misunderstanding of what the values in users.conf mean.

The "username" section in users.conf is only used for what we use as a username for calling them.

If the username that the provider will use for calling us is the same, then that needs to be what is contained in brackets.  Given the current users.conf entry, the username the provider would have to use is "trunk_1", which is almost certainly never going to work.
By: Pari Nannapaneni (pari) 2007-04-03 11:30:05

> (0061862)
well in that case, we now have an ability to rename trunk to whatever the user wants. When a custom trunk is created it will how ever be created in a standard naming concention like trunk_4 or tunk_9, but hte user can later go to options and rename the trunk name to what ever he wants.