Well, after a process kill, host reboot, etc. it worked, at least for the outgoing calls.
For incoming calls via ISDN I'm now getting the following:
shaggy:/home/ucacsva # (10812) ERROR: getObjectForMessage (IsdnCapiConnectionManager.cpp:362): getObjectForMessage: Could not find callback object for message (msgid=1202, adr follows) (10812) DEBUG: getObjectForMessage (IsdnCapiConnectionManager.cpp:363): ADR: [0] [0] [2] [1] (10812) DEBUG: messageloop (IsdnCapiConnectionManager.cpp:176): incoming call deteced (10812) ERROR: incomingCall (IsdnCapiConnection.cpp:69): callee number too long (-1) (10812) ERROR: getObjectForMessage (IsdnCapiConnectionManager.cpp:362): getObjectForMessage: Could not find callback object for message (msgid=1205, adr follows) (10812) DEBUG: getObjectForMessage (IsdnCapiConnectionManager.cpp:363): ADR: [0] [0] [2] [1] (10812) DEBUG: messageloop (IsdnCapiConnectionManager.cpp:191): DEBUG: could not find object for callback (DISCONNECT_IND) (10812) DEBUG: messageloop (IsdnCapiConnectionManager.cpp:191): DEBUG: this could be a bug!
I have done all configs for MSN numbers in isdngw.conf, but in vain. British Telecom seems to insist to signal my terminal as MSN=0. Even after I register a softphone with SER as user "0", the inbound call gives me the above errors. That's how far I could get.
If anyone has a clue, in particular BT users with or without using MSN numbering, I would appreciate.
Many thanks, -- Socrates.
Socrates Varakliotis wrote:
Hi Marian:
There seem to be more than a versioning problem with my isdn g/w. I synch'ed SER rel_0_8_14 to SEMS ser_rel_0_8_12 and, although the problem with t_reply() is gone, here's another issue:
I can dial from inside and outside the g/w, call is established, but nothing can be heard on either side, i.e. no media exchange. Also, hangup is not possible.
I've tried using both isdn4linux and CAPI drivers, same result. Here's sems' output:
(10164) DEBUG: changePSTNState (IsdnCall.cpp:419): terminating i4l inbound listener thread (10164) DEBUG: changePSTNState (IsdnCall.cpp:435): now both sides connected, running connectAudio! (10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not available for writing, dropping data (10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not available for writing, dropping data (10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not available for writing, dropping data (10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not available for writing, dropping data (10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not available for writing, dropping data (10164) INFO: putVoiceStream (IsdnDevice.cpp:478): isdn device not available for writing, dropping data
If ser.cfg, sems.conf, and isdngw.conf would help people come up with some advice I could post them to the list.
Thanks
Socrates.
Marian Dumitru wrote:
Hi Socrates,
yes, you are using mismatched version. For SER rel_0_8_14 use SEMS ser_rel_0_8_12.
Best regards, Marian Dumitru
Socrates Varakliotis wrote:
Hi Marian:
Thanks for the answer.
Given that my ser.cfg loads the tm module, I presume the problem emanates from SER/SEMS versions. I've checked out rel_0_8_14 of sip_router and the CVS head of SEMS. Are these known to have conflicts?
I recall there was a reason for me checking out the tagged version of sip_router, something I've read or experienced about mysql, or serweb (don't remember what exactly). Which raises an issue with synch'ing the two s/w in the CVS.
Is there a corresponding tag for answer_machine then?
Regards,
Socrates.
----- Original Message ----- From: "Marian Dumitru" marian.dumitru@voice-sistem.ro To: "Socrates Varakliotis" S.Varakliotis@cs.ucl.ac.uk Cc: serusers@lists.iptel.org Sent: Monday, October 25, 2004 8:47 PM Subject: Re: [Serusers] SER + SEMS + isdngw problem
Hi Socrates,
My first guess is you haven't load TM module which makes available function "t_reply" or you are mixing the version of SER and SEMS.
Best regards, Marian Dumitru
Socrates Varakliotis wrote:
Hi All:
I'm trying to make an outgoing call from Kphone to an ISDN line. Although the called phone rings, when I pickup the call drops and I get the following errors on the logfiles:
Has anyone come across this? Any suggestions welcome.
Regards,
Socrates.
------------------- SER.log ---------------------------
...
sip_request.isdngw INVITE 76793696 . 128.16.64.71 128.16.64.71 . sip:576793696@128.16.64.71 sip:root@128.16.64.71:5062;transport=udp "Socrates Varakliotis" sip:6222@shaggy.cs.ucl.ac.uk sip:576793696@128.16.64.71 183464563 64247849 . 5593 55871:1543819790 . . P-MsgFlags: 0 . v=0 o=username 0 0 IN IP4 128.16.64.71 s=The Funky Flow c=IN IP4 128.16.64.71 t=0 0 m=audio 32802 RTP/AVP 0 97 3 a=rtpmap:0 PCMU/8000 a=rtpmap:3 GSM/8000 a=rtpmap:97 iLBC/8000
5(4251) DEBUG: write_to_vm_fifo: write completed 5(4251) DEBUG: add_to_tail_of_timer[0]: 0x402e35a4 5(4251) DEBUG:destroy_avp_list: destroing list (nil) 5(4251) receive_msg: cleaning up 9(4255) ERROR: fifo_server: command t_reply is not available 9(4255) ERROR: fifo_server: command must begin with :: isgndw: ringing 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09 9(4255) ERROR: fifo_server: command must have at least 3 chars 9(4255) INFO: fifo_server: command empty 9(4255) ERROR: fifo_server: command t_reply is not available 9(4255) ERROR: fifo_server: command must have at least 3 chars 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09 9(4255) ERROR: fifo_server: command must begin with :: Content-Type: application/sdp 9(4255) ERROR: fifo_server: command must begin with :: v=0 9(4255) ERROR: fifo_server: command must begin with :: s=session 9(4255) ERROR: fifo_server: command must begin with :: t=0 0 9(4255) ERROR: fifo_server: command must begin with :: a=rtpmap:0 PCMU/8000 9(4255) INFO: fifo_server: command empty 9(4255) ERROR: fifo_server: command t_reply is not available 9(4255) ERROR: fifo_server: command must begin with :: could not send response. 9(4255) ERROR: fifo_server: command must begin with :: 000010A77D8E0A09 9(4255) ERROR: fifo_server: command must have at least 3 chars 9(4255) INFO: fifo_server: command empty 10(4257) DEBUG: timer routine:0,tl=0x402e35a4 next=(nil)
------------------- SEMS.log ---------------------------
....
180 isgndw: ringing 55871:1543819790 000010A77D8E0A09 Contact: sip:76793696@128.16.64.71 . .
(4263) DEBUG: write_to_fifo (SerClient.cpp:244): Write to fifo:
completed
(4263) DEBUG: getReturnCode (AmRequest.cpp:357): response from Ser: 500 command 't_reply' not available (4263) ERROR: reply (AmRequest.cpp:335): AmRequestUAS::reply: 500 command 't_reply' not available (4263) DEBUG: cb_connect_active_ind (IsdnCapiConnection.cpp:282): callback funtion called: cb_connect_active_ind! (4263) DEBUG: cb_connect_active_ind (IsdnCapiConnection.cpp:290): physical connection established, now creating logical connection (4263) DEBUG: cb_connect_b3_conf (IsdnCapiConnection.cpp:308): connected, now unlocking mutex (4263) DEBUG: changePSTNState (IsdnCall.cpp:348): CALL: PSTN state (outbound): from (CONNECTING|CONNECTING) to (CONNECTING|CONNECTED) (4263) DEBUG: changePSTNState (IsdnCall.cpp:550): DONE: PSTN state (outbound): from (CONNECTING|IDLE) to (CONNECTING|CONNECTING)
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Voice Sistem http://www.voice-sistem.ro
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers