[Serusers] Handling of REFER messages

[Greger V. Teigre]

I'm not sure if I understand what you want to accomplish, but I would say that if you can get the REFERs to SER, then you can do whatever you want with them.
g-)
  ----- Original Message ----- 
  From: Miroslaw Nawrot 
  To: serusers at lists.iptel.org 
  Sent: Friday, October 14, 2005 02:46 AM
  Subject: [Serusers] Handling of REFER messages


  Hi, I am trying to do a peculiar task and I want to find out if SER can do it. The issue is with call transfers which generate the REFER message. I am connecting a Nortel voip switch to Asterisk via sip. I need to have all call transfers generated by the Nortel switch to not reach Asterisk as all the call transfers are done to dids/extensions not found on the Asterisk PBX. Instead I would like to intercept / re-route them back to my Nortel switch which can handle it. Currently I have a workaround using an Audiocodes gateway with loopback cables. The Audiocodes when sees the transfer request sends it back to the Nortel switch. As this is a wasteful use of expensive hardware I would like to find another method to do this. Can someone let me know if this is possible with SER? And if it is which functions do I use? Any help is greatly appreciated.

  Mirek







  The Future of Voice


  Globalive Communications Corp.

  T: 416-640-1088

  F: 416-640-1089

  60 Adelaide St. E, 6th Floor

  Toronto, ON, M5C 3E4

  www.globalive.com




------------------------------------------------------------------------------


  _______________________________________________
  Serusers mailing list
  serusers at lists.iptel.org
  http://lists.iptel.org/mailman/listinfo/serusers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20051027/bc852ba3/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 3212 bytes
Desc: not available
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20051027/bc852ba3/attachment.jpeg>