El 26/05/14 11:05, Alex Villacís Lasso escribió:
My current working theory is that the Record-Route headers are incorrect in the
original trace. The trace, as captured in the firewall, looks like this:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
38.126.208.41:5060;rport=5060;branch=b18bbcc394bb5dae4394
My current working theory is that the Record-Route headers are incorrect in the
original trace. The trace, as captured in the firewall, looks like this:
SIP/2.0 200 OK
Via: SIP/2.0/UDP
38.126.208.41:5060;rport=5060;branch=b18bbcc394bb5dae43946b12f5d5fe0e
Record-Route:
Record-Route:
The f
> "AVL" == Alex Villacís Lasso writes:
AVL> could this work if the kernel SIP modules at the firewall are
AVL> blacklisted and Kamailio is made to do all the heavy lifting itself?
There has been quite a bit of advice on various sip-related lists over
the last decade to avoid the sip conntra
El 21/05/14 11:41, Alex Villacís Lasso escribió:
El 21/05/14 10:28, Alex Villacís Lasso escribió:
El 21/05/14 00:52, Juha Heinanen escribió:
Alex Villacís Lasso writes:
I am trying to explain the situation to our carrier, but I want to
rule out possible misconfigurations on our side. Are t
El 21/05/14 10:28, Alex Villacís Lasso escribió:
El 21/05/14 00:52, Juha Heinanen escribió:
Alex Villacís Lasso writes:
I am trying to explain the situation to our carrier, but I want to
rule out possible misconfigurations on our side. Are there common
misconfigurations that produce the symp
El 21/05/14 00:52, Juha Heinanen escribió:
Alex Villacís Lasso writes:
I am trying to explain the situation to our carrier, but I want to
rule out possible misconfigurations on our side. Are there common
misconfigurations that produce the symptoms described here? Are there
any issues evident f
Alex Villacís Lasso writes:
> I am trying to explain the situation to our carrier, but I want to
> rule out possible misconfigurations on our side. Are there common
> misconfigurations that produce the symptoms described here? Are there
> any issues evident from the attached traffic?
200 ok matc
I am trying to diagnose a SIP issue between our carrier and our network. The carrier has a CARRIER_IP and a different CARRIER_MEDIA_IP, and it submits an INVITE packet to MY_PUBLIC_IP using MY_DID. The firewall at our public IP (where the attached traffic
sample was taken) redirects it to a partic
