SIP/2.0 400 Bad Request No matching peer

Does anyone know what might be going wrong here?

This is the only phone that is doing this. It is a Cisco 7970 and it is showing a 400 Bad Request when I show debugging in SIP. It looks like it is trying to do a PUBLISH and then Asterisk is saying that it has no matching peer.

Here are the details:

<--- SIP read from UDP: --->
PUBLISH sip:00131a592255@ SIP/2.0
Via: SIP/2.0/UDP;branch=z9hG4bK4580744c
To: <sip:00131a592255@>
From: <sip:00131a592255@>;tag=00131a5922553835d9e361a4-776fd7ea
Call-ID: 00131a59-22552f88-a17a07bc-b8efb072@
Contact: <sip:00131a592255@>
CSeq: 12167 PUBLISH
User-Agent: Cisco-CP7970G/9.4.2
Event: presence
Expires: 2147483647
Max-Forwards: 70
Content-Length: 465
Content-Type: application/pidf+xml
Content-Disposition: session;handling=required

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:e="urn:ietf:params:xml:ns:pidf:status:rpid" xmlns:ce="urn:cisco:params:xml:ns:pidf:rpid" xmlns:sc="urn:ietf:params:xml:ns:pidf:servcaps" entity="sip:00131a592255">
<tuple id="1"> <status> <basic>open</basic> </status> </tuple>
<dm:person><e:activities><ce:available/></e:activities> </dm:person>
--- (14 headers 5 lines) ---
Sending to (no NAT)
No matching peer for '00131a592255' from ''

<--- Transmitting (no NAT) to --->
SIP/2.0 400 Bad Request
Via: SIP/2.0/UDP;branch=z9hG4bK4580744c;received=
From: <sip:00131a592255@>;tag=00131a5922553835d9e361a4-776fd7ea
To: <sip:00131a592255@>;tag=as5e73d260
Call-ID: 00131a59-22552f88-a17a07bc-b8efb072@
CSeq: 12167 PUBLISH
Server: Asterisk PBX 13.12.1
Supported: replaces,timer
Content-Length: 0

Thanks in advance.

Do you have a peer named 00131a592255?

Definitely one of my thoughts. I don’t have a peer named that, but I don’t know where it’s getting that name from.

It looks like a MAC address.

I just looked at it and it is indeed the MAC address of the phone having the issue. Why would it try using that as the peername though?

It’s probably thinking it is connected to CCM where it is expected that the phone publishes information to the server based on MAC address. As chan_sip does not allow publishing even if it did match it would get rejected.

I understand. It’s interesting because that particular model is the only one that does that. The 7961,62 and the 7975 I have don’t do that. But anyway that’s not really an Asterisk problem.

Things continue to operate fine, I just didn’t want my Asterisk server to constantly be trying to do something over and over it doesn’t really want to do.