No matching Contact in positive reply : Gateway Registrartion

1

I am trying to register to an Auth based gateway , but I get the following error
“no matching Contact in positive reply”. I have configured the account under Equipment>Registrations

On my sip trace , my Auth gateway gives me a 200 OK but Yeti sends another register attempt.

See Trace below image

Capture
Capture1918×959 75.3 KB

2
  • it is pretty hard debug anything by image. Could you share .pcap trace?
  • Usually no matching Contact in positive reply happened when 200OK response doesn’t contain same Contact value as was sent in REGISTER(as required by RFC). So 200OK is not enough for successful registrations - 200OK should also contains right Contact value.
3

@dmitry.s

I have checked the contact filed reply from my trunk provider. is it possible to disable contact requirement on yeti?

Find the trace below

REGISTER xxxxxxxxxxxxxxxxx;transport=TCP SIP/2.0.
Via: SIP/2.0/TCP 10.37.137.236:5061;branch=z9hG4bK0NjOaah8;rport.
From: sip:xxxxxxxxxxxx@xxxxxxxxxxxxxxx;tag=8-76802E16-5E1F38E100038A96-BA9C7700.
To: sip:xxxxxxxxxxxx@talk2.ai.co.zw.
CSeq: 204 REGISTER.
Call-ID: 8-1C3FA258-5E1F38E20001429A-B8169700.
Max-Forwards: 70.
Expires: 10000.
Authorization: Digest username=“xxxxxxxxxxx”, realm=“xxxxxxxxxxxxxx”, nonce=“5e1f3ac80001820118dee23670d493eca81d70807eddf15f”, uri=“sip:xxxxxx;transport=TCP”, response=“cb60711610b34d84f2d21a07cab00fa9”, algorithm=MD5.
User-Agent: SBC 1.8.34-5.
Contact: sip:xxxxxxxxxxxxx@xxxxxxxxxxx;transport=tcp.
Content-Length: 0.
.

T 209.97.142.21:5060 -> 10.37.137.236:5061 [AP]
SIP/2.0 401 Unauthorized.
Via: SIP/2.0/TCP 10.37.137.236:5061;received=xxxxxxxxxxxxxxx;branch=z9hG4bK0NjOaah8;rport=5061.
From: sip:xxxxxxxxxxxxxxxx@xxxxxxxxxxxxx;tag=8-76802E16-5E1F38E100038A96-BA9C7700.
To: sip:xxxxxxxxxxxxxx@xxxxxxxxxxxxxxxxx;tag=9f79.4946d6edfcb7c34b975ee6842330eb3d.
CSeq: 204 REGISTER.
Call-ID: 8-1C3FA258-5E1F38E20001429A-B8169700.
WWW-Authenticate: Digest realm=“xxxxxxxxx”, nonce=“5e1f3ace0001824aa78f4c605820c752c49c36e841a55bef”, stale=true.
Server: OpenSIPS (3.0.1 (x86_64/linux)).
Content-Length: 0.
.

REGISTER sip:xxxxxxxxx;transport=TCP SIP/2.0.
Via: SIP/2.0/TCP xxxxxxxxxxxxx:5061;branch=z9hG4bKUl1bZaTL;rport.
From: sip:xxxxxxxxxx@xxxxxxxxx;tag=8-76802E16-5E1F38E100038A96-BA9C7700.
To: sip:xxxxxxxxxx@xxxxxxx.
CSeq: 205 REGISTER.
Call-ID: 8-1C3FA258-5E1F38E20001429A-B8169700.
Max-Forwards: 70.
Expires: 10000.
Authorization: Digest username=“xxxxxxxx”, realm=“xxxxxxxx”, nonce=“5e1f3ace0001824aa78f4c605820c752c49c36e841a55bef”, uri=“sip:talk2.ai.co.zw;transport=TCP”, response=“edbcfdd48b7802d1ad96f009eff0f4bc”, algorithm=MD5.
User-Agent: SBC 1.8.34-5.
Contact: sip:xxxxxxxxxxxx@xxxxxxxxx;transport=tcp.
Content-Length: 0.
.

SIP/2.0 200 OK.
Via: SIP/2.0/TCP xxxxxxxxxxxx:5061;received=91.205.175.140;branch=z9hG4bKUl1bZaTL;rport=5061.
From: sip:xxxxxxxx@xxxxxxxxx;tag=8-76802E16-5E1F38E100038A96-BA9C7700.
To: sip:xxxxxxx@xxxxxxxx;tag=9f79.02c6f133cf0ad5364cddef2257f8341b.
CSeq: 205 REGISTER.
Call-ID: 8-1C3FA258-5E1F38E20001429A-B8169700.
Contact: sip:xxxxxxx@xxxxxxxx:5061;transport=tcp;expires=350.
Server: OpenSIPS (3.0.1 (x86_64/linux)).
Content-Length: 0.

4

Have you asked your provider why they respond:

Contact: sip:08644888999@91.205.175.140:5061;transport=tcp;expires=350

when you requested:

Contact: sip:08644888999@91.205.175.140;transport=tcp

?

5

Thanks, I missed that part: I just added the port to my contact string in yeti.

This issue has been solved