SIP Line issue

[jimrit]

New set up, Twillio SIP trunk, R 11.04 IPOffice,, Twilio has 4 IP address's. 54.172.60.0 .1 .2 and .3
I set up a SIP Trunk on each of these, and they all have a singular URI line group 0 on inbound and outbound. Currently just have one inbound number. Half of the time, calls into that number hit one of the 4 SIP lines and is routed as it is supposed to be. The other half of the attempts get interrupted before it hits the system with an operator type interupt... cant be accessed as dial.. quick busy or something else. When it hits the system, it works as intended. When it doesnt hit the system Twillio shows it was some type of error communicating with the system. Dont think there are any traffic problems.. most testing was done in the middle of the night when there wasnt any local traffic. Any Thoughts on the possible causes?

 

[derfloh]

I guess you connect to all servers through the same account? The four servers are probably as fallback and not to connect to all of them simultaneously. Enter the IPs as 'ITSP Proxy' addresses. One line and one URI only.

Usually carriers give you one FQDN instead of IPs and IPO decides what server to connect through DNS requests (NAPTR/SRV).

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[TouchToneTommy]

Why not just enter all 4 addresses in the ITSP Proxy Address field?

This is the SIP Proxy address used for outgoing SIP calls. The address can be specified in the following ways:

A list of up to 4 IP addresses, with each address separated by a comma or space.

The addresses can include an indication of the relative call weighting of each address compared to the others. This is done by adding a w N suffix to the address where N is the weighting value. For example, in the list 213.74.81.102w3 213.74.81.100w2, the weighting values assigns 1.5 times the weight of calls to the first address. The default weight if not specified is 1. A weight of 0 can be used to disable an address. Weight is only applied to outgoing calls.

If there is more than one proxy defined, and no weight indication, then calls are only sent to the first in the list until there is a failure at which point the next proxy is used.

If the Calls Route via Registrar setting below is enabled, the weighting is applied to registrations rather than calls

54.172.60.0w1,54.172.60.1w1,54.172.60.2w1,54.172.60.3w1

 

[jimrit]

Avaya did not like it with 4 IP addresses on the same line separated with a comma or with a blank. It gave me a red error level and would not work. I read another listing that separated them into 4 lines.... and had success all on the same URI, same credentials.. I have success.. part of the time... which isnt enough it is driving me batty

 

[jimrit]

error code is invalid characters. i have tried them a dozen times... with and with blanks and with commas, It likes neither

 

[jimrit]

more info


The final piece to the puzzle for us had to do with the IP address that Twilio sends SIP invites from for incoming calls to the Avaya system. To get this to work in the Avaya we had to set up 4 SIP "Lines" pointing to 4 different "ITSP IP Address" values and 4 "Incoming Call Routes" per DID because Twilio sends from 4 different domestic IP addresses. I did read some documentation about being able to leave the ITSP IP Address blank (0.0.0.0) since we do have the "ITSP Domain Name" populated but that does not seem to work in our situation.

In researching this on the Internet I surprisingly did not find much evidence of Avaya customers ever having to deal with this issue (with or without Twilio), however I did find some examples of some other PBX systems having this issue with connecting to Twilio but those systems seemed equipped to configure multiple IP addresses for a single line.


Thus my question - do any Avaya customers have a suggestion for an alternate configuration to make this work? Anything we could do on our firewall? Twilio does not support sending SIP Invites from a single IP address or via a proxy server address. Fortunately we only have about 10 DID's so this won't be that hard to setup and maintain.

 

[derfloh]

Choose another carrier. This behavior is more than stupid.

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[jimrit]

issue solved.. they have a second set of IP addresses that they also use... a backup/csrry over...etc.. i added those and it works just fine... wish i had known sooner,,,,, i do appreciate the help though i learned a lot just from your answers