- sr-users - kamailio.org

BLF on different IPs/domains
by Phil Lavin 12 Feb '16

12 Feb '16

Hi all, A different BLF query to my other one so creating another thread. We've tried to have a BLF client SUBSCRIBE using a secondary IP on Kamailio. It is not sent a NOTIFY, but a client which has done a SUBSCRIBE using the primary IP is. If we route the problematic client such that it connects to the primary IP, it too is sent a NOTIFY. Looking at the query that is done on the database when a call is made to 441164969988 it is as follows: select `callid`,`to_tag`,`from_tag` from `active_watchers` where `presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog' Where 185.28.212.118 is the primary IP. In reality, it should be doing an additional query for anything considered `myself`. i.e. select `callid`,`to_tag`,`from_tag` from `active_watchers` where `presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog' I've been scouring the docs for a way to add additional IPs and/or domains for the purpose of querying active_watchers but I can't see anything relevant. What's the process here? Thanks Phil

2 3

kamailio xmpp gateway configuration issue
by kevin hifx 12 Feb '16

12 Feb '16

Dear friends, I am facing an issue, when trying to configure xmpp gateway between kamailio and ejabbred xmpp server. I have followed the steps mention in this web site: http://www.kamailio.org/docs/modules/4.1.x/modules/xmpp.html The kamailio service is running but in the log file it show that xmpp connection failed. "*Feb 5 11:32:33 sip-xmpp-server /usr/sbin/kamailio[646]: ERROR: xmpp [network.c:122]: net_connect(): connect() failed: Connection refused* " (Both kamailio and ejabbred installed on the same server in local network and have local DNS server) I have added following entries in the kamailio configuration file. I am only mentioning the xmpp section. " ####### Global Parameters ######### alias=sip-xmpp.kevin.org ####### Modules Section ######## #!ifdef WITH_MYSQL loadmodule "db_mysql.so" #!endif loadmodule "mi_fifo.so" loadmodule "kex.so" loadmodule "corex.so" loadmodule "tm.so" loadmodule "tmx.so" loadmodule "sl.so" loadmodule "rr.so" loadmodule "pv.so" loadmodule "maxfwd.so" loadmodule "usrloc.so" loadmodule "registrar.so" loadmodule "textops.so" loadmodule "siputils.so" loadmodule "xlog.so" loadmodule "sanity.so" loadmodule "ctl.so" loadmodule "cfg_rpc.so" loadmodule "mi_rpc.so" loadmodule "acc.so" # XMPP loadmodule "xmpp.so" # ----------------- setting module-specific parameters --------------- modparam("mi_fifo", "fifo_name", "/var/run/kamailio/kamailio_fifo") modparam("rr", "enable_full_lr", 1) # XMPP modparam("xmpp", "domain_separator", "*") modparam("xmpp", "gateway_domain", "sip-xmpp.kevin.org") modparam("xmpp", "xmpp_domain", "xmpp-sip.kevin.org") modparam("xmpp", "xmpp_host", "xmpp.kevin.org") ###############XMPP # initial sanity checks -- messages with # max_forwards==0, or excessively long requests if (!mf_process_maxfwd_header("10")) { sl_send_reply("483","Too Many Hops"); exit; }; if (msg:len >= 2048 ) { sl_send_reply("513", "Message too big"); exit; }; ### absorb retransmissions ### if (!t_newtran()) { sl_reply_error(); return; } if (method == "MESSAGE") { log("*** xmpp-handled MESSAGE message.\n"); if (xmpp_send_message()) { t_reply("200", "Accepted"); } else { t_reply("404", "Not found"); } return; } log("*** xmpp: unhandled message type\n"); t_reply("503", "Service unavailable"); return; ############### " could you please help me solve this issue. Thank you kevin

2 5

Only Cassandra, Possible?
by Barış Şekerciler 12 Feb '16

12 Feb '16

Hello, I want to use only Cassandra DB for Kamailio. Is this possible? If it yes, how can I do that? For example, if I replace the DBENGINE as DB_CASSANDRA can I use it like this? Thank you. Regards.

2 3

Kamailio TLS
by Kethzer Docteur 12 Feb '16

12 Feb '16

Im trying to enable Kamailio TLS but the configuration is not running at all when I cahnge it liike this as follow. Kamailio 3.3 ubuntu 12.04 LTS #!define WITH_TLS #!ifdef WITH_TLS enable_tls=yes #!endif #!ifdef WITH_TLS loadmodule "tls.so" #!endif #!ifdef WITH_TLS # ----- tls params ----- modparam("tls", "config", "/etc/kamailio/tls.cfg") #!endif Please help -- Kethzer Docteur

4 3

Negative return codes from functions
by Phil Lavin 11 Feb '16

11 Feb '16

Hi all, Just a sanity check, really. Does Kamailio consider negative response codes to be false? For example, should the following log execute? if (!foo()) { # Returns -2 x_log("Foo is false"); } The reason for asking here is that I'm implementing flood protection using pike, based off the kamailio.cfg that ships with v4.3. The logic is thus: if (!pike_check_req()) { # Do blocking } However pike_check_req only returns -1 or -2 in the case of failure, never 0. The blocking code is, thus, never executed. Changing to explicitly check for != 1 works correctly. Am I missing something here or is the example kamailio.cfg incorrect? Cheers

2 3

Kamailio 4.2.6 crash
by Igor Potjevlesch 11 Feb '16

11 Feb '16

Hello, I have seen couple of crashes since yesterday. I copy/paste the last "bt full": Program terminated with signal 11, Segmentation fault. #0 0x0000000000619694 in fm_extract_free (qm=0x7fcdf8780000, frag=0x7fcdf8a62c78) at mem/f_malloc.c:206 206 *pf= (gdb) bt full #0 0x0000000000619694 in fm_extract_free (qm=0x7fcdf8780000, frag=0x7fcdf8a62c78) at mem/f_malloc.c:206 pf = 0x6576203b50555349 hash = 2097 #1 0x000000000061ad68 in fm_malloc (qm=0x7fcdf8780000, size=1104, file=0x7fce0f081a7b "tm: t_msgbuilder.c", func=0x7fce0f0860a0 "build_local_reparse", line=369) at mem/f_malloc.c:490 f = 0x7fcdf8780b08 frag = 0x7fcdf8a62c78 hash = 156 __FUNCTION__ = "fm_malloc" #2 0x00007fce0f011fa9 in _shm_malloc (size=1099, file=0x7fce0f081a7b "tm: t_msgbuilder.c", function=0x7fce0f0860a0 "build_local_reparse", line=369) at ../../mem/shm_mem.h:208 p = 0x6 #3 0x00007fce0f01920e in build_local_reparse (Trans=0x7fcdf8a5e2f0, branch=0, len=0x7fff00c32fbc, method=0x7fce0f087a25 "ACK", method_len=3, to=0x7fff00c32d90, reason=0x0) at t_msgbuilder.c:369 invite_buf = 0x7fcdf8a62868 "INVITE sip:<CALLED>@goren SIP/2.0\r\nRecord-Route: <sip:A.B.C5.60;lr;did=5b1.3112>\r\nCSeq: 1 INVITE\r\nCall-ID: 3da8-469-1111201513435-JANGO-1-A.B.C_leg2\r\nFrom: <sip:<CALLING>@<HOST_FROM>>;"... invite_buf_end = 0x7fcdf8a62c70 "" cancel_buf = 0x415440 "1\355I\211\321^H\211\342H\203\344\360PTI\307\300\300\363m" s = 0x7fcdf8a62868 "INVITE sip:<CALLED>@goren SIP/2.0\r\nRecord-Route: <sip:A.B.C5.60;lr;did=5b1.3112>\r\nCSeq: 1 INVITE\r\nCall-ID: 3da8-469-1111201513435-JANGO-1-A.B.C_leg2\r\nFrom: <sip:<CALLING>@<HOST_FROM>>;"... s1 = 0x0 d = 0x10703ab0 <Address 0x10703ab0 out of bounds> invite_len = 1032 hf_type = 2540 first_via = 0 to_len = 67 cancel_buf_len = 1099 reason_len = 0 code_len = 0 reas1 = 0x0 reas_last = 0x0 hdr = 0xa7294e __FUNCTION__ = "build_local_reparse" #4 0x00007fce0f02e58b in build_ack (rpl=0x7fce107038b8, trans=0x7fcdf8a5e2f0, branch=0, ret_len=0x7fff00c32fbc) at t_reply.c:439 to = {s = 0xa728f6 "To: <sip:+<CALLED>@A.B.C5.60:5060>;tag=3658827875-928685\r\nContent-Length: 0\r\n\r\n", len = 67} __FUNCTION__ = "build_ack" #5 0x00007fce0f03b3ca in reply_received (p_msg=0x7fce107038b8) at t_reply.c:2253 msg_status = 488 last_uac_status = 100 ack = 0x7fce10588010 "\001" ack_len = 0 branch = 0 reply_status = 274235864 onreply_route = 1 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 10955086}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 10955086}}}} uac = 0x7fcdf8a5e458 t = 0x7fcdf8a5e2f0 lack_dst = {send_sock = 0x13a948, to = {s = {sa_family = 10306, sa_data = "\247\000\000\000\000\000(\r\030\000\000\000\000"}, sin = {sin_family = 10306, sin_port = 167, sin_addr = {s_addr = 0}, sin_zero = "(\r\030\000\000\000\000"}, sin6 = {sin6_family = 10306, sin6_port = 167, sin6_flowinfo = 0, sin6_addr = { __in6_u = {__u6_addr8 = "(\r\030\000\000\000\000\000\270|^\020\316\177\000", __u6_addr16 = {3368, 24, 0, 0, 31928, 4190, 32718, 0}, __u6_addr32 = {1576232, 0, 274627768, 32718}}}, sin6_scope_id = 93}}, id = 0, proto = -72 '\270', send_flags = {f = 106 'j', blst_imask = 94 '^'}} backup_user_from = 0x758a50 backup_user_to = 0x415440 backup_domain_from = 0x300c337e0 backup_domain_to = 0x0 backup_uri_from = 0x7fce10703ab0 backup_uri_to = 0x7fff00c330d0 backup_xavps = 0x628478 replies_locked = 0 branch_ret = 0 prev_branch = 275790040 blst_503_timeout = 32718 hf = 0x18e00c33060 onsend_params = {req = 0x7fff00c32f50, rpl = 0x47deb8, param = 0x0, code = 274623280, flags = 32718, branch = 0, t_rbuf = 0xa7294e, dst = 0xa727e1, send_buf = { s = 0x7fff00c33010 "\320\060", <incomplete sequence \303>, len = 6402299}} ctx = {rec_lev = 7715456, run_flags = 0, last_retcode = 7704068, jmp_env = {{__jmpbuf = {232, 140523014225936, 140523014226728, 140523014618240, 29, 0, 140523015781040, 4281408}, __mask_was_saved = 12793824, __saved_mask = {__val = {0, 140733206179856, 6439748, 140733206179616, 140523001001690, 140733206179584, 0, 67108864, 65537912, 1288288, 1570952, 1576232, 8, 94, 0, 1473240891392}}}}} __FUNCTION__ = "reply_received" #6 0x000000000048cc3a in do_forward_reply (msg=0x7fce107038b8, mode=0) at forward.c:783 new_buf = 0x0 dst = {send_sock = 0x0, to = {s = {sa_family = 0, sa_data = '\000' <repeats 13 times>}, sin = {sin_family = 0, sin_port = 0, sin_addr = {s_addr = 0}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 0, sin6_port = 0, sin6_flowinfo = 0, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, id = 0, proto = 0 '\000', send_flags = {f = 0 '\000', blst_imask = 0 '\000'}} new_len = 1 r = 0 ip = {af = 12792240, len = 32767, u = {addrl = {6466393, 280}, addr32 = {6466393, 0, 280, 0}, addr16 = {43865, 98, 0, 0, 280, 0, 0, 0}, addr = "Y\253b\000\000\000\000\000\030\001\000\000\000\000\000"}} s = 0x410004 "" len = 0 __FUNCTION__ = "do_forward_reply" #7 0x000000000048e27d in forward_reply (msg=0x7fce107038b8) at forward.c:885 ---Type <return> to continue, or q <return> to quit--- No locals. #8 0x0000000000509c9c in receive_msg ( buf=0xa727c0 "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"..., len=398, rcv_info=0x7fff00c333b0) at receive.c:275 msg = 0x7fce107038b8 ctx = {rec_lev = 10237056, run_flags = 0, last_retcode = 0, jmp_env = {{__jmpbuf = {0, 0, 0, 272136986608, 1812476198913, 0, 272145363728, 272145384176}, __mask_was_saved = 0, __saved_mask = {__val = {140523014366192, 140733206180688, 1, 140522613671152, 272137013029, 50195, 1024, 4307759872, 140522613671152, 140733206180608, 6299381, 140733206180896, 140522613671152, 81, 6299509, 140733206180976}}}}} ret = 12792656 inb = { s = 0xa727c0 "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"..., len = 398} __FUNCTION__ = "receive_msg" #9 0x0000000000608f02 in udp_rcv_loop () at udp_server.c:521 len = 398 buf = "SIP/2.0 488 Not Acceptable Here\r\nVia: SIP/2.0/UDP A.B.C5.60;rport=5060;branch=z9hG4bKce12.98a05ce27e0243c4d775920d81e7ce82.0\r \nVia: SIP/2.0/UDP <HOST_FROM>;branch=z9hG4bK.5667f6e0\r\nFrom: <sip:332"... tmp = 0x3f60c4067a <Address 0x3f60c4067a out of bounds> from = 0x7fce105e7920 fromlen = 16 ri = {src_ip = {af = 2, len = 4, u = {addrl = {151524537, 0}, addr32 = {151524537, 0, 0, 0}, addr16 = {5305, 2312, 0, 0, 0, 0, 0, 0}, addr = "\271\024\b\t", '\000' <repeats 11 times>}}, dst_ip = {af = 2, len = 4, u = {addrl = {1016190299, 0}, addr32 = {1016190299, 0, 0, 0}, addr16 = {54619, 15505, 0, 0, 0, 0, 0, 0}, addr = "[Õ<", '\000' <repeats 11 times>}}, src_port = 5060, dst_port = 5060, proto_reserved1 = 0, proto_reserved2 = 0, src_su = { s = {sa_family = 2, sa_data = "\023Ä¹\024\b\t\000\000\000\000\000\000\000"}, sin = {sin_family = 2, sin_port = 50195, sin_addr = {s_addr = 151524537}, sin_zero = "\000\000\000\000\000\000\000"}, sin6 = {sin6_family = 2, sin6_port = 50195, sin6_flowinfo = 151524537, sin6_addr = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, sin6_scope_id = 0}}, bind_address = 0x7fce105aa2b0, proto = 1 '\001'} __FUNCTION__ = "udp_rcv_loop" #10 0x00000000004a6d9b in main_loop () at main.c:1629 i = 0 pid = 0 si = 0x7fce105aa2b0 si_desc = "udp receiver child=0 sock=A.B.C5.60:5060\000\177\000\000 5\303\000\377\177\000\000\003zN\000\000\000\000\000\016\b\000\000\377\177\00 0\000\260\204x\370\315\177\000\000\000\000\000\020\004\000\000\000\260\204x\ 370\315\177\000\000@TA\000\000\000\000\000\340\067\303\000\001\000\000\000p5 \303\000\377\177\000\000\246zN\000\000\000\000" nrprocs = 8 __FUNCTION__ = "main_loop" #11 0x00000000004acedf in main (argc=7, argv=0x7fff00c337e8) at main.c:2581 cfg_stream = 0xac7010 c = -1 r = 0 tmp = 0x7fff00c34f70 "" tmp_len = 32767 port = 12793534 proto = 0 options = 0x6ff8f8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 3913881212 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x40d11c p = 0xc2 <Address 0xc2 out of bounds> __FUNCTION__ = "main" Regards, Igor.

2 15

Reg: REGISTER request don't have username in request line
by sainath.ellendula＠wipro.com 11 Feb '16

11 Feb '16

Hi Team, Working on Kamailio setup with IMS components(P-CSCF, I-CSCF, S-CSCF). Assigned IP's: hss/server-10.0.0.9 P-CSCF-10.0.0.10 I-CSCF-10.0.0.11 S-CSCF-10.0.0.12 Here tried to send an REGISTER request from Boghe IMS client, the register request should go from P-CSCF to I-CSCF, here P-CSCF - I-CSCF communication is not happening but I could able ping. One more thing observed from logs here is REGISTER request don't have username (username is not there in request line), Execution log: 0(1338) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please find attachment of Zone file, SCSCF.xml, Diameter.xml, ICSCF.xml and tcpdump. Any changes/suggestions would be very helpful. Regards, Sainath The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 1

Terminate dialogs on [websocket:closed]
by mayamatakeshi 11 Feb '16

11 Feb '16

Hello, I am using module websocket and it works very well. However I would like to send BYE to the other end if event [websocket:closed] happens. >From the docs I can see websocket module itself doesn't provide for this. I was considering doing something like this: - use module htable to match $si:$sp to dialogs - use event_route[dialog:start] to insert dialog info to my htable under $si:$sp of Websocket side of the call - use event_route[dialog:end] to remove dialog info from htable - use event_route[websocket:closed] to iterate over entries in the htable under key $si:$sp and call dlg_get() and dlg_bye(). Obs: in the above, there is a risk of losing some dialogs as insertion in htable cannot be done atomically, but I am fine with it as it it not expected to happen as WebSocket users would only infrequently generate simultaneous calls. However before going with this, I would like to ask for other possible approaches. Regards, Takeshi

2 6

Route for BYE requests
by alexandre.anconetti＠orange.com 11 Feb '16

11 Feb '16

Hello, I would like some advice about a situation i have encountered recently. I'm using Kamailio 4.3.4 as a "proxy" : I have a media server, and to reach this server all the requests have to pass through my Kamailio server. The Kamailio server does not have to handle authentification or registration, all of that stuff is done on the media server. To do that I'm using the following route : route[REDIRECT] { if($rU == "" ) { $ru = ("sip:1.2.3.4:xxxx"); } else { $ru = ("sip:" + $rU + "@1.2.3.4:xxxx"); } } 1.2.3.4 is my media server's address. I have 2 users : an "internal" one registered on the media server, and an "external" one which is a random caller. It works fine for EXT -> Kamailio -> Media server requests but when I try to hang up with my internal user, the "BYE" request uses the following path : Internal user -> Media server -> Kamailio -> Media server instead of : Internal user -> Media server -> Kamailio -> External user. Obviously it is because of the REDIRECT route which send back the "BYE" request to the media server, when it should sends that request to the external user. So, how should I modify that route to do what I want ? Maybe should I create a second route ? Any answer will be appreciated :) Best regards, Alexandre _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.

2 1

kamctl ul add...<path>
by kssyrr 10 Feb '16

10 Feb '16

1 0

RTCWeb Breaker question
by SamyGo 10 Feb '16

10 Feb '16

Hi All, reference to this link: https://www.kamailio.org/wiki/devel/rtcweb_breaker#scenarios I want to know if the module to communicate with RTCWeb Breaker is available or it was just a proposal and no more under consideration. I have webrtc clients registered to Kamailio but due to lack of (scalable/efficient) transcoding capabilities they can not make video calls to Video IP-Phones. I tried using webrtc2sip from doubango telecom and it actually enabled me to achieve the goal, the problem with that case is webrtc2sip is working with sipml5 client and there is not a big list of WebRTC clients that work with it. If I can achieve the referred rtc_web_breaker architecture then I believe a lot of webRTC clients will be able to integrate with my setup. Thanks, Regards, Sammy

2 4

Kamailio SST and Dialog module workings
by Jason Penton 10 Feb '16

10 Feb '16

Hi Kamailio users and Devs. I am interested to know if any of you are using SST module with DIALOG module and sharing the timeout avp between the two - expecting the call to be torn down if no in-dialog requests are processed. If you are using it, is it working as you expect? To me it seems that the timers in the dialog module will never be updated by any in-dialog requests. I just wanted to check before I start looking at fixing... perhaps I am missing something. Cheers Jason

2 2

Permission module about from_pattern
by Yasin CANER 10 Feb '16

10 Feb '16

2 3

regular expression for fromuser
by Yasin CANER 10 Feb '16

10 Feb '16

1 0

regular expression for from_pattern
by Yasin CANER 10 Feb '16

10 Feb '16

1 0

info: dialog_ng renamed to ims_dialog
by Daniel-Constantin Mierla 09 Feb '16

09 Feb '16

Hello, based on a previous discussion on mailing lists, I just renamed the dialog_ng to ims_dialog in order to reflect better its purpose nowadays (use together with the other ims modules) and avoid confusion that it is something that includes the features of dialog module and some new stuff. Functions and params are not renamed, being anyhow overlapping a lot with dialog module, but they are not intended to be used at the same time. Perhaps some examples still need to be updated (contributions are welcome here if you identify such places). If any other issue is discovered to the ims modules, write here to get it fixed. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

1 0

Re: [SR-Users] Kamailio IMS deployment
by Franz Edler 09 Feb '16

09 Feb '16

The REGISTER request is OK. There is no username included in REGISTER request.Regarding the mismatch: do you use NATURAL on your platform? Next step should be a tracefile (tcpdump) and later a debug-log from the node which shows the problem. Von Samsung-Tablet gesendet-------- Ursprüngliche Nachricht --------Von: sainath.ellendula(a)wipro.com Datum: 2016.02.09 08:05 (GMT+01:00) An: franz.edler(a)technikum-wien.at Cc: basitstar(a)hotmail.com, sr-users(a)lists.sip-router.org Betreff: RE: Re:[SR-Users] Kamailio IMS deployment Hi Franz, Please find ping status and seems good. root@server:~# ping -c 1 hss.net1.test PING hss.net1.test (10.0.0.9) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.9): icmp_seq=1 ttl=64 time=0.017 ms --- hss.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# ping -c 1 pcscf.net1.test PING pcscf.net1.test (10.0.0.10) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.10): icmp_seq=1 ttl=64 time=0.020 ms --- pcscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.020/0.020/0.020/0.000 ms root@server:~# ping -c 1 icscf.net1.test PING icscf.net1.test (10.0.0.11) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.11): icmp_seq=1 ttl=64 time=0.018 ms --- icscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.018/0.018/0.018/0.000 ms root@server:~# ping -c 1 scscf.net1.test PING scscf.net1.test (10.0.0.12) 56(84) bytes of data. 64 bytes from server.net1.test (10.0.0.12): icmp_seq=1 ttl=64 time=0.017 ms --- scscf.net1.test ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.017/0.017/0.017/0.000 ms root@server:~# Seems Some progress happened: Tried register using Boghe IMS client and observed few errors: 0(1445) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1445) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55280) to sip:alice@net1.test, 2006cdca-0076-bacb-5010-bffa714b3cdb) 0(1445) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <7994> <REGISTER> 0(1445) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 0(1445) DEBUG: maxfwd [mf_funcs.c:85]: is_maxfwd_present(): value = 70 0(1445) DEBUG: <core> [parser/msg_parser.c:89]: get_hdr_field(): found end of header 0(1445) DEBUG: sanity [mod_sanity.c:248]: w_sanity_check(): sanity checks result: 1 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: <core> [select.c:412]: run_select(): Calling SELECT 0x7fb548dd2400 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=1 T start=0xffffffffffffffff 0(1445) DEBUG: tm [t_lookup.c:466]: t_lookup_request(): t_lookup_request: start searching: hash=65064, isACK=0 0(1445) DEBUG: tm [t_lookup.c:424]: matching_3261(): DEBUG: RFC3261 transaction matching failed 0(1445) DEBUG: tm [t_lookup.c:648]: t_lookup_request(): DEBUG: t_lookup_request: no transaction found 0(1445) DEBUG: tm [t_lookup.c:1080]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T end=(nil) 0(1445) DEBUG: sl [sl.c:280]: send_reply(): reply in stateless mode (sl) 0(1445) DEBUG: siputils [checks.c:97]: has_totag(): no totag 0(1445) DEBUG: tm [t_lookup.c:1011]: t_check_msg(): DEBUG: t_check_msg: msg id=2 global id=2 T start=(nil) 0(1445) DEBUG: tm [t_lookup.c:1086]: t_check_msg(): DEBUG: t_check_msg: T previously sought and not found 0(1445) DEBUG: ims_registrar_pcscf [save.c:273]: save_pending(): contact requesting to expire in 600000 seconds 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:155]: get_hash_slot(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:159]: get_hash_slot(): Returning hash slot: [167] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:465]: get_pcontact(): Searching for contact in P-CSCF usrloc [sip:alice@10.0.0.8:55280;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:183]: get_aor_hash(): using host for hash [10.0.0.8] 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:187]: get_aor_hash(): Returning hash slot: [1662767783] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:483]: get_pcontact(): Comparing needle user@host:port [alice@10.0.0.8:55280] and contact_user@contact_host:port [alice@10.0.0.8:51219] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:494]: get_pcontact(): Searching for [sip:alice@10.0.0.8:55280;transport=udp] and comparing to [sip:alice@10.0.0.8:51219;transport=udp] 0(1445) DEBUG: ims_usrloc_pcscf [udomain.c:553]: get_pcontact(): Port don't match: 51219 (contact) 51219 (received) != 55280! 0(1445) DEBUG: ims_registrar_pcscf [save.c:310]: save_pending(): Adding pending pcontact: <sip:alice@10.0.0.8:55280;transport=udp> 0(1445) DEBUG: ims_usrloc_pcscf [pcontact.c:132]: new_pcontact(): New contact [<sip:alice@10.0.0.8:55280;transport=udp>] with 0 associated IMPUs in state: [registration pending] 0(1445) DEBUG: ims_registrar_pcscf [save.c:314]: save_pending(): registering for UL callback 0(1445) DEBUG: ims_usrloc_pcscf [usrloc.c:106]: get_alias_host_from_contact(): no alias param Please guide me for any more changes has to be done, As observed in Wireshark(Register request from 10.0.0.8(host)-PCSCF as REGISTER sip:net1.test SIP/2.0). I think the register request should sent as REGISTER sip:alice@net1.test SIP/2.0 Thanks in advance!! Regards, Sainath From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Tuesday, February 9, 2016 3:00 AM To: Sainath Ellendula (NEP) <sainath.ellendula(a)wipro.com> Cc: basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: RE: Re:[SR-Users] Kamailio IMS deployment Sainath, what was the result for ping on - icsct.net1.test - scscf.net1.test - hss.net1.test to increase debug level you have to modify the corresponding cfg-file, e.g. kamailio-icscf.cfg in line 35: debug=2 Just increase to debug=3 and then start the process again. BR Franz The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

1 0

GCC version in use
by Daniel-Constantin Mierla 09 Feb '16

09 Feb '16

Hello, looking a bit over our makefiles, I am thinking of simplifying some parts related to compiler optimizations, as I noticed some of them are for gcc 2.x. So I would like to see if people are still using old OSes and/or old GCC versions. In other words, if you use old or some dedicated systems and plan to deploy most recent Kamailio versions, reply here with the gcc version in use, particularly interested to see the use of gcc 2.x or 3.x. The idea is not to remove the support for it completely, but to simply and don't try to find all tunings for old versions, but go more with the default gcc options. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

3 7

Re: [SR-Users] Kamailio IMS deployment
by sainath.ellendula＠wipro.com 09 Feb '16

09 Feb '16

Hi Franz, Thank you so much for your response. As suggested modified changes and don't observe connection refused error. After modification few more errors observed. Detailed errors as below. 10.0.0.9 /catalina-optional.jar:lib/catalina.jar:lib/c3p0-0.9.1.jar:lib/base64.jar:lib/asm.jar:lib/asm-attrs.jar:lib/antlr-2.7.6.jar::log4j.properties:.. 2016-02-01 12:09:28,371 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat Tomcat-Server is started. 2016-02-01 12:09:29,301 WARN org.apache.catalina.connector.MapperListener - registerEngine Unknown default host: 10.0.0.9 2016-02-01 12:09:30,294 INFO de.fhg.fokus.hss.web.servlet.ResponseFilter - init Response Filter Initialisation! 2016-02-01 12:09:31,251 INFO de.fhg.fokus.hss.main.TomcatServer - startTomcat WebConsole of FHoSS was started ! 2016-02-01 12:09:34,813 WARN org.hibernate.impl.SessionFactoryObjectFactory - addInstance InitialContext did not implement EventContext 2016-02-01 12:09:34,847 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - <init> Bean style constructor called, don't forget to configure! 2016-02-01 12:09:34,851 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure FQDN: hss.net1.test 2016-02-01 12:09:34,852 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Realm: net1.test 2016-02-01 12:09:34,853 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Vendor_ID : 10415 2016-02-01 12:09:34,854 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure Product Name: JavaDiameterPeer 2016-02-01 12:09:34,854 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure AcceptUnknwonPeers: true 2016-02-01 12:09:34,855 INFO de.fhg.fokus.diameter.DiameterPeer.DiameterPeer - configure DropUnknownOnDisconnect: true 2016-02-01 12:09:34,864 INFO de.fhg.fokus.hss.main.HSSContainer - waitForExit Type "exit" to stop FHoSS! 2016-02-01 12:09:34,873 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer icscf.net1.test:3869 not responding to connection attempt 2016-02-01 12:09:34,876 ERROR de.fhg.fokus.diameter.DiameterPeer.peer.StateMachine - I_Snd_Conn_Req StateMachine: Peer scscf.net1.test:3870 not responding to connection attempt 10.0.0.10 root@server:~# kamailio -f /usr/local/etc/kamailio/kamailio-pcscf.cfg loading modules under config path: /usr/local/lib64/kamailio/modules/ 0(1856) INFO: <core> [sctp_core.c:75]: sctp_core_check_support(): SCTP API not enabled - if you want to use it, load sctp module Listening on udp: pcscf.net1.test [10.0.0.10]:4060 Aliases: *: pcscf.net1.test:* WARNING: no fork mode 0(1856) INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob 0(1856) INFO: rr [rr_mod.c:174]: mod_init(): outbound module not available 0(1856) INFO: ims_usrloc_pcscf [hslot.c:62]: ul_init_locks(): locks array size 512 0(1856) INFO: <core> [udp_server.c:150]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1856) INFO: <core> [udp_server.c:200]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1856) WARNING: ims_usrloc_pcscf [usrloc_db.c:59]: connect_db(): DB connection already open... continuing 0(1856) INFO: <script>: [REGISTER] from [sip:alice@net1.test] to [sip:alice@net1.test] 0(1856) ERROR: <script>: REGISTER (sip:alice@net1.test (10.0.0.8:55859) to sip:alice@net1.test, aaeacddd-376e-4a63-5745-2757d1b9a29d) 10.0.0.11 9(1870) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.11 port 3869 9(1870) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.11 port 3869 9(1870) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(1871) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(1871) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(1871) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 8(1869) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 10(1871) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(1871) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10.0.0.12 9(1883) WARNING: cdp [tcp_accept.c:123]: create_socket(): create_socket(): Trying to open/bind/listen on 10.0.0.12 port 3870 9(1883) WARNING: cdp [tcp_accept.c:148]: create_socket(): create_socket(): Successful socket open/bind/listen on 10.0.0.12 port 3870 9(1883) INFO: cdp [acceptor.c:96]: acceptor_process(): Acceptor opened sockets. Entering accept loop ... 7(1881) INFO: cdp [receiver.c:445]: receiver_process(): receiver_process(): [] Receiver process doing init on new process... 7(1881) INFO: cdp [receiver.c:450]: receiver_process(): receiver_process(): [] Receiver process starting up... 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 0 10(1884) INFO: cdp [peerstatemachine.c:526]: I_Snd_Conn_Req(): I_Snd_Conn_Req(): Peer hss.net1.test 10(1884) WARNING: cdp [receiver.c:864]: peer_connect(): peer_connect(): Trying to connect to 10.0.0.9 port 3868 10(1884) INFO: cdp [receiver.c:932]: peer_connect(): peer_connect(): Peer hss.net1.test:3868 connected 8(1882) ERROR: cdp [peerstatemachine.c:635]: I_Snd_CER(): I_Snd_CER(): Error on finding local host address > Socket operation on non-socket 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 10(1884) WARNING: cdp [peermanager.c:315]: peer_timer(): Inactivity on peer [hss.net1.test], sending DWR... - if we don't get a reply, the peer will be closed 10(1884) INFO: cdp [peermanager.c:280]: peer_timer(): peer_timer(): Peer hss.net1.test State 6 Could you please guide me here. Any suggestions would be very helpful. Thanks in advance!! Regards, Sainath -----Original Message----- From: Franz Edler [mailto:franz.edler@technikum-wien.at] Sent: Saturday, January 30, 2016 1:27 PM To: Sainath Ellendula (WT01 - NEP) <sainath.ellendula(a)wipro.com>; basitstar(a)hotmail.com; sr-users(a)lists.sip-router.org Subject: RE: [SR-Users] Kamailio IMS deployment Hi, > As suggested, modified the changes in icscf.xml and scscf.xml files, PFA > modified files. > > Still getting few errors .... Now it seems to be clear to me where the problem might come from: I have restricted access to mysql server to address 10.0.0.9 only. You have to change the bind-address statement in /etc/mysql.cnf accordingly. See: http://dev.mysql.com/doc/refman/5.7/en/server-options.html#option_mysqld_bi… Change the address to "*" or to 0.0.0.0. BR Franz _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org<mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

2 6

No contact info(0 bindings) in 200-register
by sgy 08 Feb '16

08 Feb '16

Hi Members, I notice an issue: the client register to kamailio server and could receive 200-register message, but no contact infomation(shows 0 bindings) returns in the message(200-register). I checked contact exist in register message and client shows register successfully. When I run command "kamctl online", the client is not online. Could you met with this issue? Expected to your help, thank you very much. Register: REGISTER sip:12.2.1.197 SIP/2.0 Via: SIP/2.0/UDP 12.2.1.180:5060;rport;branch=z9hG4bKPjWScZ6O7MbSbtauTPHcKpjzsHb5U6wxGP Route: <sip:12.2.1.197;lr> Max-Forwards: 70 From: "2016" <sip:2016@12.2.1.197>;tag=jqx1XzTgoS-XKh-S3LyrYmjrCBSqJZ48 To: "2016" <sip:2016@12.2.1.197> Call-ID: AiD6dDi6YOK4.ArBsMpse2MQEoh4dBmP CSeq: 12358 REGISTER User-Agent: A-client Contact: "2016" <sip:2016@12.2.1.180:5060;ob>;+sip.instance="<urn:uuid:00000000-0000-1000-8000-000000020805>";reg-id=0 Supported: geolocation, gruu, path, outbound, answermode, tdialog, replaces, timer, precondition, norefersub Expires: 3600 Allow: INVITE, ACK, BYE, CANCEL, UPDATE, INFO, NOTIFY, REFER, MESSAGE, OPTIONS Authorization: Digest username="2016", realm="12.2.1.197", nonce="Vq8AMFau/wTtkI9/v58I86rqhbvPhSTW", uri="sip:12.2.1.197", response="aebb4a141197b2200bdfc5dce008d9ac" Content-Length: 0 200-Register: //No contact infomation rE/(a)SIP/2.0 200 OK Via: SIP/2.0/UDP 12.2.1.180:5060;rport=5060;branch=z9hG4bKPjpBm-dzHb.9vJY19Ccy9Yz8sx7jigkAM1;received=12.2.1.180 From: "2015" <sip:2015@12.2.1.197>;tag=tVTyij9jGH8wprKa2olsevAockWFs8k0 To: "2015" <sip:2015@12.2.1.197>;tag=090f6aa955fd574e08bca845127013d9.2885 Call-ID: fIQWmPXYtdkT94lzPscrMjzj3R5san9g CSeq: 58932 REGISTER Server: kamailio (4.2.0 (x86_64/linux)) Content-Length: 0 Best Regards, Shengy

2 9

Re: [SR-Users] Replace User Agent
by Daniel-Constantin Mierla 08 Feb '16

08 Feb '16

Hello, for changing the user-agent header you can use: remove_hf("User-Agent"); append_hf("User-Agent: abc\r\n"); Cheers, Daniel On 02/02/16 11:20, Steven Maddox wrote: > Hi, > > I've brought up this topic up before (here and on IRC) and I feel like > I'm getting closer but still a bit stuck. Since it takes a while to > explain the idea (and get past any confusion!) I've summarized it in a > diagram for easier understanding. > > At work my employers have decided to use this god awful hosted PBX > which is picky about which phones can register and checks their user > agent, the hosted PBX is marked on the diagram as the purple blob. > > > > The progress I've made since last time is getting Kamailio 4.2.4 on > that little white device, the *only* purpose of that device is to > change the user agent - nothing more... since it has lots of ports it > could have lots of "Unapproved" phones directly connected to it. > > Someone gave me a link to this as a starting point... > https://blog.voipxswitch.com/2015/03/27/kamailio-basic-sip-proxy-all-reques… > > However I'm not sure what portions of the default kamailio.cfg should > be kept to use this, additionally it doesn't include anything about > changing user agents. > > The normal configuration of an "Approved" phone is *like*... > > username="441234111999" > password="rAnD0Mp4s5" > auth_user="jsmith" > domain="company.co.uk" > registrar/proxy="uk.ic.56hnt.hlpcom.co.uk" > > In terms of the configuration of an "Unapproved" phone I can either... > > 1) Put in exactly the same as above (as though it isn't intending to > contact Kamailio)... but since the phone is directly connected to the > Kamailio device - perhaps Kamailio could watch SIP traffic coming in > on eth1 (even if it isn't addressed to it), alter the user agent and > pass it out through eth0 ? I'm not sure even Kamailio is capable of > this - but it'd be cool if possible. > > 2) Put in exactly the same as above however just change the > registrar/proxy to be the IP of the Kamailio device... Kamailio can > then keep all other configuration the same as it passes it through - > just change the user agent. > > Any thoughts? > > n.b. > 1) Yes changing the user agent definitely does allow you connect, it's > not just a guess - tested it with Asterisk. > 2) No I don't think the hosted PBX supports path extensions - I'd > rather not rely on it supporting undocumented stuff anyway. > > -- > Steven Maddox > > > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users(a)lists.sip-router.org > http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

1 0

Users in different domains and multiple domains
by Barış Şekerciler 08 Feb '16

08 Feb '16

Hello everyone! I'm wondering something about Kamailio. Here is the idea: Such and example, I want to give base system which depends on Kamailio to 3 companies in 1 server. So I have 1 Kamailio Server and 4 or 5 Freeswitch server. Thus, I have to set a domain for each company, so total is I need 3 domains. For example a, b, c are users. But they should in the different domains for know which is which. In a word, it should seems like this: a(a)subdomain.domain.com b(a)subdomain.domain.com c(a)subdomain.domain.com a(a)subdomain2.domain.com b(a)subdomain2.domain.com c(a)subdomain2.domain.com or a(a)subdomain.domain2.com b(a)subdomain.domain2.com c(a)subdomain.domain2.com etc... So where can I do this? Remember, Kamailio should in the 1 server and all of domains and users should in this server (I will use Postgres) For more details, you can write. Thank you. Regards.

2 5

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Below is the SIP record captured using NGREP: http://pastebin.com/hUqP56fw Regards

2 1

Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Below is the SIP record captured using NGREP Regards U 2016/02/07 20:20:06.054910 90.X.X.68:25189 -> 10.1.4.23:5060 INVITE sip:0031651022945@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. . v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.056642 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.8324. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 INVITE. Proxy-Authenticate: Digest realm="voip.system.com", nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme". Content-Length: 0. . U 2016/02/07 20:20:06.059536 90.X.X.68:25189 -> 10.1.4.23:5060 ACK sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-17160a2503261a6b-1---d8754z-;rport. To: "003165656565"<sip:003165656565@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.8324. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 1 ACK. Content-Length: 0. . U 2016/02/07 20:20:06.061317 90.X.X.68:25189 -> 10.1.4.23:5060 INVITE sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. . v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.065526 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 100 trying -- your call is important to us. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Content-Length: 0. . U 2016/02/07 20:20:06.065940 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 INVITE sip:003165656565@voip.system.com SIP/2.0. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>. From: <sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Content-Type: application/sdp. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 230. Remote-Party-ID: "9005" <sip:9005@103.XXX.XXX.23 >;party=calling;privacy=off;screen=no. v=0. o=- 1 2 IN IP4 10.1.10.11. s=CounterPath eyeBeam 1.5. c=IN IP4 10.1.10.11. t=0 0. m=audio 52282 RTP/AVP 0 8 101. a=alt:1 1 : h0yu+bYK 4sdGkNzr 10.1.10.11 52282. a=fmtp:101 0-15. a=rtpmap:101 telephone-event/8000. a=sendrecv. U 2016/02/07 20:20:06.090448 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 100 Trying. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.883489 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.883574 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:10.884941 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 180 Ringing. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Length: 0. . U 2016/02/07 20:20:10.885646 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 183 Session Progress. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:20.596774 90.X.X.68:25189 -> 10.1.4.23:5060 CANCEL sip:003165656565@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport. To: "003165656565"<sip:003165656565@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 CANCEL. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="b739a517585b9bdcd997b3e3322c3bad",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:20.599102 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 500 cancel error. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189;received=90.X.X.68. To: "003165656565"<sip:003165656565@voip.system.com >;tag=79597765d0ff0775a3cc048295d6500c-3fc1. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 CANCEL. Content-Length: 0. . U 2016/02/07 20:20:23.407575 90.X.X.68:25189 -> 10.1.4.23:5060 REGISTER sip:voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-7176c672f55aba4c-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189;rinstance=5a52b9593b8bd582>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 7 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc1l1a3NGs8NrsUIZb+Kyau9v9Q9jUn",uri="sip:voip.system.com ",response="602901348ea359e385f99c5d4261ea5c",algorithm=MD5. Content-Length: 0. . U 2016/02/07 20:20:23.409286 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-7176c672f55aba4c-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.fab9. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 7 REGISTER. WWW-Authenticate: Digest realm="voip.system.com", nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa". Content-Length: 0. . U 2016/02/07 20:20:23.515175 90.X.X.68:25189 -> 10.1.4.23:5060 REGISTER sip:voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189;rinstance=5a52b9593b8bd582>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Expires: 3600. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa",uri="sip:voip.system.com ",response="e7d27803d159526ee124e64e59bcc7d0",algorithm=MD5. Content-Length: 0. . U 2016/02/07 20:20:23.520290 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Contact: <sip:9005@90.X.X.68 :25189;rinstance=5a52b9593b8bd582>;expires=600;received="sip:90.X.X.68:25189". Content-Length: 0. . U 2016/02/07 20:20:23.520546 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-9a36b0060c000e77-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=4f0c6043. Call-ID: MzliN2E4ZTRkYjViZWFiN2Y4YjRjZDExMjc4ODg0NWQ.. CSeq: 8 REGISTER. Contact: <sip:9005@90.X.X.68 :25189;rinstance=5a52b9593b8bd582>;expires=600;received="sip:90.X.X.68:25189". WWW-Authenticate: Digest realm="voip.gpnsystem.com", nonce="Vrc3s1a3Noe7UjBYG6PYJGPaghIpTBqa", qop="auth". Content-Length: 0. . U 2016/02/07 20:20:24.426155 90.X.X.68:25189 -> 10.1.4.23:5060 SUBSCRIBE sip:9005@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-3f31377b941acf34-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 1 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. User-Agent: eyeBeam release 1102q stamp 51814. Event: message-summary. Content-Length: 0. . U 2016/02/07 20:20:24.428409 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-3f31377b941acf34-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.351d. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 1 SUBSCRIBE. Proxy-Authenticate: Digest realm="voip.system.com", nonce="Vrc3tFa3NoiYOjmQMojfuh3ttECnmpZW". Content-Length: 0. . U 2016/02/07 20:20:24.534158 90.X.X.68:25189 -> 10.1.4.23:5060 SUBSCRIBE sip:9005@voip.system.com SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-4b7b5d2b2726d57d-1---d8754z-;rport. Max-Forwards: 70. Contact: <sip:9005@90.X.X.68:25189>. To: "+3165656565"<sip:9005@voip.system.com>. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 2 SUBSCRIBE. Expires: 300. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3tFa3NoiYOjmQMojfuh3ttECnmpZW",uri="sip:9005@voip.system.com ",response="2d1f53e6973bf2eb878f679add8bebc8",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Event: message-summary. Content-Length: 0. . U 2016/02/07 20:20:24.537592 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 404 No voicemail service. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-4b7b5d2b2726d57d-1---d8754z-;rport=25189;received=90.X.X.68. To: "+3165656565"<sip:9005@voip.system.com >;tag=2b9ac8ee2b24b631c656d775cbaad9e0.2dea. From: "+3165656565"<sip:9005@voip.system.com>;tag=f1000570. Call-ID: NzJiNTM5YjlhOTIyYjFhNWRkNTkzOWQ3MzViNGJiYTg.. CSeq: 2 SUBSCRIBE. Content-Length: 0. . U 2016/02/07 20:20:25.358979 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 OPTIONS sip:103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bK828d.ce4b9911000000000000000000000000.0. To: <sip:103.XXX.XXX.22:5060>. From: <sip:dispatcher@localhost>;tag=56254dc816783af7c55a1ac0231200e3-6d5c. CSeq: 10 OPTIONS. Call-ID: 4063eaf942a6e19e-12704(a)10.1.4.23. Max-Forwards: 70. Content-Length: 0. . U 2016/02/07 20:20:25.365672 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 404 Not Found. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bK828d.ce4b9911000000000000000000000000.0;received=103.XXX.XXX.23. From: <sip:dispatcher@localhost>;tag=56254dc816783af7c55a1ac0231200e3-6d5c. To: <sip:103.XXX.XXX.22:5060>;tag=as00a791b0. Call-ID: 4063eaf942a6e19e-12704(a)10.1.4.23. CSeq: 10 OPTIONS. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Accept: application/sdp. Content-Length: 0. . U 2016/02/07 20:20:26.250911 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.66b1d70306f62152bc5c1a7a1b68eb82.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: <sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:26.252410 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-06468b691617fc32-1---d8754z-;rport=25189. Record-Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 INVITE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Contact: <sip:003165656565@103.XXX.XXX.22:5060>. Content-Type: application/sdp. Content-Length: 327. . v=0. o=root 1558510539 1558510539 IN IP4 103.XXX.XXX.22. s=Useragent. c=IN IP4 103.XXX.XXX.22. t=0 0. m=audio 59130 RTP/AVP 9 18 0 8 101. a=rtpmap:9 G722/8000. a=rtpmap:18 G729/8000. a=fmtp:18 annexb=no. a=rtpmap:0 PCMU/8000. a=rtpmap:8 PCMA/8000. a=rtpmap:101 telephone-event/8000. a=fmtp:101 0-16. a=ptime:20. a=sendrecv. U 2016/02/07 20:20:26.362474 90.X.X.68:25189 -> 10.1.4.23:5060 ACK sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-8c04097075073c09-1---d8754z-;rport. Max-Forwards: 70. Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 ACK. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.362493 90.X.X.68:25189 -> 10.1.4.23:5060 BYE sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport. Max-Forwards: 70. Route: <sip:voip.system.com ;lr;ftag=d7622f3c;vsf=AAAAAE9fWUVwRQEFXldDAB9XFAQLHlcQGwhXG1NZXQ--;nat=yes>. Contact: <sip:9005@90.X.X.68:25189>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri="sip:003165656565@103.XXX.XXX.22 :5060",response="e3f1d030387f1b10ab21c126b8e8d656",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.365975 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 ACK sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKddff.9327d42091ecb853a5c80ed2dd347040.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-8c04097075073c09-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 2 ACK. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri=" sip:003165656565@voip.system.com ",response="3473bd0cf6c9af95690edc953fd7346d",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.367367 10.1.4.23:5060 -> 103.XXX.XXX.22:5060 BYE sip:003165656565@103.XXX.XXX.22:5060 SIP/2.0. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKedff.e74ad188da31f15ff2ec2bcb57878ae2.0. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. Max-Forwards: 69. Contact: <sip:9005@90.X.X.68:25189;alias=90.X.X.68~25189~1>. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Proxy-Authorization: Digest username="9005",realm="voip.system.com ",nonce="Vrc3ola3NnZiKoF8g2hRTk/0p4EeWKme",uri="sip:003165656565@103.XXX.XXX.22 :5060",response="e3f1d030387f1b10ab21c126b8e8d656",algorithm=MD5. User-Agent: eyeBeam release 1102q stamp 51814. Content-Length: 0. . U 2016/02/07 20:20:26.368319 103.XXX.XXX.22:5060 -> 10.1.4.23:5060 SIP/2.0 200 OK. Via: SIP/2.0/UDP voip.system.com:5060 ;branch=z9hG4bKedff.e74ad188da31f15ff2ec2bcb57878ae2.0;received=103.XXX.XXX.23. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. From: "+3165656565"<sip:voip.system.com:5060>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Length: 0. . U 2016/02/07 20:20:26.369422 10.1.4.23:5060 -> 90.X.X.68:25189 SIP/2.0 200 OK. Via: SIP/2.0/UDP 10.1.10.11:51106 ;received=90.X.X.68;branch=z9hG4bK-d8754z-fd38c235b8219d09-1---d8754z-;rport=25189. From: "+3165656565"<sip:9005@voip.system.com>;tag=d7622f3c. To: "003165656565"<sip:003165656565@voip.system.com>;tag=as18998769. Call-ID: MzEyNTgyOGYwODU0NTEwZjE2OGJmMWVmNzRjMzkxZGI.. CSeq: 3 BYE. Server: UltraTone. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE. Supported: replaces, timer. Content-Length: 0. . <CAEmfXJ4KeqaPD_7k9pgFJNK3Ny4OsQ5X36M+r=Y6LQ1eYwy0pg(a)mail.gmail.com>

1 0

Re: [SR-Users] Error or Bug: [t_msgbuilder.c:490]: build_local_reparse(): ERROR: build_local_reparse: HDR_EOH_T was not found
by Sid Mason 07 Feb '16

07 Feb '16

Hi, Thanks a lot for the reply, It means a lot to as I am stuck on this issue. I'm not sure if attachment works here or not. I will paste the log in paste bin: http://pastebin.com/0w6a8iTB Regards <CAEmfXJ4KeqaPD_7k9pgFJNK3Ny4OsQ5X36M+r=Y6LQ1eYwy0pg(a)mail.gmail.com>

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users