We have all working, trunk registering (was the ethernet port), Passing to PRI (was a command I missed), and passing the name (again...I missed.).
<Substitute real numbers in the x spots>
Now, xxx-xxx-9903 is our main phone number. However, we have 3 numbers that ring in to us. xxx-xxx-9903 is our school, xxx-xxx-4553 is another office, and xxx-xxx-1869 is a third office on the same campus.
The Avaya sees the DNIS and routes the call just fine on inbound. On outbound, I want to send the appropriate outbound Caller ID, but register the SIP trunk ONLY with the 9903. SO, if I pick up an office phone, and dial out, I want to send xxx-xxx-4553 as my caller ID. BUT Sip registration at the carrier MUST be xxxxxx9903@<trunk location>.
It's not doing that, it's trying to register sip with xxxxxx4553@<trunk Location>.
Are we using HMR wrong?
Carrier had me modify this, but still not working:
voice codec-list "CARRIER SIP"
codec g711ulaw
codec g729
!
!
!
voice trunk T01 type sip
description "CARRIER SIP"
sip-server primary <TRUNK LOCATION>
sip-server validation register
domain "<TRUNK LOCATION>"
max-number-calls 9
register xxxxxx9903 auth-name "xxxxxx9903" password "NOTTODAYHACKERS"
codec-list "Frontier SIP" both
hmr VoIP_RPID out
grammar request-uri host domain
grammar from host domain
grammar p-asserted-identity host domain
!
voice trunk T02 type isdn
description "PRI to Avaya"
resource-selection circular descending
connect isdn-group 1
rtp delay-mode adaptive
codec-list "CARRIER SIP"
!
!
voice grouped-trunk PRI
trunk T02
accept $ cost 0
!
!
voice grouped-trunk SIP
trunk T01
accept $ cost 0
!
!
voice grouped-trunk "SIP > PRI"
!
!
hmr rule-set Outbound_RPID
message-rule RPID message-type request 10
add header remote-party-id position if-not-present new-value <sip:xxxxxx9903@TRUNK LOCATION>;party=calling;screen=no;privacy=off 10
!
hmr policy VoIP_RPID
rule-set Outbound_RPID 10
!
Hello TVining,
Do you need the HMR rule?
On the PRI voice trunk you can use the command: caller-id-override
There are a slew of options but in a nutshell, when a call is originated from the PRI trunk and it is going to be switched outbound to the SIP trunk, this command sets the Outbound CID for the SIP trunk messages sent upstream but the ADTRAN.
Geo
I do want to caller ID to be proper at the receiving end, just not for the sip trunk login
That command will affect the calling party information in the SIP Invite generated by the TA908e sent to the SIP server.