Hello,
Running FusionPBX 5.1.0 RC1.
Symptom: A call comes in and the user presses the extension to route the call to. The end point has a Yealink desk phone and a Bria Softphone. The Desk phone rings and Bria does not. I look at the SIP messages and found this:
Before the above error, there is an INVITE with this:
I do not know how 2 "Identity" strings gets put into the INVITE message. Seems to me Bria cannot handle parsing/processing 2 "Identity" strings. I am 99% confident this is the cause of the because I had a very similar issue where I have a direct dial number that is programmed on the inbound route to go to a specific Extension and I get the same symptom: Rings the Desk phone but not the Bria Softphone. I had handled this with an "action export" rule of "sip_h_identity=" for each Direct Dial Number I have.
I suppose I could use the same or similar rule in a lower order Inbound route rule, but blanking out the "sip_h_Identity=" may not be the right thing to do since it has shaken/stir information.
Any recommendation on the best way to handle?
Thanks
DD
Running FusionPBX 5.1.0 RC1.
Symptom: A call comes in and the user presses the extension to route the call to. The end point has a Yealink desk phone and a Bria Softphone. The Desk phone rings and Bria does not. I look at the SIP messages and found this:
SIP/2.0 400 Bad Request(Multiple values in single-value header Identity)Before the above error, there is an INVITE with this:
From: "CALLER NAME" <sip:+19998887777@sip.domain.io>;tag=a310yeF06pScD
To: <sip:241@108.64.114.44:63555;rinstance=55cc27870c8fadfc>
Call-ID: fa43c5be-c91e-123c-c79a-2cea7f6151e3
CSeq: 72546486 INVITE
Identity: eyJhbGciOiJFUzI1NiIsInBwdInNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9zdGkudmVyaXpvbi5jb20vdnp3Y2VydC92enNoYWtlbi1pbnRlcm1lZGlhdGUtMDItMjAyNC5jcnQifQ.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODAwMjY2Nzc5OCJdfSwiaWF0IjoxNjk0MjAwNTQwLCJvcmlnIjp7InRuIjoiMTkxNjIxNjg2NTMifSwib3JpZ2lkIjoiRkZGRkZGRkYtRkZGRi1GRkZGLUZGRkYtMDEwMTAwMDAwMDAwIn0.5U5-3JBS8V8-NdT2UA_2lEa97NYVE7tlBcuoqSgl7NdhBUkVOuLNBo58__i-kDVISLfSLcIYlbTr5elA_JDoJQ;info=<https://sti.verizon.com/vzwcert/vzshaken-intermediate-02-2024.crt>;alg=ES256;ppt=shaken
Identity: eyJhbGciOiJFUzI1NiIsInBwdInNoYWtlbiIsInR5cCI6InBhc3Nwb3J0IiwieDV1IjoiaHR0cHM6Ly9zdGkudmVyaXpvbi5jb20vdnp3Y2VydC92enNoYWtlbi1pbnRlcm1lZGlhdGUtMDItMjAyNC5jcnQifQ.eyJhdHRlc3QiOiJBIiwiZGVzdCI6eyJ0biI6WyIxODAwMjY2Nzc5OCJdfSwiaWF0IjoxNjk0MjAwNTQwLCJvcmlnIjp7InRuIjoiMTkxNjIxNjg2NTMifSwib3JpZ2lkIjoiRkZGRkZGRkYtRkZGRi1GRkZGLUZGRkYtMDEwMTAwMDAwMDAwIn0.5U5-3JBS8V8-NdT2UA_2lEa97NYVE7tlBcuoqSgl7NdhBUkVOuLNBo58__i-kDVISLfSLcIYlbTr5elA_JDoJQ;info=<https://sti.verizon.com/vzwcert/vzshaken-intermediate-02-2024.crt>;alg=ES256;ppt=shaken
I do not know how 2 "Identity" strings gets put into the INVITE message. Seems to me Bria cannot handle parsing/processing 2 "Identity" strings. I am 99% confident this is the cause of the because I had a very similar issue where I have a direct dial number that is programmed on the inbound route to go to a specific Extension and I get the same symptom: Rings the Desk phone but not the Bria Softphone. I had handled this with an "action export" rule of "sip_h_identity=" for each Direct Dial Number I have.
I suppose I could use the same or similar rule in a lower order Inbound route rule, but blanking out the "sip_h_Identity=" may not be the right thing to do since it has shaken/stir information.
Any recommendation on the best way to handle?
Thanks
DD