sip - How Kamailio transformations work? -


why kamailio isn't set all headers properly?

kamailio route excerpt:

route[pstn] {     ...     # set user     $fu = "+34687xxxxxx";      # set info headers     append_hf("remote-party-id: <$fu>\r\n");     append_hf("p-preferred-identity: <$fu>\r\n");     ... } 

ngrep result of invite:

u xxx.xxx.xxx.xxx:5060 -> xxx.xxx.xxx.xxx:5060 invite sip:+34951xxxxxx@xxx.xxx.xxx.xxx;transport=udp sip/2.0. record-route: <sip:xxx.xxx.xxx.xxx;lr>. via: sip/2.0/udp xxx.xxx.xxx.xxx;branch=z9hg4bke235.4728a380ee70fc55cc0cecbb7919bee5.0. via: sip/2.0/udp xxx.xxx.xxx.xxx:38293;rport=38293;branch=z9hg4bk-d8754z-34c6ee584c5f95cd-1---d8754z-. max-forwards: 69. contact: <sip:javier.valencia@xxx.xxx.xxx.xxx:38293;transport=udp>. to: <sip:951xxxxxx@xxx.xxx.xxx.xxx;transport=udp>. from: <sip:+34687xxxxxx@xxx.xxx.xxx.xxx;transport=udp>;tag=666b4350. call-id: mgy2odbkzjq4owi3zwfmn2zinwqwyzhizwi5zmrkyzk.. cseq: 2 invite. allow: invite, ack, cancel, bye, notify, refer, message, options, info, subscribe. content-type: application/sdp. supported: replaces, norefersub, extended-refer, timer, x-cisco-serviceuri. allow-events: presence, kpml. content-length: 163. remote-party-id: <sip:javier.valencia@xxx.xxx.xxx.xxx;transport=udp>. p-preferred-identity: <sip:javier.valencia@xxx.xxx.xxx.xxx;transport=udp>. user-agent: voiper.es. . v=0. o=z 0 0 in ip4 xxx.xxx.xxx.xxx. s=z. c=in ip4 xxx.xxx.xxx.xxx. t=0 0. m=audio 8000 rtp/avp 8 101. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-15. a=sendrecv. 

the from header set properly, remote-party-id , p-preferred-identity isn't set properly.

i'm running kamailio 4.2.0 on debian 8.

$fu specific user in kamailio syntax. can try putting local variable , using purpose mentioned ?


Comments

Popular posts from this blog

c# - Validate object ID from GET to POST -

node.js - Custom Model Validator SailsJS -

php - Find a regex to take part of Email -