Hi Team:
We have a Adtran 904 which R10.7 running and we are following the link below to add p-asserted-id )PAID) but it not adding it...but sends the number passed from the PRI side to SIP in both From header and PAID...
Page 5
If the adtran is detecting a PRI msg SETUP with ino that it is using to populate the PAID, would the add command on the voice trunk T01 not work?
match d-idani $ add p-asserted-identity 4056741212
had a typo
match ani $ add p-asserted-identity 4056741212
ujjvalkoul,
When I did that on 10.3 code I used HMR rule sets to modify the PAI. The following snippets are what I used, in your case you may not need the additional HMR rule set but I needed to use it because our ITSP had a special domain requirement that does not exactly follow the RFC:
!
voice trunk T01 type sip
description Provider Trunk
! insert needed provider connectivity code
sip-server primary XXX.XXX.net
domain "yyy.xxx.net"
!
hmr TRUNK out
!
register 5555553382 auth-name "5555555555" password encrypted "passwordhere"
!
trust-domain p-asserted-identity-required
p-assert-diversion
grammar p-asserted-identity host domain
!
!
voice grouped-trunk SIP
description "Descriptive Name"
trunk T01
accept $ cost 0
!
!
hmr policy TRUNK
rule-set PAI_Change 1
!
hmr rule-set PAI_Change
message-rule CHANGE_PAI_TO_TRUNK_NUMBER message-type any 1
match header p-asserted-identity match-value /555\d{7}/
modify header p-asserted-identity position first-match new-value /SRP_Test<sip:4056741212@yyy.xxx.net>/ 2
!
John Wable
Ujjvalkoul,
I wanted to see if you still having problems adding a P-Asserted_identity to your outbound SIP packets. I tested this on my lab unit and it appears to work properly in R10.7.0. If you are still unable to get it working, feel free to post additional questions here or open up a Technical Support ticket by calling 888-423-8726.
Thanks!
David