Community

Content

Page tree

I've a snomD785/10.1.57.14 - and my older snom821/8.7.5.35. Both phones are in the same network, and I try to connect to the Swisscom-Box (a router, that as well includes SIP telephony over the Swisscom network); I'll call it PBX hereafter.

In a nutshell: The connection with the old Snom821 works perfectly, but the D785 doesn't connect. So I can compare a working-set and a non-working set, and I am sure that I am with credentials in a good status; the web-forms of the configured identities are structural identical - of course, except that the two phones have a distinct username.

Side-note: I can connect very well with both phones to external SIP-providers; so I'm sure both phones in a good condition.

When looking at the SIP-trace, I note that the D785 just sends UDP-packets to the PBX, but never gets a return. This brings me to the idea, that the PBX can't handle some information in the SIP-REGISTER-Requests.

Looking at the diff of the two phones, I note in the SIP-headers:

  • Max-Forwards: D785 has 70, 821 has 10 (I don't consider this as significant)
  • Contact:  <sip:220@192.168.1.63:3072> (that is the 821), Contact: <sip:221@192.168.1.64:37460;line=54fj8adz> (that is the D785)
  • Allow-Events: dialog, talk, hold, check-sync (D785), the 821 has just dialog

My questions:

  • Does someone experience a similar issue? And has an idea to deal with it?
  • Are there any settings with the D785 to not put the "line=" into the "Contact" header (if this is causing the PBX to discard the request)?
  • Are there any settings in the D785 to limit the "Allow-Events" to the 821 capabilities?

The rest of the SIP-message are structural identical.. So I don't suspect an issue there.   My gut feeling points towards the "line=" parameter.

Thank you for any hints.

Cheers Dani


profilePicture

Daniel Zuck

End user

Joined: 17.12.2022

1 Comment

  1. End user Daniel Zuck

    diff sip_821-new.txt sip_d785-new.txt

    1c1

    < Sent to udp:192.168.1.1:5060 at Dec 17 18:04:12 (926 bytes):

    ---

    > Sent to Udp:192.168.1.1:5060 from Udp:192.168.1.64:37460 at Dec 17 18:22:10.449 (966 bytes):

    4,13c4,13

    < Via: SIP/2.0/UDP 192.168.1.63:3072;branch=z9hG4bK-4xpdsz3nttoc;rport

    < From: "Swisscom" <sip:220@192.168.1.1>;tag=gwoqgp87og

    < To: "Swisscom" <sip:220@192.168.1.1>

    < Call-ID: 313635393338323038363332323634-zqimu2d7trf3

    < CSeq: 5583 REGISTER

    < Max-Forwards: 10

    < User-Agent: snom821/8.7.5.35

    < Contact: <sip:220@192.168.1.63:3072>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:832cf8fd-3d5e-465d-8d8d-000413488AD6>";audio;mobility="fixed";duplex="full";description="snom821";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

    < Allow-Events: dialog

    < X-Real-IP: 192.168.1.63

    ---

    > Via: SIP/2.0/UDP 192.168.1.64:37460;branch=z9hG4bK-nwebe04c6la6;rport

    > From: "Swisscom" <sip:221@192.168.1.1>;tag=3i44fyho4t

    > To: "Swisscom" <sip:221@192.168.1.1>

    > Call-ID: 313637313239373638383235343634-wtqysq221coi

    > CSeq: 3 REGISTER

    > Max-Forwards: 70

    > User-Agent: snomD785/10.1.57.14

    > Contact: <sip:221@192.168.1.64:37460;line=4vjcbxp0>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:526637f4-1fa4-4d09-8762-0004139A7222>";audio;mobility="fixed";duplex="full";description="snomD785";actor="principal";events="dialog";methods="INVITE,ACK,CANCEL,BYE,REFER,OPTIONS,NOTIFY,SUBSCRIBE,PRACK,MESSAGE,INFO"

    > Allow-Events: dialog, talk, hold, check-sync

    > X-Real-IP: 192.168.1.64

    15,16c15,16

    < Authorization: Digest username="phoneuser15xxx",realm="Home",nonce="xxxxxxxxxxe0056a8f1bb",uri="sip:b2b.domain",qop=auth,nc=00000001,cnonce="xxxd5032",response="9055a13032682548915eca37355b201e",algorithm=MD5

    < Expires: 0

    ---

    > Authorization: Digest username="phoneuser09xxx",realm="Home",nonce="xxxxxxxxxxx8403a0014c4",uri="b2b.domain",qop=auth,nc=00000002,cnonce="xxx5928f",response="5bfe24e6a95ed7d366cb0a5d8352da1e",algorithm=MD5

    > Expires: 0