Get Access Denied on new SIP trunk

[billz0r]

So we've setup a new SIP trunk in our MiVB. The carrier says it's registered.
We can't make outbound calls on it. The users get Access Denied.
The SIP Trunk has the same COR as the other SIP trunk that works. 5 in this case.
All the phones are assigned COR 3
The ARS routes uses COR groups 1-9, depending on the ARS Digits Dialed.
COR 3 doesn't appear is any of the COR groups so I expected to be able to dial out.
COR 5 does appear in some of them.
Now the working SIP trunk uses COR 5 as well, hence why I used it again.
Is there somewhere else I need to allow outbound calls as when I change the ARS to use the new SIP trunk, with all the same COR values, it fails with access denied.

[sarond]

Might need to do a SIP trace to find out for sure.

Access Denied is normally a restriction the MiVB is giving. What if you make the ARS COR a 20? i.e. something that isn't used.

[billz0r]

Might need to do a SIP trace to find out for sure.

Access Denied is normally a restriction the MiVB is giving. What if you make the ARS COR a 20? i.e. something that isn't used.

Thanks, I have changed the ARS to use a COR group that has no restrictions on it at all (65 in this case). Waiting for the client to call back to let me know if it worked.
I'll google how to do a SIP trace. I haven't done 1 before.

[billz0r]

I fixed it.
Looks like it was SDP options of the SIP peer that fixed it.
The new SIP trunk was with the same provider but a different SIP Server. Seems the new server needed different settings.

[sarond]

Glad you got it sorted.

Look at the SIP TCPDUMP command for tracing SIP signalling.

If there is low traffic you can sometimes get away with SIP TAIL ON to display small output to maintenance screen.