Hi,
On 08/20/2011 08:37 PM, Skyler wrote:
Hi Vlada,
SEMS is running on 5080, but where is the INVITE that is received by
SEMS (127.0.0.1:xyz -> 127.0.0.1:5080)? Are you sure that From HF has
not been modified somewhere before?
You were correct, the missing INVITE from kamailio to SEMS shows that
the From HF was indeed modified by kamailio config prior to sending to
SEMS. So this is not a problem with SEMS config at all. I will now look
into kamailio config to check "RURI=$r", "From=$f", "To=$t" as
suggested.
this "RURI=$r" etc. are configuration parameters for SEMS, not kamailio.
Thank you very much for your help, I have learned now to pay closer
attention to traces before posting :)
no problem at all ;-)
-Vlada B.
S.
U 2011/08/20 14:20:31.790504 127.0.0.1:5062 -> 127.0.0.1:5080
INVITE sip:b2b-16048881212@DEVICE_IP:5060 SIP/2.0.
Record-Route:
<sip:127.0.0.1:5062;lr=on;ftag=as6c6ae522;did=982.3dde1881;vsf=SlZ3eUh2S29GYmhXTExOWVUzZk1KVnd5SHZLb0ZiaFdMTE4->.
Record-Route:<sip:127.0.0.1;r2=on;lr=on;ftag=as6c6ae522>.
Record-Route:<sip:SPCE_IP;r2=on;lr=on;ftag=as6c6ae522>.
Via: SIP/2.0/UDP
127.0.0.1:5062;branch=z9hG4bK8513.86716cf040064692b88f0029bb3fc8c7.0.
Route:<sip:[email protected]:5060;lr>.
Via: SIP/2.0/UDP 127.0.0.1;rport=5060;branch=z9hG4bK8513.9dd8fe07.0.
v: SIP/2.0/UDP ASTERISK_IP:5060;branch=z9hG4bK3bb6032e;rport=5060.
Max-Forwards: 68.
f: "2725846431"<sip:2725846431@ASTERISK_IP>;tag=as6c6ae522.
t:<sip:16048881212@SPCE_IP>.
m:<sip:2725846431@ASTERISK_IP>.
i: 7fc3bcbf5bf0e6ef19907a8d5dc0e179@ASTERISK_IP.
CSeq: 102 INVITE.
User-Agent: voxcentral.
Date: Sat, 20 Aug 2011 18:20:31 GMT.
x: 600.
Min-SE: 90.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,
INFO.
k: replaces, timer.
c: application/sdp.
l: 544.
P-Asserted-Identity:<sip:2725846431@ASTERISK_IP>.
P-R-Uri: sip:16048881212@DEVICE_IP:5060.
P-D-Uri: sip:[email protected]:5060;lr
.
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
