ICR and multiple accounts

[ipohead]

I have a series of numbers each with separate accounts from same provider which need to go to separate destinations - but all calls go to the first ICR based on their IP address.

I did try called number on the ICR but I note that all my numbers are followed by the same letters so the default right to left matching will not work. Should I just switch to left-right matching?

I see there are other options in SIP Line - SIP advanced or SIP line calls details so are these relevant?

 

[derfloh]

In SIP trunk settings there is something like call number match (don't know it out of my brain) where you can set it to 'To header user part'.

 

[ipohead]

Thanks Sipmeister!

I now have 'real' numbers coming is as +N but adding the to incoming number in the ICR doesn't seem to make any difference.

In SIP Line - SIP advanced the options for association method aside from the default source IP look to be for the hostname which will of course be the same for both lines or I have I missed something?

 

[Menniss]

This makes no sense to me, can you post an example invite?

 

[ipohead]

Thanks for checking. Line A running by itself

number A, credentials A, no incoming number in ICR to extn 400. Main works OK as only a single number, SIP call details Line Credentials A all set to auto. HG Main has SIP name main

Invite with actual numbers hidden

09:28:20 157051962mS SIP Call Tx: 26
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 81.187.30.116;branch=z9hG4bK2025022409282100010-1;rport
From: "07xxx xxxxxx" <sip:07xx xxxx@example.com>;tag=2025022409282100010
Call-ID: 2025022409282100010@2900-0601-0284-92
CSeq: 1 INVITE
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
Server: IP Office 11.0.4.7.0 build 6
Content-Length: 0
To: <sip:+44AAAAAAAAAA@192.168.0.201:5060;transport=udp>;tag=bbb7b74c84f640a3

Adding Line B

number B, credentials B, no incoming number in ICR to extn 408 408. SIP call details line B Credentials B all set to auto. HG Main has SIP name 408
not accepting incoming calls "no route to destination" or route to 400 Main and not 408 408

Both lines are from the same provider and hence the same IP address which I think is where the IPO is confused. Adding called number makes no difference.
I have read the docs and tried a few test setting but not completely clear on exactly which ones to change,

Screenshots for Line A. Line B is Line Group ID 27 etc

 

[ipohead]

From the help for R11.

SIP Trunk Advanced

Association Method: Default = By Source IP address. Software level = 8.0+. This field sets the method by which a SIP line is associated with an incoming SIP request. The search for a line match for an incoming request is done against each line until a match occurs. If no match occurs, the request is ignored. This method allow multiple SIP lines with the same address settings. This may be necessary for scenarios where it may be required to support multiple SIP lines to the same ITSP. For example when the same ITSP supports different call plans on separate lines or where all outgoing SIP lines are routed from the system via an additional on-site system.

·

By Source IP Address This option uses the source IP address and port of the incoming request for association. The match is against the configured remote end of the SIP line, using either an IP address/port or the resolution of a fully qualified domain name. This matches the method used by pre-8.0 systems.

·	"From" header hostpart against ITSP domain This option uses the host part of the From header in the incoming SIP request for association. The match is against the line's Domain Name.

·	R-URI hostpart against ITSP domain This option uses the host part of the Request-URI header in the incoming SIP request for association. The match is against the line's Domain Name.

·	"To" header hostpart against ITSP domain This option uses the host part of the To header in the incoming SIP request for association. The match is against the line's Domain Name.

·

"From" header hostpart against DNS-resolved ITSP domain This option uses the host part of the FROM header in the incoming SIP request for association. The match is found by comparing the FROM header against a list of IP addresses resulting from resolution of the line's Domain Name or, if set, the Proxy Server Address.

·

"Via" header hostpart against DNS-resolved ITSP domain This option uses the host part of the VIA header in the incoming SIP request for association. The match is found by comparing the VIA header against a list of IP addresses resulting from resolution of the line's Domain Name or, if set, the line's Proxy Server Address.

·	"From" header hostpart against ITSP proxy This option uses the host part of the “From” header in the incoming SIP request for association. The match is against the line's Proxy Server Address.

·	"To" header hostpart against ITSP proxy This option uses the host part of the From header in the incoming SIP request for association. The match is against the line's Proxy Server Address.

·	R-URI hostpart against ITSP proxy This option uses the host part of the Request-URI in the incoming SIP request for association. The match is against the line's Proxy Server Address.

 

[ipohead]

Looking at the help above isn't the Source IP Address, ITSP domain etc, going to be the same for all lines from the ITSP?

Tests so far shows that the IPO just reacts to the lowest numbered line and uses that destination.