1926 (10.92) 2*SIP TK Anlage & Multi-Login

[Henri]

Hallo,

ich muss eine alte SIP TK Anlage (Lokal) austauschen, dazu wurde die neue Anlage an einem anderen VLAN installiert.
Auf dem 1926 ist der VCM aktiv. Jetzt möchte ich via Multi-Login die neue Anlage (172.21.2.35) gegen die gleiche Nummer 0049711111111 registrieren, was auch funktioniert. Allerdings bekommen ich bei einen Outbound Call diese Nachricht.

Leider habe ich mich seit längere Zeit nicht mehr mit dem VCM beschäftigt. Was mache ich denn falsch?

Danke und viele Grüße

Henri


root@Router:/Status/Voice-Call-Manager/Users
>
[SIP-Packet] 2026/02/14 10:42:20,746 [Packet]:
Receiving datagram (877 Bytes) at 172.21.2.1:5060 from 172.21.2.35:5060 using UDP (RtgTag 0):
INVITE sip:01722222222@router:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 172.21.2.35:5060;branch=z9hG4bK2ab70e3b\r\n
Max-Forwards: 70\r\n
From: "anonymous" <sip:0049711111111@router>;tag=as5cc28660\r\n
To: <sip:01722222222@router:5060>\r\n
Contact: <sip:0049711111111@172.21.2.35:5060>\r\n
Call-ID: 7f6d7c31319016384dbd6188078e3737@router\r\n
CSeq: 102 INVITE\r\n
User-Agent: STARFACE PBX\r\n
Date: Sat, 14 Feb 2026 09:42:20 GMT\r\n
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE\r\n
Supported: replaces, timer\r\n
Content-Type: application/sdp\r\n
Content-Length: 309\r\n
\r\n
v=0\r\n
o=root 27546036 27546036 IN IP4 172.21.2.35\r\n
s=STARFACE PBX\r\n
c=IN IP4 172.21.2.35\r\n
t=0 0\r\n
m=audio 11632 RTP/AVP 9 8 0 3 101\r\n
a=rtpmap:9 G722/8000\r\n
a=rtpmap:8 PCMA/8000\r\n
a=rtpmap:0 PCMU/8000\r\n
a=rtpmap:3 GSM/8000\r\n
a=rtpmap:101 telephone-event/8000\r\n
a=fmtp:101 0-16\r\n
a=ptime:20\r\n
a=maxptime:140\r\n
a=sendrecv\r\n

