SIP User Tab -- Anonymous Field 2

[twitchy087]

I am having lots of issues with this seemingly not working properly. My understanding is that enabled the "Anonymous" option will ONLY push Anonymous when the SIP URI is set to "Use Internal Data". Unfortunately, I am having "Anonymous" get pushed through all types of URI types. I have two URIs built per the the attached screenshot. They both route through a SIP trunk that allows all traffic to pass through. When I test without "Anonymous" checked, everything works fine however when "Anonymous" is checked, both URIs send "Anonymous". I have been able to replicate this same issue on two different systems now (8.1.73 and 9.0.5).

Is there something else that comes into play with this setting or is this simply a bug in the IPO?

Thanks in Advance.

 

[twitchy087]

I suppose it may help to actually attach the file...

 

[amriddle01]

I've noticed that on many releases not just the current ones. As there is no sensible route to let Avaya know such things I don't think anyone has bothered

 

[pkdev]

Can you tell us more detail on what you expect the IPO to do ? And maybe upload the entire config file ?

 

[amriddle01]

That field is not supposed to have any effect on SIP URI's that don't have "Use Internal Data" selected but it does

 

[twitchy087]

This customer has many locations connecting to a central PBX via MPLS. The idea is that we can dial 911 out through multiple URIs for the SIP provider to match and relay the proper info to the dispatcher. So, they want to make blocked outbound calls and to send the proper digits when dialing 911. Everything works fine without blocking via the "Anonymous" tab but everything goes to crap when that is introduced. I believe this is simply a bug as amriddle mentions. I just want to the tab to work ONLY on "Internal Data" URIs.. so disappointing

 

[pkdev]

For multisite customer I usually create an ARS for each site that override the calling number with the local site number.
In 9.1 you can use Location to assign the ARS to a specific site.
For previous versions you'll have to use User Rights (or set it manually for each user) to create a specific "Dial Emergency" shortcode

 

[twitchy087]

I have multiple ARS patterns set up and user rights to assign the proper short codes so all of that is fine and dandy. The problem is none of that matters when the system inserts "Anonymous" no matter what URI the call is being pushed out through.

I appreciate the input guys. Have a good day!

 

[pkdev]

Did you try to force the calling party in ARS using ".sXXXXXXX" ?
can you capture a SIP invite and post it ?

 

[pkdev]

I've found an Avaya doc which indicate that the only field that is not change by the block caller id is P-Asserted ID:

P-Asserted Identity field content
Without Call-Id blocking, this field essentially mirrors the From:field.
P-Asserted-Identity: " SipDisplayName " <sip: SipName@ITSP_Domain>
Call-Id blocking: using W in a short code, or by checking the User | SIP | Anonymous checkbox
results in the P-Asserted field being the only header that carries the calling party information,
and so is unchanged from the non-blocked case above.
P-Asserted-Identity: " SipDisplayName" <sip:SipName@ITSP_Domain>