Am 28.12.2021 um 21:21 schrieb Antony Stone: > I would look at whatever part of the dial plan is responsible for inserting > "Sekretariat", and also check whether you have "sendrpid=yes" in sip.conf.
I find "Sekretariat" in the Ringing sent from Asterisk: Via: SIP/2.0/UDP 192.168.60.53:3072;branch=z9hG4bK-igym6msxn88p;received=192.168.60.53;rport=3072 From: "Sekretariat" <sip:74@192.168.60.1>;tag=ts2ye4krhs To: <sip:01773218409@192.168.60.1;user=phone>;tag=as32fe51ba Call-ID: 313634303731393637343630373636-ex7145moy1mt CSeq: 2 INVITE Server: Asterisk PBX 16.2.1~dfsg-1+deb10u2 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE Supported: replaces Contact: <sip:01773218409@192.168.60.1:5060> Content-Length: 0 In the users.d/74.conf (the configuration of the SIP client for "Sekretariat") I have: .... sendrpid=pai .... > However, at least you've got as far as ruling out Telekom as being the source > of the problem, which I think is good. Well, this means, that the problem is in the Asterisk... Very huge part of the infrastructure... :( Thanks Luca Bertoncello (lucab...@lucabert.de) -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
