On Tuesday 28 December 2021 at 20:39:37, Luca Bertoncello wrote:> After about 6 seconds I get from the Telekom: > > Via: SIP/2.0/UDP > 87.191.224.158:5060;received=87.191.224.158;rport=5060;branch=z9hG4bKPj43be > 873a-cf55-4348-8867-5c2bb97bd76a > To: <sip:01773218409 at tel.t-online.de>; > tag=h7g4Esbg_p65544t1640719676m169304c9321s1_3514393582-932943693 > From: > <sip:03529529874 at tel.t-online.de>;tag=4781eb96-b155-421e-8206-593d44c9f7c4 > Call-ID: 478ba582-946c-46ac-984d-6f1835e3391b > CSeq: 15716 INVITE > Contact: <sip:sgc_c at 217.0.27.161;transport=udp> > Record-Route: <sip:217.0.27.161;transport=udp;lr> > P-Early-Media: sendrecv, gated > Require: 100rel > RSeq: 2 > Content-Type: application/sdp > Content-Length: 281 > Allow: REGISTER, REFER, NOTIFY, SUBSCRIBE, PUBLISH, MESSAGE, UPDATE, > PRACK, INFO, INVITE, ACK, OPTIONS, CANCEL, BYESo, no PAID header there, and no mention of "Sekretariat" either.> Then I see Asterisk sends this to the phone: > > Via: SIP/2.0/UDP > 192.168.60.53:3072;branch=z9hG4bK-igym6msxn88p;received=192.168.60.53;rport > =3072 > From: "Sekretariat" <sip:74 at 192.168.60.1>;tag=ts2ye4krhs > To: <sip:01773218409 at 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 at 192.168.60.1:5060> > P-Asserted-Identity: "03529529874" <sip:03529529874 at 192.168.60.1> > Content-Length: 0 > > So, it seems Asterisk receives from Deutsche Telekom _one_ "Ringing" and > sends the phone _two_ "Ringing", the second one with the > P-Asserted-Identity...Indeed.> Maybe help it to identify the problem?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. However, at least you've got as far as ruling out Telekom as being the source of the problem, which I think is good. Antony. -- I bought a book about anti-gravity. The reviews say you can't put it down. Please reply to the list; please *don't* CC me.
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 at 192.168.60.1>;tag=ts2ye4krhs To: <sip:01773218409 at 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 at 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 (lucabert at lucabert.de)
On 28.12.21 at 21:21 Antony Stone wrote:> On Tuesday 28 December 2021 at 20:39:37, Luca Bertoncello wrote:[...]>> Then I see Asterisk sends this to the phone: >> >> Via: SIP/2.0/UDP >> 192.168.60.53:3072;branch=z9hG4bK-igym6msxn88p;received=192.168.60.53;rport >> =3072 >> From: "Sekretariat" <sip:74 at 192.168.60.1>;tag=ts2ye4krhs >> To: <sip:01773218409 at 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 at 192.168.60.1:5060> >> P-Asserted-Identity: "03529529874" <sip:03529529874 at 192.168.60.1> >> Content-Length: 0 >> >> So, it seems Asterisk receives from Deutsche Telekom _one_ "Ringing" and >> sends the phone _two_ "Ringing", the second one with the >> P-Asserted-Identity... > > Indeed. > >> Maybe help it to identify the problem? > > 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.Well, I can see a much more strange behavior here in Asterisk 18.x / pjsip. On outbound calls, the 180 and 200 Ok packages sent from asterisk to the internal caller contain a RPID or PAI header like this one: Remote-Party-ID: "CID:+49..(own external number)" <sip:(dialed number)@192.168.136.20;user=phone>;party=called;privacy=off;screen=no It contains a mix of both, the own external number and the number initially dialed by the caller. I consider this pretty odd. The dialplan is generated by FreePBX. My internal phone ignores the RPID completely and from the PAI, it presents the own external number (and the dialed number isn't shown any more). "Solution" is to disable rpid or pai completely. Thanks Michael
Am 28.12.2021 um 21:21 schrieb Antony Stone: Hi> However, at least you've got as far as ruling out Telekom as being the source > of the problem, which I think is good.So, I setted: sendrpid=rpid instead of: sendrpid=pai and now it seems to work. The called number does not change anymore. Last very strange problem is, that the list of missed calls on the phone is always empty... But it can be a problem of the phone hisself... Maybe has someone an idea? The phone is a Snom 821-SIP Thanks and happy new year! Luca Bertoncello (lucabert at lucabert.de)