[Spce-user] Bye not passed down

[qabane me]

Hi

Just to confirm that indeed that's exactly what it was. Took a bit of
convincing to get the interconnect partner to believe that they were
violating RFC but they saw the light.

On Sat, Sep 1, 2018 at 3:05 PM Daniel Grotti <dgrotti at sipwise.com> wrote:

> That’s ok, I’m the BYE the from headers contain the info of the one who
> sent the bye.
> So, if the bye is sent by the callee, the from and the to are swapped, the
> from is the original callee and the to is the original caller.
>
> Daniel
>
> Sent from my iPhone
>
> On 01.09.2018, at 13:01, qabane me <qabaneitsolutions at gmail.com> wrote:
>
> Ok cool so that's the part they need to fix.
>
> Is the fact that they actually change the from-tag as well ok otherwise?
> or am I mistaken with that?
>
> Thanks
>
>
> On Sat, Sep 1, 2018 at 12:51 PM Daniel Grotti <dgrotti at sipwise.com> wrote:
>
>> As I was guessing, the bye does not have the correct RURI.
>> It must be sip: ngcp-lb at ..... the same you have in the contact of the
>> INVITE.
>>
>> Daniel
>>
>> Sent from my iPhone
>>
>> On 01.09.2018, at 12:43, qabane me <qabaneitsolutions at gmail.com> wrote:
>>
>> Hi
>> I have sent this privately.
>>
>> On Sat, Sep 1, 2018 at 11:19 AM Daniel Grotti <dgrotti at sipwise.com>
>> wrote:
>>
>>> Hi,
>>> Would be easier to see the trace or the kamailio proxy/lb log.
>>> Tag must be the same as they define the dialog.
>>> Another common issue with BYE (or ACK) is the RURI which doesn’t no
>>> contain the contact value received in the initial INVITE or 200 OK.
>>>
>>> Hard to say without a trace.
>>>
>>> Danie
>>>
>>>
>>> Sent from my iPhone
>>>
>>> > On 01.09.2018, at 02:02, qabane me <qabaneitsolutions at gmail.com>
>>> wrote:
>>> >
>>> > Hi
>>> >
>>> > We have an issue with one of our interconnects where they send a bye
>>> and sipwise does not process it. I have pinned this down to this carrier
>>> changing the From-tag - the tag in the bye is not the same as in our invite.
>>> >
>>> > Am I correct in saying that this is wrong? And that this would indeed
>>> cause the bye not to be processed?
>>> >
>>> > While I will report this to them, there is a fair chance that they
>>> will not do anything about it. When using freeswitch, I don't have an issue
>>> and the bye is processed. Is there a parameter somewhere that would make
>>> kamailio ignore the fact that the from-tag is wrong (assuming that indeed
>>> one is not allowed to change this in a dialogue, which is my understanding).
>>> >
>>> >
>>> > _______________________________________________
>>> > Spce-user mailing list
>>> > Spce-user at lists.sipwise.com
>>> > https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20180905/0c7331ad/attachment-0001.html>