How to configure a public name for an specific range of SIP phones (SIP environment)

[JuanCarman]

We are trying to send "company#1" for an specific range of SIP phones from the phone system and "Company#2" for an specific range of SIP phones from the phone system, we are not trying to send an speccific main number (something that we can configure over public-unknown-numbering in the PBX.

I dont know if this is the correct queue for this question, but I tried to find a thread that could talk about something similar, but I was not able to find any thread.

I really appreciate your comments and assistance,
Regards
FC

 

[kyle555]

SIP: do it in the SBC.
ISDN: There's a special application to override outgoing name display

 

[JuanCarman]

Thank you for the update Kyle555, I have tried to find documentation but I have not been able to find something specific. Is there something you can help me out with? Thank you

 

[kyle555]

Look up sigma scripts in devconnect notes for any sip trunking interop. Something like `replace URI.USER `mycompany`
If you, hypothetically, had 1 CM, 1 SM, 1 SBC, you could cut it up different ways.

Say it's a multi-tenant 'as-a-service' solution, you'd have 2 trunks from CM for "outbound.customer1.com" and outbound.customer2.com". You'd have 2 inside IPs on the SBC, SM would have dial pattern "x@outbound.customer1.com route to sip entity with inside SBC IP 1" and the same for customer 2.
Then, the SBC flow would be like "anything received on inside interface for customer1, replace URI.USER with COMPANY1"

Say it's just 2 company names for 1 enterprise and you don't care about segregation - like "Happy Kid Movies Inc" and "Movies You Watch After Inc", you could do it with 1 IP and routing policy to the SBC and sigma script "if uri user contains@customer1.com, replace uri user with COMPANY1"

For PRI, look at

http://downloads.avaya.com/css/P8/documents/100121721

SA9086, if enabled, lets you specify the replacement name and/or number.
If you had 1 PRI, you could still have 2 trunk groups with channels 1-12 in trunk group 1 and 13-23 in trunk group 2. You could have customer1 as the name on trunk 1 and the same for 2, and in the later pages where you specify which ports (bchannels) are members of the group, you can specify which signaling group manages them.

To say, "trunk 1" with outgoing name 'customer1' can have 1 member, port 1b101 and be managed by signaling group 1. Trunk 2 can have 1 member, outgoing name customer2 and port 1b102 managed by sig group 1.