[Callmanager] 2026/02/14 10:42:20,747 [cCldE164Addr] : - info : cCldE164Addr::cCldE164Addr B - Number: 01722222222, Len: 11
[Callmanager] 2026/02/14 10:42:20,747 [cCldE164Addr] : - info : cCldE164Addr::cCldE164Addr B - Number: 01722222222, Len: 11
[Callmanager] 2026/02/14 10:42:20,747 [SIP-URI]: URI COMPARISON
[Callmanager] 2026/02/14 10:42:20,747 [Sip-UA] : FindBinding A -- ContactValid: yes, HasContact: yes, FromValid: yes
[Callmanager] 2026/02/14 10:42:20,747 [Sip-UA] : FindBinding -- OrigName: "0049711111111", OrigDomain: "router", ContactName: "0049711111111"
[Callmanager] 2026/02/14 10:42:20,747 [Registration Registry]: Registration Registry: FindRegistration A -- Name: "0049711111111", Domain: "router", Contact: "0049711111111", PPI: "", PAI: ""
[Callmanager] 2026/02/14 10:42:20,747 [Registration Registry]: Registration Registry: FindRegistration -- RegName: "0049711111111", RegDomain: "router", IsTrunk: no
[Callmanager] 2026/02/14 10:42:20,747 [Registration Registry]: FindRegistration --> It's a match(1)!
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding A -- Find Uri: <sip:0049711111111@172.21.2.35:5060>
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding -- Find PAI-Uri:
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding -- Find PPI-Uri:
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding -- isTrunkUser: no, Binding Uri: <sip:0049711111111@172.21.5.80:5060;transport=UDP>
[Callmanager] 2026/02/14 10:42:20,747 [SIP-URI]: URI COMPARISON
[Callmanager] 2026/02/14 10:42:20,747 [SIP-URI]: Wrong Domain!!! - Uri1-Domain: 172.21.5.80, Uri2-Domain: 172.21.2.35
[Callmanager] 2026/02/14 10:42:20,747 [Sip-UA] : FindBinding -- trying username of originator to find binding since search for contact URI name was not successful
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding A -- Find Uri: <sip:0049711111111@172.21.2.35:5060>
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding -- Find PAI-Uri:
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding -- Find PPI-Uri:
[Callmanager] 2026/02/14 10:42:20,747 [SIP Registration]: 0049711111111@router: SIP Registration: FindBinding -- isTrunkUser: no, Binding Uri: <sip:0049711111111@172.21.5.80:5060;transport=UDP>
[Callmanager] 2026/02/14 10:42:20,747 [SIP-URI]: URI COMPARISON
[Callmanager] 2026/02/14 10:42:20,747 [SIP-URI]: Wrong Domain!!! - Uri1-Domain: 172.21.5.80, Uri2-Domain: 172.21.2.35
[Callmanager] 2026/02/14 10:42:20,747 [Sip-UA] : FindBinding -- no respective binding found
[Callmanager] 2026/02/14 10:42:20,747 [Sip-UA] : - info : Reject, user (binding) not found
[Callmanager] 2026/02/14 10:42:20,747 [SIP]: ResponseToVia: No or empty "received" and/or "rport" Via parameter! Are you responding to a SIP response?
[SIP-Packet] 2026/02/14 10:42:20,747 [Packet]:
Sending datagram (456 Bytes) from 172.21.2.1:5060 to 172.21.2.35:5060 using UDP (RtgTag 0):
SIP/2.0 404 Not Found\r\n
Via: SIP/2.0/UDP 172.21.2.35:5060;branch=z9hG4bK2ab70e3b;received=172.21.2.35\r\n
From: "anonymous"<sip:0049711111111@router>;tag=as5cc28660\r\n
To: <sip:01722222222@router>\r\n
Call-ID: 7f6d7c31319016384dbd6188078e3737@router\r\n
CSeq: 102 INVITE\r\n
User-Agent: LANCOM 1926VAG-5G 10.92.0227\r\n
Server: Lancom\r\n
Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS, PRACK, UPDATE, SUBSCRIBE, INFO\r\n
Supported: timer\r\n
Content-Length: 0\r\n
\r\n

[SIP-Packet] 2026/02/14 10:42:20,750 [Packet]:
Receiving datagram (372 Bytes) at 172.21.2.1:5060 from 172.21.2.35:5060 using UDP (RtgTag 0):
ACK sip:01722222222@router:5060 SIP/2.0\r\n
Via: SIP/2.0/UDP 172.21.2.35:5060;branch=z9hG4bK2ab70e3b\r\n
Max-Forwards: 70\r\n
From: "anonymous" <sip:0049711111111@router>;tag=as5cc28660\r\n
To: <sip:01722222222@router:5060>\r\n
Contact: <sip:0049711111111@172.21.2.35:5060>\r\n
Call-ID: 7f6d7c31319016384dbd6188078e3737@router\r\n
CSeq: 102 ACK\r\n
User-Agent: STARFACE PBX\r\n
Content-Length: 0\r\n
\r\n

[tobiasr]

Ziemlich genau an der Meldung bin ich auch mal verzweifelt. Solange, bis die Telefonanlage einfach nie einen Amtsanschluss bekommen hat. Wird eh nur intern benötigt.

Welche Parameter hast du in der TK-Anlage GENAU eingetragen? Insbesondere bezüglich 'Domain' und welche Anlage ist es genau?

[Henri]

Habe "force local auth." ausgeschaltet, jetzt funktioniert es.

Danke

Henri