SUGGESTIONS Routing calls from specific trunk - non-standard DID

mainenotarynet

Not really a Guru - Just a long time user
Joined
May 29, 2010
Messages
619
Reaction score
82
Location
Bangor, ME USA
Along with many other things I am (some not so nice :smile5: ) I am an amateur radio operator. There is a system out there called Hamshack Hotline (4 servers tied by IAX and over 1,000 extensions) - I have an extension on this system (4329) and can make (and now receive (probably for a long time, no one calls me :smile5: ) ) calls. But the caller ID is a person's extension and the number they call is MY extension. How would I set up an inbound route to catch calls from this one specific trunk. My CDR shows this :
"DFLT:UNKNOWN" <5006>sDial43290ANSWERED

The DFLT says it came through the Default Catch All route -- I did set up - while testing with another person to catch CID's as 4XXX -- well I guess wildcards do not work here. But the DID called to shows up as the "s"

So my question is how to get calls to my IAX2 Trunk using non satndard length CIDs to prooperly rout to the HH:CID route. The unknown on the name is understandable as it is not a NANP standard and lookup sources would not know what to do with it.

Any suggestions or help would be greatly appreciated.

Some people using HamshackHotilne are using IncrediblePBX on a RasPi3, So if I get mine working we may get more members here too :party:
 

dallas

Active Member
Joined
Oct 21, 2007
Messages
234
Reaction score
36
Location
Sydney, Australia
The DFLT says it came through the Default Catch All route -- I did set up - while testing with another person to catch CID's as 4XXX -- well I guess wildcards do not work here. But the DID called to shows up as the "s"
You can use wildcards in inbound routes. In this example I accept all calls starting with 0247 of any number length. you prefix the CID with an underscore to tell asterisk that it's a dial pattern.
I know this isn't exactly what you want and I don't know if the inbound route will allow a DID of "s" but it may help.

2473
 

mainenotarynet

Not really a Guru - Just a long time user
Joined
May 29, 2010
Messages
619
Reaction score
82
Location
Bangor, ME USA
Custom context, not in the cards. I tried that with Piaf Green and Purple with the custom contexts module and paging Intercom and other features would not work in CC.

OK Dallas, I had just 4XXX (no underscore), that may be my error. I can leave the DID blank and see what happens. "s" happens frequently so adding "s" as a did my be a weird outcome in the long run.

What I am trying to understand is why the "s" andnot the DID they called on the IAX2 trunk -- 4329?

See if I put that in the DID, I'm not sure if it would follow inbound route or shove to Any/Any. According to another user My caller ID is sent as "W1KMC Trunk"<4329> -- What I have sent in my system is "W1KMC-Kevin Bangor ME US"<4329> so the main system is setting the caller ID, but that is when I call out. What I am getting when people call ME is "[my prefix]:UNKNOWN"<their Ext> e.g. DFLT:UNKNOWN 4996 (DFLT is the Any/Any catch all route). What it should be is HH:KM4FTY Joe 14144 where HH is the prefix for the IAX2 trunk. I should not see the "s"

Hope this is a little clearer, I will try the underscore and see what happens.
 

dallas

Active Member
Joined
Oct 21, 2007
Messages
234
Reaction score
36
Location
Sydney, Australia
You can leave the DID blank and it will match only on the CID. The only problem will be that an incoming call with CID of 4XXX on ANY trunk will be sent to 4329.
 

dallas

Active Member
Joined
Oct 21, 2007
Messages
234
Reaction score
36
Location
Sydney, Australia
Kevin, you are on the otherside of the world to me which makes for a long time between posts. If trying the underscore isn't the fix I'm happy to troll through a log file to see what's happening.
Happy to help out a fellow ham.
 

Members online

No members online now.

PIAF 5 - Powered by 3CX

Forum statistics

Threads
22,560
Messages
138,866
Members
14,669
Latest member
cleron