SIP ITSP Proxy Addresses - I have 10 of them?

[stownsend]

my SIP Provider gave me 10 SIP ITSP Proxy Addresses to connect to.

I have 3 SIP Lines configured. One with 2 IPs and 2 with 4 IPs.
The main one with the 2 IPs also has Specific SIP URI Groups that are used from ARS.
The other 2 SIP Lines with 4 IPs each only have Group 0 0

Reading though the ITSP Proxy Addresses info, this seems to be more for Outbound Calling and not Inbound Calling?

If the IPs in the first SIP Line that have the Specific ARS Groups is not Online, The Outbound call wont use the other SIP Line that is Group 0 0?

Seems like when we added these in there they said that I needed the IPs in there to be able to receive Calls from those IPs? That seems different from what the Hep says for ITSP Proxy Addresses.

Any Clarification?

Thank you,
Scott<-

 

[amriddle01]

Any clarification needs to some from the provider, if done properly all you need is a URI. I would be very wary of any provider that makes you do their job by adding loads of alternate proxy addresses etc.

Accident waiting to happen springs to mind

 

[stownsend]

Thank you for your reply. the Reply form my SIP Provider is Below. From their reply it seems like I should be using the following for my ITSP Proxy Address:
[tt]us-west.p.SIP-Provider.net.[/tt]

I'm not sure if I should be using:
[tt]us-west.p.SIP-Provider.net.(2)
[/tt] or just
[tt]us-west.p.SIP-Provider.net.
[/tt]

I do see the Options hitting the server.
The first profile has valid IP's to some of our older servers.
The other IP's I do not recognise. They may be IP's that we have transitioned away from or belong to some other provider. None of them responded to pings.
Our recommendation is to use the SRV records to base your profiles on.

# dig _sip._udp.us-west.p.SIP-Provider.net SRV
;; ANSWER SECTION:
_sip._udp.us-west.p.SIP-Provider.net. 3600 IN SRV 10 10 7000 lb001.sjc.p.SIP-Provider.net.
_sip._udp.us-west.p.SIP-Provider.net. 3600 IN SRV 20 20 7000 lb001.ord.p.SIP-Provider.net.

#dig _sip._udp.us-east.p.SIP-Provider.net SRV
;; ANSWER SECTION:
_sip._udp.us-east.p.SIP-Provider.net. 3497 IN SRV 10 10 7000 lb001.ewr.p.SIP-Provider.net.
_sip._udp.us-east.p.SIP-Provider.net. 3497 IN SRV 20 20 7000 lb001.ord.p.SIP-Provider.net.

#dig _sip._udp.us-central.p.SIP-Provider.net SRV
;; ANSWER SECTION:
_sip._udp.us-central.p.SIP-Provider.net. 1943 IN SRV 20 20 7000 lb001.ewr.p.SIP-Provider.net.
_sip._udp.us-central.p.SIP-Provider.net. 1943 IN SRV 10 10 7000 lb001.ord.p.SIP-Provider.net.

Basically defining fail over.
A records for the above.

# dig lb001.ewr.p.SIP-Provider.net.
;; ANSWER SECTION:
lb001.ewr.p.SIP-Provider.net. 3600 IN A <IP Address>

# dig lb001.ord.p.SIP-Provider.net.
;; ANSWER SECTION:
lb001.ord.p.SIP-Provider.net. 3600 IN A <IP Address>

# dig lb001.sjc.p.SIP-Provider.net.
;; ANSWER SECTION:
lb001.sjc.p.SIP-Provider.net. 900 IN A <IP Address>

Does that make sense?

The ones you have are valid and are not planned for removal. So you can continue to use them. But the others are newer and more reliable.
You probably want to use the us-west.p.SIP-Provider.net records.
The servers for in ord (central) group are planned to be moved to a new data center, so the IP will be changing when that happens. There will be notifications sent out around that change.
So it is best if you can set it up to use the SRV records rather than putting in the IPs that they resolve to.
If you can set it to use the SRV records, you would only use one name for the profile. Like us-west.p.SIP-Provider.net. When you put it in, do not include the _sip._udp. They are automatically added by your system as part of the standard way of working with SRV records.