911 dialing help- IP office 500 v2 ver 11.0 1

[TIgerV]

I have the above system, connected PRI to an adtran 908e SIP gateway.
Whenever I call 911 from certain extensions, it send the header FROM: 911@<sip domain>. TO:911@<sip domain>. All other calls go out with the proper caller ID. eg: 26012345486@<sipdomain>.
ONE extension calls 911 properly with the proper caller id.
Problem is that the SIP provider rejects the outgoing FROM header.
I know the Adtran is getting the outbound caller ID from the IPOffice, but where do I make it so that it has the proper header?
Can I tell the Adtran "When you see 911 as callerid change it to xxxxxxxxxx"?
I have tried MANY combinations, and just can't get it. Further, I see NO difference in the one station that works and the others.

--TIger

 

[Ekster]

In The UK, caller ID for emergency service calls is passed in the PAID Header. Could that be the case here?

 

[derfloh]

That sound like a bad configured dial short code.

 

[TIgerV]

This is what my ARS looks like for all 3 sites. The issue is that my phones config uses these same ARS routes. I don't see any difference in the user or extension that should cause this. (Redacted phone #s)

 

[derfloh]

If NSi is not set, maybe some information from Trunk Call Details or user‘s SIP entry is inserted.

 

[TouchToneTommy]

Remember that the call is leaving the IPO on a PRI and is connected to an Adtran 908e gateway - which is standard PRI towards the IPO and SIP towards the carrier. The mistranslation is happening within the Adtran

 

[derfloh]

I guess the NSi is missing though. Nevertheless the carrier should replace an wrong or missing caller ID with a valid one that belongs to that trunk.

 

[TIgerV]

@TouchToneTommy is there a way to tell the adorn that "If you see 911@ in the header, change it to xxxxxxxxxx@"?

Someone suggested adding this to the adtran
voice dial-plan 10 local 988
voice dial-plan 20 local N11
voice dial-plan 30 long-distance 1-NXX-NXX-XXXX
voice dial-plan 40 local NXX-NXX-XXXX
voice dial-plan 50 international 011-$

voice class-of-service AllowAll
default-level
permit-template NXX-XXXX
permit-template 1-NXX-NXX-XXXX
permit-template NXX-NXX-XXXX
permit-template 011-$
permit-template 988
permit-template N11
permit-template 933

 

[TIgerV]

anyone else with ideas?

 

[derfloh]

Maybe it would help if you test the suggestions and provide some feedback.

 

[TIgerV]

I see some pointing to what might be wrong, but nothing saying "DO THIS". I tried adding an NSI line to match the dial plan, and got no change. Still sending "911@"

 

[derfloh]

How are SIP trunk call details configured?

 

[Shaun E]

I see some pointing to what might be wrong, but nothing saying "DO THIS". I tried adding an NSI line to match the dial plan, and got no change. Still sending "911@"

Have you tried doing an ISDN trace in Monitor to see if the IPO is sending the correct details to the Adtran?

It would at least help identify where the issue lies. If the IPO is sending the right details then you need to look at the Adtran config and not the IPO. Both of them can manipulate caller ID and if it's the Adtran changing it, changing the ARS routes on the IPO won't help.