Guest zhangmin Report post Posted 09/06/2012 07:52 AM There is a very strange problem,yesterday I registed two clients in config file.It works well,but today only on can work. please help me ,thanks. attachment.zip Share this post Link to post
Guest zhangmin Report post Posted 09/06/2012 08:41 AM I have solved this problem.now another problem comes out. I have tow lines and tow clients.how can I bind a client to a lines.So that I could use different script on different clients. Is this possible? Share this post Link to post
SupportTeam Report post Posted 09/06/2012 08:58 AM You are registering two numbers/extensions with the switch. 5000 and 7000. If multiple numbers are registered with same "realm" then in the <VoIP_Authentications> section you need to indicate which <VoIP_Authentication> entry is for which number/extension. To do this you need to use the <Identity> entry. The <AuthUsername> entry is not enough. <AuthUsername> and <AuthPassword> just specifies what username/password to supply during SIP digest authentication. If <Identity> is omitted then the first <VoIP_Authentication> entry with a matching realm will be used. Try using these in the respective <VoIP_Authentication> entries: <Identity>sip:7000@192.168.1.24</Identity> <Identity>sip:5000@192.168.1.24</Identity> Share this post Link to post
SupportTeam Report post Posted 09/06/2012 08:59 AM I have solved this problem.now another problem comes out. Did you solve this using <Identity> entries or another way? Share this post Link to post
SupportTeam Report post Posted 09/06/2012 09:02 AM I have tow lines and tow clients.how can I bind a client to a lines.So that I could use different script on different clients.Is this possible? You can usually use the $RV_DNIS to see for which account the arriving call was intended for. Can you please post the vgEngine and ktTel traces capturing the system startup and an incoming call? Please .ZIP up any traces before posting. Share this post Link to post
Guest zhangmin Report post Posted 09/10/2012 08:32 AM Quote I have solved this problem.now another problem comes out. Did you solve this using <Identity> entries or another way? yes ,I solve this using <Identity> entries. but it realy very strange,sometime I registe two clients in config file without using <Identity>.It works well.and sometime not. I think there is a bug. Bad luck ,my pc is being repaired ,so I can not give you the log file. maybe I will post it to you latter. Share this post Link to post
SupportTeam Report post Posted 09/10/2012 08:40 AM Using the <Identity> field is how the registrations for the different accounts on same server are differentiated. Not sure why registrations would sometimes work without it. Usage instructions say to use the <Identity> field in case of multiple accounts on same SIP server. Share this post Link to post
Guest zhangmin Report post Posted 09/10/2012 09:37 AM You can usually use the $RV_DNIS to see for which account the arriving call was intended for. I know ISDN line can use this RV.but how about in VoIP? Share this post Link to post
SupportTeam Report post Posted 09/10/2012 09:58 AM $RV_DNIS works in VoIP as well. You can even see its value for the incoming call captured in the trace attached to first post in this thread. From the vgEngine log: 153457.197 6 3 1 d added $RV_DNIS | 7000@192.168.1.24:5060 Look in vgEngine log to see what other variables are created during call startup and script processing. eg: 153457.197 6 3 1 d added $RV_CIDNUMBER | 2000@192.168.1.24 Share this post Link to post