Coming in on the wrong context

[fejj1]

No matter what I try, all calls coming in that should go to context=from2example come in on context=from3example.

I added a lot of stuff in that I have no clue what it is, but didn’t help this problem.

Thanks in advance for any suggestions.

[transport2]
type=transport
protocol=udp
bind=0.0.0.0:5061

[transport3]
type=transport
protocol=udp
bind=0.0.0.0:5062

[trunk2example]
type=registration
retry_interval=60
expiration=3600
auth_rejection_permanent=yes
server_uri=sip:voip.example.net
outbound_auth=trunk2example
transport=transport2
contact_user=99999963715
client_uri=sip:99999963715@voip.example.net

[trunk2example]
type=auth
auth_type=userpass
password=nunubiz
username=99999963715

[trunk2example]
type=endpoint
disallow=all
allow=alaw
allow=ulaw
allow=g729
aors=trunk2example
transport=transport2
outbound_auth=trunk2example
context=from2example
; just added these in - didn't help
from_domain=voip.example.net
from_user=99999963715
sdp_owner=99999963715
send_rpid=yes
force_rport=yes
timers=no

[trunk2example]
type=aor
contact=sip:99999963715@voip.example.net

[trunk2example]
type=identify
match=voip.example.net
endpoint=trunk2example

[trunk3example]
type=registration
retry_interval=60
expiration=3600
auth_rejection_permanent=yes
server_uri=sip:voip.example.net
outbound_auth=trunk3example
transport=transport3
contact_user=99999963554
client_uri=sip:99999963554@voip.example.net

[trunk3example]
type=auth
auth_type=userpass
password=nunubiz
username=99999963554

[trunk3example]
type=endpoint
disallow=all
allow=alaw
allow=ulaw
allow=g729
aors=trunk3example
transport=transport3
outbound_auth=trunk3example
context=from3example
; just added these in - didn't help
from_domain=voip.example.net
from_user=99999963554
sdp_owner=99999963554
send_rpid=yes
force_rport=yes
timers=no

[trunk3example]
type=aor
contact=sip:99999963554@voip.example.net

[trunk3example]
type=identify
match=voip.example.net
endpoint=trunk3example

[david551]

I’d assume that is because the type=identify section doesn’t have a transport parameter, so, when matching by IP only one section with that IP will match, for all transports. You’d have to use dialplan to try and distinguish the two cases.

[fejj1]

Thanks! I was afraid that is the case. I’ve dealt with it in the dial plan.