HT-503 Caller ID

Asterisk Asterisk Support
1

I’ve been googling and tinkering with configs for hours. I’ve setup an HT-503 to replace an HT-488 because if it’s lack of ability to pass caller ID.
The HT-503 keeps passing the caller ID of the SIP account rather than the CID of the ingress call on the FXO…

Dialplan

exten => s,1,Answer exten => s,2,Wait(1) exten => s,3,Set(Imgoingcrazy=${CALLERID(all)})

Debug

-- Executing [s@inbound-calls:3] Set("SIP/999-00000008", "Imgoingcrazy="" <999>") in new stack

I’ve fiddled with about every portion of the config for the 503. I’m starting to wonder if being a Noob Gingrich is part of my problem. If someone… anyone could give me some insight on this I’d greatly appreciate it.

sip.conf

[code][general]
port=5060
bindaddr=172.16.x.x
disallow=all
allow=G723.1
allow=ulaw
allow=alaw
dtmfmode=inband

[global]
nat=no

[5015]
type=friend
host=dynamic
secret=xxx
dtmfmode=rfc2833
context=outbound-calls
allow=all
nat=no

[999]
type=friend
secret=xxx
host=dynamic
dtmfmode=rfc2833
context=inbound-calls
nat=no

[ht503]
;#canreinvite=no
trunkname=ht503
host=172.16.x.x
port=5062
type=friend
insecure=port,invite
[/code]

2

insecure=port,invite will be rejected by current versions of Asterisk. and is usually wrong.

If you really need type=friend for the ht603, the From: header will be the account name. In that situation, you will have to configure both sides to support some other method of passing caller ID. Asterisk has built in support for Remote Party ID and P-Asserted-ID can be handled in the dialplan.

I seem to remember that type=friend often isn’t really needed in dynamic cases.

3

Thanks for the info, after pulling my head out of my anus and dropping back to full troubleshooting, I purchased a crap 20 dollar radio shack phone with caller ID to verify that the line even had caller ID. It doesn’t. :imp: