SIP trunk changed in MX4.1

[teretore]

Hi,
I have a serious problem with MX4.1 and SIP trunk
In old version I had parameters
Registration type = Broadworks
trusted = NO, and
in INVITE command was line "P-Preferred-Identity: <sip:sip.P00889785@pbx.operator.ee>,
this line is needed from my operator

and - in MX 4.1, if Registration type = Broadworks,
the parameter trusted is in this case overid-ed,
so in INVITE I can see line "P-Asserted-Identity: <sip:sip.P00889785@pbx.operator.ee>"
and if I change something in -trusted, there is no result
So-becose it is not permitted from my operator (needed is P-preferred),
- my SIP trunkfor my customer is out-of-work
if I change "Registration type" to something else,
then the registration string is replaced with calling nr and it is not allowed also

is tehere some other parameter, what I can change?

BR




Protocol = udp
Invite URI string 0 = sip:?@pbx.operator.ee
Invite URI string 1 =
Invite URI string 2 =
Invite URI string 3 =
Invite URI string 4 =
Invite URI string 5 =
Invite URI string 6 =
Invite URI string 7 =
From URI string 0 = sip:+3726025?@pbx.operator.ee
From URI string 1 =
From URI string 2 =
From URI string 3 =
From URI string 4 =
From URI string 5 =
From URI string 6 =
From URI string 7 =
Port = 5060
Proxy IP = 195.250.168.178
Proxy port = 5060
Accepted calls = ALL
Priority = 255
Match this =
context B-party 0 =
context B-party 1 =
context B-party 2 =
context B-party 3 =
context B-party 4 =
context B-party 5 =
context B-party 6 =
context B-party 7 =
context A-party 0 =
context A-party 1 =
context A-party 2 =
context A-party 3 =
context A-party 4 =
context A-party 5 =
context A-party 6 =
context A-party 7 =
Authentication username = sip.P00889785@pbx.operator.ee
Password = 148XXXXX
Realm = pbx.operator.ee
Registration type = Broadworks
Timer = 300
Number range = 1...1
Registration string = sip:sip.P00889785@pbx.operator.ee
Register port = 5060
Trusted privacy domain = NO_TRUSTED
SOS a subscriber number =
SOS type of number =
SOS destination number =

 

[LCE]

Hi,
Did you try to get help about sip_route command from mdsh shell?

I think that there are more values than yes/no

and maybe one of them uses "preferred" instead of "asserted" id.

I saw that last week but when I was looking for another problem.

Regards

 

[Kressmark]

Maybe this one?

sip_route -trusted
Is the remote end within a domain that uses p-asserted ids. Values are yes/no, default=no.

/mk